[QUEST] v8 Release

[bertdeblock]

• Move @babel/core to peerDependencies - Move @babel/core to peerDependencies to resolve peer dependency warnings and errors #452
• Drop support for Node v6, v8, v10 and v12 (Add support for Node v14, v16 and v18) - Drop support for Node < v14 and add support for Node v16 and v18 #454
• Remove includePolyfill support - Drop support for the includePolyfill option #458
• Change broccoli-babel-transpiler to either make @babel/core a peer dependency or make it accept the current Babel as an argument, and upgrade ember-cli-babel to that version (without this we're still not actually transpiling people's code with the version of @babel/core in their own package.json) - Move @babel/core to peerDependencies to resolve peer dependency warnings and errors babel/broccoli-babel-transpiler#221
• Update broccoli-babel-transpiler to v8 - Update broccoli-babel-transpiler to v8.0.0-beta.1 #460
• Write upgrade guide for apps and addons - Add upgrading to v8 guide #464
• Release first v8 beta version
• Release a stable version of broccoli-babel-transpiler v8 and update in ember-cli-babel - Update broccoli-babel-transpiler to v8 #494
• Release a stable version of ember-cli-babel v8
• Update ember-cli-babel in the default blueprint and add @babel/core - [ENHANCEMENT] Update ember-cli-babel to v8 in app and addon blueprints ember-cli/ember-cli#10141

[kategengler]

from @rwjblue in Discord

rwjblue — 09/16/2022
Agree
There’s a non trivial amount of cleanup we should do though
Like bumping the broccoli-Babel-transpiler version
Changing poly fill support around (removing it basically)

[ef4]

Also just noticed that broccoli-babel-transpiler has @babel/core in dependencies. That means we should also change and release broccoli-babel-transpiler to either use a peerDep or accept babel itself as an argument when you create the broccoli node.

[ef4]

(I can't edit the description above, so I'm rewriting it here with updates.)

• move @babel/core to peerDependencies Move @babel/core to peerDependencies to resolve peer dependency warnings and errors #452
• drop support for node < 14 and add test coverage for 14 through 18
• remove includePolyfill support
• change broccoli-babel-transpiler to either make @babel/core a peerDep or make it accept the current Babel as an argument, and upgrade ember-cli-babel to that version. (Without this we're still not actually transpiling people's code with the version of @babel/core in their own package.json.)

[bertdeblock]

@ef4 For the broccoli-babel-transpiler update, which option do you prefer / is best in this case?

[bertdeblock]

Also, does includePolyfill support need to be dropped without a replacement?

[bertdeblock]

Created PRs for the remaining issues. Hope I understood everything correctly 😄.

Probably need some guidance on the "Remove includePolyfill support" issue.

[ef4]

Also, does includePolyfill support need to be dropped without a replacement?

babel has deprecated the polyfill and tells you the replacement is to add import "core-js/stable" yourself: https://babeljs.io/docs/en/babel-polyfill

This probably belongs in changelog and in any how-to-upgrade doc that we may write for this major release.

[rwjblue]

I released https://github.com/babel/broccoli-babel-transpiler/releases/tag/v8.0.0-beta.1 so we can start updating here a bit easier

[bertdeblock]

👍 I'll try to fix the broccoli-babel-transpiler update here asap.

[ef4]

We're going to need to document what addon authors are supposed to do. They traditionally must have ember-cli-babel in dependencies and therefore they bring their own babel into app builds. The way to reproduce that after this change is for addons to @babel/core in dependencies. But it's probably better for them to put it into peerDependencies (and devDependencies).

[bertdeblock]

After the transpiler PR, I can look into writing an upgrade guide for apps and addons.

[ef4]

I said about "it's probably better for them to put it into peerDependencies", but after thinking about it, the less disruptive change is to put @babel/core into dependencies. That is equivalent to how things already worked, with every addon potentially bringing its own babel. We don't need to rock that boat any harder, the longer-term plan is for them to get to v2 addons and then they don't bring ember-cli-babel at all.

[JackHowa]

Excited to see babel polyfills removed 👍

[bertdeblock]

v8 is released.

[ef4]

Thank you @bertdeblock!