-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
check-env for aio should not fail if the check-env for the main angular project fails #17434
Labels
Comments
gkalpak
added a commit
to gkalpak/angular
that referenced
this issue
Jun 14, 2017
gkalpak
added a commit
to gkalpak/angular
that referenced
this issue
Jun 14, 2017
gkalpak
added a commit
to gkalpak/angular
that referenced
this issue
Jun 14, 2017
gkalpak
added a commit
to gkalpak/angular
that referenced
this issue
Jun 14, 2017
gkalpak
added a commit
to gkalpak/angular
that referenced
this issue
Jun 14, 2017
gkalpak
added a commit
to gkalpak/angular
that referenced
this issue
Jun 15, 2017
petebacondarwin
pushed a commit
that referenced
this issue
Jun 16, 2017
petebacondarwin
pushed a commit
that referenced
this issue
Jun 16, 2017
asnowwolf
pushed a commit
to asnowwolf/angular
that referenced
this issue
Aug 11, 2017
juleskremer
pushed a commit
to juleskremer/angular
that referenced
this issue
Aug 28, 2017
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
repro:
cd angular/aio
yarn install
yarn start
expected result:
actual result:
yarn check-env
failsThis failure is because we didn't install npm dependencies in the main project - this error is however irrelevant to what we are trying to do and those dependencies are not at all required for the aio build to work, so we should not require them.
The text was updated successfully, but these errors were encountered: