NPM Scope Support

[thousand]

Right now I don't see anything in the readme about addons that include the NPM scope in the name. ember-cli has enforced that the package and addon name match for a while, and we've been using the moduleName hook in the addon's index.js to override that, mostly for backward compatibility for our consumers. It'd be nice to have the addon namespace match since we use the full package name in other non-addon places. Is there a way to do this currently, or something on the roadmap?

[rwjblue]

Sorry, I don't fully understand the question. Are you saying you'd like to use something like <@org-name/foo$whatever />?

[thousand]

Yup!

[rwjblue]

The issue is mostly with things that are valid to parse in Handlebars, and I believe you cannot use an @ sign in the first position within mustaches and also have arguments.

Specifically, I think this throws a parse error:

{{@something/stuff someArg=“lol”}}

This addon is not currently setup to try to replace handlebars’s internal parser, as it’s chosen syntax that does work in all positions (initially :: and now $).

[thousand]

I'm not necessarily looking specifically for that syntax, just some way to have the organization or scope in the addon namespace. For stuff created internally at linkedin, packages use the @linkedin org/scope, and since ember-cli enforces that addon and package names match, we must include moduleName: () => 'some-addon', in order for it to be findable through the namespaced component syntax. This seems like a missing feature, since orgs/scopes are becoming increasingly common, and an org could be used to logically group parts of a design system.