Skip to content

Tracking: Lower Install Time. #3199

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

Closed
2 of 5 tasks
hansl opened this issue Nov 18, 2016 · 5 comments
Closed
2 of 5 tasks

Tracking: Lower Install Time. #3199

hansl opened this issue Nov 18, 2016 · 5 comments
Assignees
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful

Comments

@hansl
Copy link
Contributor

hansl commented Nov 18, 2016

  • Fork CompressionPlugin and remove Zopfli dependency.
  • Make Sass Loader not directly depend on node-sass and install it only if/when needed.
  • Remove direct dependency to protractor and show error message when ng e2e is run but protractor isn't in node modules.
  • Remove direct dependency on karma and show an error message when ng test is run but karma isn't in node modules.
  • Drop bootstrapping time down to under 1 seconds on Travis (or in e2e in general).
@hansl hansl self-assigned this Nov 18, 2016
@hansl
Copy link
Contributor Author

hansl commented Dec 6, 2016

Forking CompressionPlugin happened in #3414.

@hansl
Copy link
Contributor Author

hansl commented Dec 16, 2016

Cleaned up the package json and made a script to make sure we always depends on the exact dependencies, not more or less.

hansl added a commit to hansl/angular-cli that referenced this issue Dec 19, 2016
hansl added a commit to hansl/angular-cli that referenced this issue Dec 21, 2016
hansl added a commit that referenced this issue Dec 21, 2016
@filipesilva filipesilva added the P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful label Dec 29, 2016
@Bulan
Copy link

Bulan commented Jan 24, 2017

I was about to create a new issue about not able to install since node-gyp requirement requires the server to access something other than npmjs.com (which our build server is locked down to only allow access to).

But found this #3428 the lead me here, so how far along is the "remove sass loader", any ETA since it seems to be next on the list?

@hansl
Copy link
Contributor Author

hansl commented Feb 3, 2017

Closing this as done;

  1. we will not remove dependencies on protractor and karma before 1.0
  2. the sass-loader plugin is useful for most people and the main users having problems (Chinese developers behind the firewall) can now use cnpm to install.

The install time went down significantly, and we have support for yarn as well which reduces further time.

@hansl hansl closed this as completed Feb 3, 2017
MRHarrison pushed a commit to MRHarrison/angular-cli that referenced this issue Feb 9, 2017
MRHarrison pushed a commit to MRHarrison/angular-cli that referenced this issue Feb 9, 2017
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful
Projects
None yet
Development

No branches or pull requests

3 participants