ng build -aot

[x] Bug report [x] Feature request

Current behavior

There is no project in the folder. ng build -aot node_modules appears empty, you may need to run npm install Next, the user will run npm install. As a result: 1.

npm WARN saveError ENOENT: no such file or directory, open '../package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '../package.json'
npm WARN td No description
npm WARN td No repository field.
npm WARN td No README data
npm WARN td No license field.

1. A file will be created package-lock.json. Which will be garbage.

Expected behavior

ng build -aot eg:

1. node_modules not found, you need to create a project ng new <project name> or you may need to run npm install if the project already exists etc.
2. node_modules not found
3. node_modules appears empty

What is the motivation / use case for changing the behavior?

Avoid confusion and run an unnecessary command npm install. In this case

Environment

Angular CLI: 1.6.3, 1.7.4 etc.

For Tooling issues:

• Node version: 8.9.4
• Platform: Linux

Others: npm, debian 9.3

[hansl]

Hi @isopen,

It seems that our detection of a project is wrong. This seems like a real issue.

I think what @netstart was saying is that we don’t support - for long form arguments anymore. Which in your case doesn’t seem to be the issue, but please note that in a project -aot would not work as expected.

Cheers!

[netstart]

try ng build --aot

see ng help build