-
-
Notifications
You must be signed in to change notification settings - Fork 201
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
Razzle as dev dependency? #419
Comments
+1. I encountered this problem while trying to containerize a AfterJS app. Having to add razzle and all its dependencies into a production build makes the container image very big (due to all of the dependencies of razzle like babel etc.). |
+1. I encountered this issue as well as when testing out the examples provided it uses 1 major version behin of razzle and even no longer works once all additional dependencies are added. |
your point is totally valid, I'm going to use tsdx for repo after.js package it contains necessary utils for logging .... |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Can we please reopen this? |
🚀 Feature request
All Razzle examples use Razzle package as dev dependency. Except AfterJS - it needs Razzle as regular dependency because of razzle-dev-utils.
Current Behavior
If Razzle stays as a dev dep, I get this error message in production build:
Desired Behavior
I would like to add AfterJS to my Razzle based project without moving Razzle from dev to regular dependencies.
Suggested Solution
Is using razzle-dev-utils in AfterJS worth? Can it be replaced with something?
The text was updated successfully, but these errors were encountered: