![]() It sounds as if including an exports field in package.json is effectively a breaking change due to Node compat concerns, so we can't do that yet.(I can also see an argument for only releasing those in a 2.0 as a carrot to get people to upgrade, so I'm willing to listen to debate on this point.) Plus, it's all additive APIs, much like React released hooks in a 16.8 minor. I want to get the RTKQ stuff out in a minor build to help increase the initial uptake on that.So, in theory, none of the build changes should be breaking yet. The build artifacts we're generating should effectively match what we've had so far: ES5 syntax and IE11 compat for CJS/ESM/UMD, plus a new set of "modern" artifacts that target bundlers and browsers. We just merged in the big TDX->ESBuild conversion over in chore(build): move tsdx to esbuild #957.I want to get that into RTK 1.6 too.īut at this point, we have no real plans to actually get Redux 5.0 out the door. I am planning to put out a new Redux 4.1.0 release in the near-ish future that would extract our error messages to "error codes" to shave down prod size, tweak a couple error messages, and remove the remaining deps like `symbol-observable. So, basically it's about no one prioritizing the effort, combined with concern about breaking the ecosystem (and potentially for not much real benefit). Meanwhile, Redux 4.x works just fine, both code and types. For TS specifically, there's almost definitely some breaking changes in the Redux core TS types, either because something got "fixed" during the TS conversion, or something accidentally got broken.A major release of any lib is always a big deal, and there's a lot of Redux-related packages that might need to get updated to say they work with 5.x.was overseeing both of those changes, and he's been extremely busy with his day job for a while now.There's a couple different potential things here: Sorta related to that, there's some changes to the redux-thunk typings that have been sitting around unreleased for a very long time. So if you look over in on master, the Redux core was actually converted to TS almost two years ago.Īnd it's just sat there ever since, unreleased. The ESBuild PR in #957 is problematic for IE11 compat out of the box, but it's likely we could down-compile the ESBuild output to resolve that. Right now we're planning to put RTK Query out in RTK 1.6. I suppose the hypothetical Redux 5.0 with potentially altered TS types might fit in there, but I truly have no idea if we're ever going to get around to releasing that. In particular, dropping the default enableES5() plugin call for Immer, and dropping publishing IE11-compatible syntax from our published build artifacts. The most obvious ones I can think of would involve changing back-compat publishing stuff. Okay, with that disclaimer out of the way: what would an RTK 2.0 look like? What "breaking" changes would we want? When should we actually consider doing that? ![]() # THIS IS HYPOTHETICAL AND WE ARE NOT GOING TO BE RELEASING RTK 2.0 ANY TIME SOON PLEASE DON'T PANIC UPDATE : THIS IS NOW MUCH LESS HYPOTHETICAL AND HOPEFULLY HAPPENING SOON-ER THAN LATER!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |