-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support React 17 in peer dependencies, move to a fork of create-react-context #452
base: master
Are you sure you want to change the base?
Conversation
LGFM |
Will this get merged soon? Having some issues with storybook :) |
Cool stuff! Looks like |
Hi would love to get this in to unblock consumers (and lots of people trying to update storybook), is there any timeline when this will be merged and a new version released @bcomnes ? :) |
I dunno, whenever a maintainer can be tracked down with a few minutes. I'm external |
Ah my mistake! I thought you were internal in this space! |
@ryanflorence, this repo still maintain or currently it's frozen and we must use react-router ? |
@Hypnosphi greetings from Salzburg and thank you for this PR. I would like raise the question if there is a point in using create-react-context polyfill. Couldn't it be exchanged in favor of useContext. I know then reach/router would lose the backwards compatibility to react 15. However it would be nice if a maintainer could review this, since it's not a huge change and this issue is blocking a lot of people from moving to npm v7. Please let me know if there is anything I can do to get this merged. |
|
Any news on this folks? |
Looks like reach-router is getting replaced with react router 5?
Migration guide here. https://reacttraining.com/blog/reach-react-router-future/ wrt storybook, @storybook/api@6.2.8 and @storybook/router@6.2.8 would need to migrate over. Still trying to figure out if that is possible still. |
Ok, so I looked into moving from reach/router to react-router 6 in the storybook context. Unfortunately in that case there is enough going on to where its involved and not a trivial rename of things. I do support the effort to get that moved over, but in the meantime, landing this would be extremely helpful. Does anyone have back channels to @ryanflorence or @blainekasten, (or someone who might) to land this simple change in the meantime? I'll be collecting react-router 6 notes for storybook over in their issue tracker. |
@bcomnes Another option would just be to fork @reach/router and do our own release, similar to what @Hypnosphi has done for the create-react-context library. |
@shilman yeah, that would be a good option too. I would be happy to do that work or let @Hypnosphi do it. |
I'm just suggesting, did anyone try the organization email, because if that not responding then it means they actually ignore this repo. PS: I'm new around here. |
Gatsby has a working React v17 fork: https://www.npmjs.com/package/@gatsbyjs/reach-router |
Well it doesn't have typescript or even a link to repo or issue page. |
Yes, very true. It’s not meant be be a replacement in any kind. I just wanted to mention it, because this PR is about React v17 compatibility. |
It'd be great to get rid of this warning...
|
Should be fixed when Storybook v6.4.0 is released thanks to storybookjs/storybook#16440. |
This is a breaking change-free alternative to #436
Here's the diff between my fork and the original package: https://github.com/jamiebuilds/create-react-context/pull/33/files