-
Notifications
You must be signed in to change notification settings - Fork 63
Angular cli beta.31+ breaks playground #11
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
Comments
Hi @isaacplmann! We have a note in the Changelog about this issue. Once Angular CLI goes to |
Thanks for letting me know. It would probably be good to mention this issue in the documentation somewhere too. Or you could just leave this issue open until RC0 drops. |
I was debating on adding it to the docs site but I think this fix is really close to being available (it has been merged into AngularCLI master already). Hopefully that will be on npm soon and I can update the docs to have the instructions on how to use it with the latest version :) |
I'm excited to use angular cli rc.0, but the error still occurs with the latest version. I'm assuming I need to define a separate app with an entry point that references PlaygroundModule instead of AppModule. I'll work in that direction and let you know if I make any progress. |
I got it working and then found your |
I just merged that into master and am working on pushing a release out to npm. Here is a link to the example app for angular cli in the code base that shows how to setup the app in the I will be updating the docs after that to explain the new approach. |
I needed to add |
Published version |
Working for me. Closing. |
With
@angular/[email protected]
or@angular/[email protected]
, when you runangular-playground angular-playground.json
, you get the following error message:Running
npm start
works just fine.I reproduced by taking your
example-app-angular-cli
, updating the@angular/cli
version and runningnpm i && npm run playground
.Thanks.
The text was updated successfully, but these errors were encountered: