Unable to register options for the new command w/ non-default blueprints

[pittst3r]

When I do:

$ ember new hello-wc --web-component -b @glimmer/blueprint

I get the warning:

The option '--web-component' is not registered with the new command. Run `ember new --help` for a list of supported options.

But the option still gets passed into the blueprint and it still works.

Basically the following is not a thing you can do with the new command:

availableOptions: [
  {
    name: 'web-component',
    type: Boolean
  }
]

cc @tomdale

---

Output from ember version --verbose && npm --version:

ember-cli: 2.13.0-beta.3
http_parser: 2.7.0
node: 6.9.2
v8: 5.1.281.88
uv: 1.9.1
zlib: 1.2.8
ares: 1.10.1-DEV
icu: 57.1
modules: 48
openssl: 1.0.2j
os: darwin x64
3.10.9

[rwjblue]

Thanks for reporting!

[tomdale]

I suspect there are a number of options we may eventually want to expose when creating a new app, such as JavaScript or TypeScript.

Has there been any discussion about an interactive prompt addons could offer to walk users through the choices? At a certain point a few targeted questions for frequent options is a better user experience than a big list of options people have to dig through.

[kellyselden]

Has there been any discussion about an interactive prompt addons could offer to walk users through the choices? At a certain point a few targeted questions for frequent options is a better user experience than a big list of options people have to dig through.

cc @seawatts

[Turbo87]

Has there been any discussion about an interactive prompt addons could offer to walk users through the choices?

I might be wrong, but I think this should be possible already using something like this.ui.prompt() in the e.g. beforeInstall hook