Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update app/addon blueprints to ember-auto-import@2 #9623

Merged
merged 1 commit into from Sep 15, 2021

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Sep 15, 2021

Quick Summary of Breaking Changes

  • apps that have custom webpack config will need to check that their config is compatible with webpack 5
  • apps must add webpack to their own dependencies (yarn add --dev webpack@5 or npm install --save-dev webpack@5)
  • apps that were adding css handling (like css-loader, style-loader, and MiniCSSExtraPlugin) to the webpack config must remove those, because they're now included by default for compatibility with the embroider v2 package spec.
  • apps should confirm that their deployment strategy includes all files produced under dist (not just the traditional expected ones like dist/assets/your-app.js and dist/assets/vendor.js)
  • apps that use fingerprint.prepend to move their assets to a different origin will also need to set autoImport.publicAssetURL. See example below.
  • addons that upgrade to ember-auto-import >= 2 will only work in apps that have ember-auto-import >= 2, so they should do their own semver major releases when they upgrade
  • our alias option has changed slightly to align better with how it works in webpack
  • we dropped support for node < 12 and ember-source < 3.4 and ember-cli < 3.4.

For more details read the 2.0 upgrading guide here:

https://github.com/ef4/ember-auto-import/blob/main/docs/upgrade-guide-2.0.md

Quick Summary of Breaking Changes
---------------------------------

- apps that have custom webpack config will need to check that their config is compatible with webpack 5
- apps must add webpack to their own dependencies (`yarn add --dev webpack@5` or `npm install --save-dev webpack@5`)
- apps that were adding css handling (like `css-loader`, `style-loader`, and `MiniCSSExtraPlugin`) to the webpack config must remove those, because they're now included by default for compatibility with the embroider v2 package spec.
- apps should confirm that their deployment strategy includes all files produced under `dist` (not just the traditional expected ones like `dist/assets/your-app.js` and `dist/assets/vendor.js`)
- apps that use `fingerprint.prepend` to move their assets to a different origin will also need to set `autoImport.publicAssetURL`. See example below.
- addons that upgrade to ember-auto-import >= 2 will only work in apps that have ember-auto-import >= 2, so they should do their own semver major releases when they upgrade
- our `alias` option has changed slightly to align better with how it works in webpack
- we dropped support for node < 12 and ember-source < 3.4 and ember-cli < 3.4.

For more details read the 2.0 upgrading guide here:

https://github.com/ef4/ember-auto-import/blob/main/docs/upgrade-guide-2.0.md
@rwjblue rwjblue merged commit d52d9a6 into master Sep 15, 2021
@rwjblue rwjblue deleted the update-ember-auto-import branch September 15, 2021 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants