6.0.0-beta.4 ng eject throws error recommending config.optimization.minimize

[gregbown]

Versions

Angular CLI: 6.0.0-beta.4
Node: 8.9.0
OS: win32 x64
Angular: 6.0.0-beta.6
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Repro steps

• Step 1
  cmd console:

ng eject --target=production --environment prod --aot=true --progress=true --extract-licenses=false -vc -cc -ec -nc --output-hashing=bundles --buildOptimizer

Observed behavior

Fails with error:

webpack.optimize.UglifyJsPlugin has been removed, please use config.optimization.minimize instead.

Desired behavior

Expose updated CLI commands, the ng --help doesn't work
Have eject support the commands even if it is using something else internally

[clydin]

Eject is currently non-functionality in the current 6.0 beta with the transition to Webpack 4. However, work is underway to resolve the issue.

[gregbown]

Hmmm, In 6.0.0-beta.6 The CLI responded
The specified command (eject) is invalid. For a list of available options, run `ng help`.
Is this temporary or moving forward?

[joshwiens]

@gregbown - If you go look in the commands directory, eject no longer exists.

It was removed in #9883

[gregbown]

Got all excited when I saw the eject command was reinstated... but then I read inside...

      The 'eject' command has been temporarily disabled, as it is not yet compatible with the new
      angular.json format. The new configuration format provides further flexibility to modify the
      configuration of your workspace without ejecting. Ejection will be re-enabled in a future
      release of the CLI.

Still, thank you for the clarification and of course everyone's hard work.

[clydin]

eject functionality is no longer available in the latest version (6.x+). For custom webpack configurations the following unofficial add-on is a suggested solution: https://github.com/manfredsteyer/ngx-build-plus

[angular-automatic-lock-bot]

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.}