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

Respect --ignore-engines flag when creating Angular v12 workspace #20050

Closed
1 of 15 tasks
prabh-62 opened this issue Feb 13, 2021 · 3 comments · Fixed by #20051
Closed
1 of 15 tasks

Respect --ignore-engines flag when creating Angular v12 workspace #20050

prabh-62 opened this issue Feb 13, 2021 · 3 comments · Fixed by #20051
Labels
area: angular/cli freq1: low Only reported by a handful of users who observe it rarely severity3: broken type: bug/fix
Milestone

Comments

@prabh-62
Copy link

🐞 Bug report

Command (mark with an x)

  • new
  • build
  • serve
  • test
  • e2e
  • generate
  • add
  • update
  • lint
  • extract-i18n
  • run
  • config
  • help
  • version
  • doc

Is this a regression?

Not applicable

Description

Developers should be able to create angular applications under any node runtime using custom CLI flags

🔬 Minimal Reproduction

❯ npx @angular/cli@12.0.0-next.0 new admin-console --ignore-engines

ng_12_node_15

🔥 Exception or Error


Node.js version v15.8.0 detected.
Odd numbered Node.js versions will not enter LTS status and should not be used for production. For more information, please see https://nodejs.org/en/about/releases/.

🌍 Your Environment


❯ node --version
v15.8.0
❯ yarn --version
1.22.10
❯ npm --version
7.5.0

Anything else relevant?

@clydin
Copy link
Member

clydin commented Feb 13, 2021

That message should actually be a warning. A fix will be available in the next version.
However, the CLI cannot be executed under an arbitrary Node.js version. It requires a minimum set of versions to ensure that the necessary APIs are present and that those APIs provide the expected behavior. The Angular CLI would crash, act erratically, and/or generate invalid output otherwise. For v12, the minimums are either Node.js 12.13 or 14.15; both of which are LTS versions.

@prabh-62
Copy link
Author

I understand the intent. I am just trying to experiment with Angular v12 on another machine and don't want to go through the hassle of uninstalling/installing node runtimes.
I am not going to run this application in production.

@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 Mar 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: angular/cli freq1: low Only reported by a handful of users who observe it rarely severity3: broken type: bug/fix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants