Skip to content

fix(install): ng install should work with local npm package archives #188

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
jeffbcross opened this issue Feb 11, 2016 · 2 comments
Closed

Comments

@jeffbcross
Copy link
Contributor

In order to test packages locally, it'd be nice to run: ng install some-local-package.tar.gz. Though npm install succeeds with this method, the install process is treating "some-local-package.tar.gz" as the package name, which causes later steps of ng install to fail. Instead, ng install should parse the name from package.json after the package is installed.

@hansl
Copy link
Contributor

hansl commented Mar 18, 2016

We're going to use npm directly in ng install. Closing this as this will be addressed. Once ng install is done we can revisit this.

@hansl hansl closed this as completed Mar 18, 2016
@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 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants