Skip to content

Current README.md is not reflective of webpack version #1808

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
RedFour opened this issue Aug 22, 2016 · 3 comments
Closed

Current README.md is not reflective of webpack version #1808

RedFour opened this issue Aug 22, 2016 · 3 comments

Comments

@RedFour
Copy link

RedFour commented Aug 22, 2016

The current readme say that the instructions are for webpack:

The current instructions on this file reflect usage for the webpack version.

But when I follow the upgrade instructions:

Updating angular-cli

To update angular-cli to a new version, you must update both the global package and your project's local package.

Global package:

npm uninstall -g angular-cli
npm cache clean
npm install -g angular-cli@latest
Local project package:

rm -rf node_modules dist tmp
npm install --save-dev angular-cli@latest
ng init

It made my project use systemjs

when check the version of the cli:

ng -v

I get angular-cli: 1.0.0-beta.10

I've been using angular-cli@webpack since RC5 was released, and I keep seeing people say that the main branch now uses webpack. And even the readme says it is using webpack. But checking the npm site shows the last published version is still beta.10:

https://www.npmjs.com/package/angular-cli

@ghost
Copy link

ghost commented Aug 23, 2016

Yeah that was confusing to me as well.

@filipesilva
Copy link
Contributor

You're right that doing npm install -g angular-cli@latest will not give you the webpack release. It's not currently marked as latest since we're still ironing out a few kinks.

I understand it's confusing, and recognize that it's a bad thing, but we don't have a good way of having split documentation for beta.10, the webpack version, and the latest master at the same time so... this is what we have right now. The best I can do is to try and get the webpack release out and thus stabilize the readme, and until then explain the situation in issues as it comes up.

@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
clydin pushed a commit to clydin/angular-cli that referenced this issue Aug 29, 2023
With this change we replace the aspnet-engine to use the common engine to fix a number of problems.

1) Injector has already been destroyed. Error: Injector has already been destroyed.
2) Mismatching HTML snapshots.

This does come with a drawback, that we needed to remove `moduleRef` from the `IEngineRenderResult` this however shouldn't cause any problem since this couldn't be used because the platform would have already been destroyed.

Fixes angular#1808
Fixes angular#1404
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants