Closed knownasilya closed 6 years ago
Yea, this is a change in the new namespaced packages - they all now define their default blueprint as default
rather than $ADDON_NAME
. I made this change to hopefully reduce potential confusion (default
seems a little clearer, although I'm open to other names - maybe something like post-install
?).
The CLI still needs to be updated to handle the different name, and I think this also exposed a latent bug you are seeing where clobbered blueprints don't get correctly namespaced because it seems like the aren't properly retrieving the addon name.
This code never runs: https://github.com/denali-js/core/blob/master/commands/install.ts#L73
The
blueprints
object doesn't have the record, and eslint and babel are all messed up..Logs:
Here is the
blueprints
object:So it finds the blueprints, but probably adds them incorrectly. Looks like
clobberedBlueprint
(https://github.com/denali-js/cli/blob/master/lib/blueprint.ts#L146) doesn't have anaddon
attribute.The issue is here: https://github.com/denali-js/cli/blob/master/lib/blueprint.ts#L132 The code uses the one with
default
, which doesn't haveaddon
set.@davewasmer