addon-blueprint
addon-blueprint copied to clipboard
embroider-build
Blueprint for v2-formatted Ember addons
On a similar note as #193, should we extends `keepAssets` to more than just CSS? Thinking of importing static assets like images, which people can do with some custom webpack...
Tried to update a v2 adodn created with the 1.3 version of this blueprint to the latest 1.4, using `npx ember-cli-update`. Which gave this error output: ``` Error creating new...
Currently using old @types/ packages
When adding the addon created via the blueprint as a dependency in the package.json file using the form: `"addon-name": "https://github.com/name/repo-name#dist` Yarn complains with the following error: ``` Packing addon-name@https://github.com/name/repo.git#commit=commitSha from...
Releasing v2 addon is not entirely trivial, so would be good to have a way to tell folks how to do this. ```sh cd my-addon-git-repo cd my-addon # because v2...
I've been using `publint` and`@arethetypeswrong/cli` on a couple repos, and it's helpful for catching common footguns these can be added to the concurrently` lint command in the addon package to...
When using dependenciesMeta.*.injected (ie: the most correct way to manage in-repo dependencies, as it simulates what would happen when installed from npm), you need a too like this: https://github.com/NullVoxPopuli/pnpm-sync-dependencies-meta-injected _however_...
https://github.com/tmux/tmux This could be a more ergonomic alternative to our _involved_ concurrently (sub)commands. It could also be worse -- regardless, documented why, the tradeoffs, etc would be valuable
To make things "easiest by default", while still also allowing for the correctness for power-users today, I'd like to propose we (eventually): - make the blueprint output a uni-repo by...
in an addon, ``` . ├─┬ @glint/environment-ember-loose 0.9.7 │ ├── ✕ missing peer @glimmer/component@^1.1.2 │ ├── ✕ missing peer ember-cli-htmlbars@^6.0.1 │ └─┬ @glint/template 0.9.7 │ └── ✕ missing peer @glimmer/component@^1.1.2...