Move React development dependencies to devDependecies #317
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.
We have a backend app. Which is small. But for some reason we have a couple of hundred React modules installed in production, in a little pure web server (soon to be a little AWS lambda).
Looks like
@bull-board/ui
have the UI inside the NPM gzip bundle:/dist/static/
. This bundle already contains React dependencies, compiled, minified, bundled.We identified the problem. The
@radix-ui/
things are not production dependencies. They are build-time dependencies (aka devDependencies in NPM).This PR decreased the
node_modules
bySee for yourself:
Please, publish the
@bull-board/ui
with this little fix. The little servers across the world will be thankful. :)