--dev option not working in Angular CLI

Question

Recently I upgraded to Angular CLI 6.0.3. My previous build script was

"build": "ng build --output-path ../public/ui", which worked fine and generated files

/ui/inline.bundle.js”. /ui/polyfills.bundle.js”. /ui/vendor.bundle.js”. /ui/styles.bundle.js”. /ui/main.bundle.js”

I notice that after upgrade, the files been generated have different names

main.js polyfills.js runtime.js styles.js vendor.js

I thought that maybe the default build is prod so I changed my script to "build": "ng build --dev --output-path ../public/ui",

but I get error Unknown option: '--dev'

What am I doing wrong? Have the generated file name changed in v6?

Thanks. Happy to accept your answer if you'll like to convert you comment to an answer. — Manu Chadha
– Manu Chadha, Commented May 24, 2018 at 9:49
ng build uses dev by default. But you can change the build target like so: "build:stage": "ng build --configuration=stage". For more see angular.io/guide/workspace-config — Ben Racicot
– Ben Racicot, Commented Sep 25, 2021 at 16:03

David · Accepted Answer · 2018-05-24 09:55:14Z

2

Yes they have changed the names of the generated bundles.

Angular cli v 1.7

node_modules/@angular/cli/models/webpack-configs/common.js

output: {
        path: path.resolve(buildOptions.outputPath),
        publicPath: buildOptions.deployUrl,
        filename: `[name]${hashFormat.chunk}.bundle.js`,
        chunkFilename: `[id]${hashFormat.chunk}.chunk.js`
    }

Angular cli v6

node_modules/@angular-devkit/build-angular/src/angular-cli-files/models/webpack-configs/common.js

output: {
        path: path.resolve(root, buildOptions.outputPath),
        publicPath: buildOptions.deployUrl,
        filename: `[name]${hashFormat.chunk}.js`,
    },

And dev is the default mode when using ng build AFAIK

answered May 24, 2018 at 9:55

David

34.6k13 gold badges90 silver badges124 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Rafael Over a year ago

So what is the solution.. ?

Wilt Over a year ago

@Rafael Run ng build or run ng build --configuration=dev

Collectives™ on Stack Overflow

--dev option not working in Angular CLI

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related