Skip to content
This repository has been archived by the owner on Oct 29, 2021. It is now read-only.

Support for react 16 #95

Open
ghost opened this issue Nov 8, 2017 · 7 comments
Open

Support for react 16 #95

ghost opened this issue Nov 8, 2017 · 7 comments

Comments

@ghost
Copy link

ghost commented Nov 8, 2017

Does this project support react 16?

@jimbojetlag
Copy link

Bump! Is this project dead?

Unfortunately webpack also needs updating. Yes it sucks to keep up with javascriptdashians.

@olebedev
Copy link
Owner

olebedev commented Mar 1, 2018

The project definitely needs more attention. I don’t know when could I dig into it and update all the things. Maybe in around 2-3 weeks. Any help is welcome!

@jimbojetlag
Copy link

jimbojetlag commented Mar 1, 2018

Is there a way that parts of the project can be delegated to create-react-app, so that the javascript updates are outsources? Even if this is updated now, it will require constant future updates.

@olebedev
Copy link
Owner

olebedev commented Mar 1, 2018

I've thought exactly about this approach. And it seems we could rely on CRA a bit. But not sure that it generates the code to use it on the server side too. Requires some investigation.

@stefanfransen
Copy link

Is there any update on this? Thanks!

@omgnull
Copy link

omgnull commented May 7, 2018

ping 0.0.0.0 -update -please

@emwalker
Copy link

emwalker commented May 7, 2018

I did this recently in a project that has now diverged enough that I won't be able to easily put together a PR for this. From memory, switching to React 16 has several follow-on effects. I think it might mess up the existing hot module reloading.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants