search

jamiebuilds / unstated-next

200 bytes to never think about React state management libraries ever again
MIT License
4.18k stars 145 forks source link

Moving from unstated to unstated-next #61

Open deg opened 4 years ago

deg commented 4 years ago

I had hoped to do a gradual move from unstated to unstated-next, but it's much trickier than I had expected, since I can't access the unstated-next state from any component that is still a class. Are there any good strategies or techniques for an incremental move?

Failing this, would you consider one more release of unstated, with the react calls renamed to the UNSAFE_ versions? That would at least buy me some time to make changes (until React 17) without exposing the long ugly chrome console message from React.

rators commented 4 years ago

@deg seems @jamiebuilds has abandoned both unstated projects. no replies to any of the issue and no prs merged or reviewed for months. we are moving away from unstated

austincollinpena commented 4 years ago

@rators What are you moving towards?

loganvolkers commented 4 years ago

For other people coming here, try unstated-retro, (see #53)

@rators @austincollinpena If you want to migrate away from unstated or unstated-next, you can also always try copy-pasting the 36 lines of code that make up the library. Writing unstated-retro was a one-hour task. Basically the React Context API is already most of what you need, and unstated-next is just a paper-thin layer on top to make a cleaner API.