Open shankarsridhar opened 4 years ago
Ya, definitely seems to be a bug. I suspect we are not properly grabbing hte name of the addon from the target package.json
(or index.js
), so we look for a default blueprint named ./some/whatever/addon-name
instead of addon-name
.
Could be closely related to https://github.com/ember-cli/ember-cli/issues/6833.
I am building an ember addon that requires a default blueprint to be run (that is, as part of
ember install <addon-name>
).And I noticed that the default blueprint doesn't run when I use a file path:
ember install <local path to addon folder>
After I publish the addon to the registry, the default blueprint from my addon works as expected - that is, files getting placed in the appropriate path in the consuming ember app.
ember install <addon-name(package.json#name)>
Is this expected ?
Current workaround(I guess I can call it a workaround ?) that I am doing: Add the
"defaultBlueprint:
key under the ember-addon section in thepackage.json
as follows:Thanks to info from source here: https://github.com/ember-cli/ember-cli/blob/master/lib/tasks/addon-install.js#L96
Output from
ember version --verbose && npm --version && yarn --version
: