Ng serve fails with Yarn and the -ng4 flag

[Ionaru]

OS?

Lubuntu 16.10

Versions.

@angular/cli: 1.0.0-beta.32.3
node: 7.5.0
os: linux x64

Repro steps. (On a clean VM)

sudo yarn global add @angular/cli
ng set --global packageManager=yarn
ng new MyYarnApp -ng4
cd MyYarnApp
ng serve or ng build

or

sudo yarn global add @angular/cli
ng new MyYarnApp -ng4 --skip-install
cd MyYarnApp
yarn
ng serve or ng build

The log given by the failure.

** NG Live Development Server is running on http://localhost:4200. **
Hash: 431dce9b2028dcad96e7                                                               
Time: 7586ms
chunk    {0} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 155 kB {4} [initial] [rendered]
chunk    {1} main.bundle.js, main.bundle.js.map (main) 3.72 kB {3} [initial] [rendered]
chunk    {2} styles.bundle.js, styles.bundle.js.map (styles) 10.1 kB {4} [initial] [rendered]
chunk    {3} vendor.bundle.js, vendor.bundle.js.map (vendor) 2.76 MB [initial] [rendered]
chunk    {4} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered]

ERROR in Could not resolve module @angular/core/src/di/opaque_token
webpack: Failed to compile.

Mention any other details that might be useful.

This seems to be a combination of installing packages with Yarn, and using Angular 4

[Meligy]

This is a duplicate of #4611

Look at #4611 (comment) or #4781 for a workaround.

[Ionaru]

I can confirm that changing the Angular versions in the package.json works.
>=4.0.0-beta <5.0.0 changed to >=next <5.0.0

Edit: This installs Angular 2 instead of 4

[Meligy]

Run ng version to be sure again.
It turned out it actually installed ng2 not ng4 :(

[Meligy]

But then again maybe following #4611 (comment) literally works. I'll be trying this later.

[jwuliger]

@Ionaru Brilliant! This worked for me. Thanks so much!

[jwuliger]

Well I spoke to soon. Meh. @Meligy you are correct. The above change to package.json results in a NG2 install.

[Ionaru]

@Meligy you are correct, it does use Angular 2 with that change. My bad.

I don't think using npm link is the right solution for this issue, however it can be a temporary workaround.

[victornoel]

For those interested, I posted a clean workaround for this problem in #4611 (comment).

[filipesilva]

Dupe of #4611

[angular-automatic-lock-bot]

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.}