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

Adding a dependency with yarn while serving the app breaks ngcc generated files import #16397

Closed
1 of 15 tasks
yjaaidi opened this issue Dec 9, 2019 · 1 comment · Fixed by #16424
Closed
1 of 15 tasks

Comments

@yjaaidi
Copy link
Contributor

yjaaidi commented Dec 9, 2019

🐞 Bug report

Command (mark with an x)

  • new
  • build
  • serve
  • test
  • e2e
  • generate
  • add
  • update
  • lint
  • xi18n
  • run
  • config
  • help
  • version
  • doc

Is this a regression?

Yes, the previous version in which this bug was not present was: 8.2.14

Description

When running Angular 9 with ng serve then installing a dependency with yarn, yarn will overwrite angular dependencies' package.json files and remove __ivy_ngcc__ files generated by ngcc when ng serve starts.
This produces an error on ng serve as it can't find IVy generated files like ./node_modules/@angular/core/__ivy_ngcc__/fesm2015/core.js

Maybe ng serve could watch for these files and rebuild them if they disappear?

🔥 Exception or Error


ERROR in ./node_modules/@angular/core/__ivy_ngcc__/fesm2015/core.js
Module build failed: Error: ENOENT: no such file or directory, open '/Users/r/Desktop/demo/node_modules/@angular/core/__ivy_ngcc__/fesm2015/core.js'
@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 Jan 13, 2020
ikjelle pushed a commit to ikjelle/angular-cli that referenced this issue Mar 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.