[legacy-framework] (newapp) move dev dependencies to devDependencies in package.json (better for Docker) #2475
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are the changes and their implications?
Prior to this commit devDependencies were moved to dependencies, in favor to fix issues with builds on some cloud server providers. But this results into a very large production container. If build as Docker image just the directory of node_modules is larger than 550MB.
There is significant reduction by moving following dependencies back to devDependencies
Testing
Build the image:
check if image was build. Check size
Test run and open in browser