-
Notifications
You must be signed in to change notification settings - Fork 45
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
We are using abandoned Razzle - should it be removed or replaced? #1345
Comments
I tried upgrading webpack-dev-server to 4.0.0 - this was blocked by latest released Razzle being broken. Though maybe we can patch it somehow for now? But breakage caused by Razzle being dead will get worse. And while for now it is survivable we may have problem if something will need to updated for one or another reason and it will break on old versions and new ones will break on Razzle. Ideally it would be proactively fixed.
|
Advice is definitely wanted, what would be the best tool for roles fulfilled by Razzle in this project? Maybe @tomalrussell or @mz8i have advise what they would use nowadays? |
See https://github.com/jaredpalmer/razzle and https://github.com/jaredpalmer/razzle/commits/master/
Luckily it is used in dev environment and in build process, not in production.
Still, it would be a good idea to replace it.
The text was updated successfully, but these errors were encountered: