You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/upgrade-guide-2.0.md
+3-2
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,7 @@
8
8
- 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`)
9
9
- 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
10
10
- our `alias` option has changed slightly to align better with how it works in webpack
11
+
- we dropped support for node < 12 and ember-source < 3.4 and ember-cli < 3.4.
11
12
12
13
# Details
13
14
@@ -21,9 +22,9 @@ One of the changes in webpack 5 is the removal of automatic node polyfills, but
21
22
22
23
Apps are required to depend on webpack. This gives the app control over the exact webpack version in use, and it makes it possible for the app to import directly from webpack for access to features like `DefinePlugin` that it may want to put into the webpack config.
23
24
24
-
Addons that use ember-auto-import 2.0 should *not* put webpack into `dependencies` (the app's version will be used instead). They will need it in `devDependencies` in order to build their own dummy app.
25
+
Addons that use ember-auto-import 2.0 should _not_ put webpack into `dependencies` (the app's version will be used instead). They will need it in `devDependencies` in order to build their own dummy app.
25
26
26
-
ember-auto-import will not list webpack in `peerDependencies`, because the ember-auto-import package does double duty -- it needs webpack when used by an app, but does *not* need webpack when used by an addon, and we don't want addons to accidentally install webpack.
27
+
ember-auto-import will not list webpack in `peerDependencies`, because the ember-auto-import package does double duty -- it needs webpack when used by an app, but does _not_ need webpack when used by an addon, and we don't want addons to accidentally install webpack.
0 commit comments