v2 addon by default

[NullVoxPopuli]

No description provided.

[NullVoxPopuli]

of note, ember-cli 5.4 broke the @embroider/addon-blueprint.

So, that's the biggest risk with using an external blueprint with no other changes to process.

The details of flags of how blueprints are created (packageManager in this case vs yarn or npm flags) don't feel exactly like public API, so I'm sure that makes this more complicated.

[NullVoxPopuli]

motivation for having external blueprint, rather than built in to ember-cli?

• easiest to test
• ember-cli's test suite is already quite slow (due to tons of tests)
• can be independently versioned, patched, etc

[NullVoxPopuli]

the addon-blueprint would likely need to test against a range of ember-cli versions, rather than what it does today, which is always use latest.

this would be good to do anyway (today) as it gives us a solid understanding of what is supported.

Afaik, the minimum supported ember-cli must be at least 5.3 for full typescript support -- the v2 addon blueprint has been ahead of ember-cli in this area for a bit, but in 5.3 alignment occurred and we don't want to have incoherence between the v2 addon blueprint and the generated app blueprint that's used for the test-app in the v2 addon blueprint as that is still under ember-cli's control

[NullVoxPopuli]

also, we'll need ember-cli to formally allow blueprints to implement their own flags

[kategengler]

Would like to codify a testing story where Ember used as library without having to have a separate app.