You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting from version 4.3, ember cli can not find default blueprint for addon if addon is a scoped package (i.e. @scope/addon-name). If I install such addon, ember cli behaves like it does not have default blueprint. If I run ember g @scope/addon-name, it gives Unknown blueprint: @scope/addon-name. Unfortunately I can not provide a specific addon example to reproduce this issue, because it is published to private registry.
Starting from version 4.3, ember cli can not find default blueprint for addon if addon is a scoped package (i.e.
@scope/addon-name
). If I install such addon, ember cli behaves like it does not have default blueprint. If I runember g @scope/addon-name
, it givesUnknown blueprint: @scope/addon-name
. Unfortunately I can not provide a specific addon example to reproduce this issue, because it is published to private registry.The cause of problem is line 1511 of lib/models/blueprint.js, which checks if blueprint name is a path (related PR). Scoped packages contain
/
, which is apath.sep
.The text was updated successfully, but these errors were encountered: