Skip to content
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

Don't automatically install website node modules. #751

Merged
merged 1 commit into from
Dec 7, 2017

Conversation

manthey
Copy link
Contributor

@manthey manthey commented Dec 7, 2017

When geojs is used as a node module in another project, we should install all of the website's node modules. Doing so bloats the deployment directory of other projects. This should be a safe change unless we expect other projects to use the generated geojs website as components within those projects.

This skips installing 10,000 files that total 76 Mb.

When geojs is used as a node module in another project, we should
install all of the website's node modules.  Doing so bloats the
deployment directory of other projects.  This should be a safe change
unless we expect other projects to use the generated geojs website as
components within those projects.

This skips installing 10,000 files that total 76 Mb.
@manthey
Copy link
Contributor Author

manthey commented Dec 7, 2017

@matthewma7 I don't think harms anything.

Copy link

@matthewma7 matthewma7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@manthey Totally, I didn't take that effect of postinstall into consideration. 👍

@manthey manthey merged commit 1ef5a2e into master Dec 7, 2017
@manthey manthey deleted the no-default-website-npm-install branch December 7, 2017 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants