V2 package RFCs checklist

[ef4]

Published RFCs:

• proposed: v2 addon format base spec (v2 Addon Format (Embroider compatibility) emberjs/rfcs#507)

TODO list of additional features that need to get specified in follow RFCs:

• providing dev middleware
• providing commands and blueprints
• preprocessing your parent package's code
• modifying your parent package's babel config
• injecting content into index.html (contentFor)
• accessing the app's configured browser targets from an addon's build file
• auto-import control
  - alias
  - skipBabel
  - how can a library like moment avoid packaging all locales?
  - indirect aliasing that lets you take into account custom fields in package.json
  - alias to empty

[NullVoxPopuli]

Should we re-purpose this ticket as a quest issue for when V2 addons are "production ready"?
Maybe pin the issue?

Building V2 Addons

• Add tests for @embroider/addon-dev
• V2 Addons: cannot import template-only components #1121
  • Fix importing of template-only components in V2 addons #1126
• Solve ts related double setComponentTemplate #1134
• Add typecsript sample rollup config + exploration of different plugins' side-effects #1099
• Iterate on https://github.com/embroider-build/addon-blueprint
  • TypeScript?
  • Interactive? (Monorepo layout, etc (at the time of writing this generates a different structure from the addon-migrator))
  • publish to npm
• Iterate on https://github.com/NullVoxPopuli/ember-addon-migrator
  • Figure out if porting every little detail is worth it, or if replacing is needed in same cases? Can aspects of little details, such as CI config, be transformed?
• [V2 Addons] Lint against importing test-support ember-cli/eslint-plugin-ember#1437
• Add rollup plugin that verifies and fixes the package.json (or other files) #1212

ember-cli integration

• generators

Testing V2 Addons

• add --no-monorepo flag to blueprint
  • example: https://github.com/ember-cli/ember-welcome-page/
  • potentially also "bottled ember" - @mansona

Documenting "somewhere" on emberjs.com

• Write authoring guide
  • mention monorepo vs non-monorepo, tradeoffs (bottled ember, should it exist, would eliminate some or all of those tradeoffs)
  • PR to cli.emberjs.com
  • Be sure to flag as "Polaris feature" if all of this is ready way before Polaris lands.
• section on build-time augmentations
  • using cross-packager plugins (for maximum compatibility)
    • e.g.: https://github.com/unjs/unplugin