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

ng update migrations not working on npm linked custom schematics #15511

Closed
bmayen opened this issue Sep 3, 2019 · 1 comment
Closed

ng update migrations not working on npm linked custom schematics #15511

bmayen opened this issue Sep 3, 2019 · 1 comment
Labels
area: @angular/cli freq1: low Only reported by a handful of users who observe it rarely severity3: broken type: bug/fix
Milestone

Comments

@bmayen
Copy link

bmayen commented Sep 3, 2019

🐞 Bug report

Command (mark with an x)

- [x] update

Description

I have custom schematics to generate a new application using ng new -c my-custom-schematics. I am attempting to add migrations so I can update my applications when the schematics are updated, using ng update my-custom-schematics. During development of these migrations, if I npm link my-custom-schematics in the generated application and run ng update my-custom-schematics --migrate-only --from=1 I receive the error "Package found in package.json but is not installed." If I copy the package to the application's node_modules folder, it works fine. The problem only arises using npm link.

🔬 Minimal Reproduction

  1. Generate a new application using custom schematics.
  2. Update the schematic to include migrations to a new version.
  3. npm link the application to the new version of the schematics
  4. Run ng update my-custom-schematics --migrate-only --from=1

🔥 Exception or Error


Package found in package.json but is not installed.

Anything else relevant?

Not receiving the error if I copy the package to the application's node_modules folder. Only occurs if the schematics package is npm linked.

@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 Oct 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: @angular/cli freq1: low Only reported by a handful of users who observe it rarely severity3: broken type: bug/fix
Projects
None yet
Development

No branches or pull requests

2 participants