Remove stage presets from the monorepo (#11101)
babel/babel-archive already includes the last working version of these presets (v7.0.0-beta.52), and they have been throwing since 7.0.0
This commit is contained in:
Nicolò Ribaudo
GitHub
parent
755ec192e2
commit
5e58903250
@ -1,3 +0,0 @@
|
||||
src
|
||||
test
|
||||
*.log
|
||||
@ -1,65 +0,0 @@
|
||||
# @babel/preset-stage-0
|
||||
|
||||
As of v7.0.0-beta.55, we've removed Babel's Stage presets. Please consider reading our [blog post](https://babeljs.io/blog/2018/07/27/removing-babels-stage-presets) on this decision for more details. TL;DR is that it's more beneficial in the long run to explicitly add which proposals to use.
|
||||
|
||||
---
|
||||
|
||||
For a more automatic migration, we have updated [babel-upgrade](https://github.com/babel/babel-upgrade) to do this for you (you can run `npx babel-upgrade`).
|
||||
|
||||
If you want the same configuration as before:
|
||||
|
||||
```jsonc
|
||||
{
|
||||
"plugins": [
|
||||
// Stage 0
|
||||
"@babel/plugin-proposal-function-bind",
|
||||
|
||||
// Stage 1
|
||||
"@babel/plugin-proposal-export-default-from",
|
||||
"@babel/plugin-proposal-logical-assignment-operators",
|
||||
["@babel/plugin-proposal-optional-chaining", { "loose": false }],
|
||||
["@babel/plugin-proposal-pipeline-operator", { "proposal": "minimal" }],
|
||||
["@babel/plugin-proposal-nullish-coalescing-operator", { "loose": false }],
|
||||
"@babel/plugin-proposal-do-expressions",
|
||||
|
||||
// Stage 2
|
||||
["@babel/plugin-proposal-decorators", { "legacy": true }],
|
||||
"@babel/plugin-proposal-function-sent",
|
||||
"@babel/plugin-proposal-export-namespace-from",
|
||||
"@babel/plugin-proposal-numeric-separator",
|
||||
"@babel/plugin-proposal-throw-expressions",
|
||||
|
||||
// Stage 3
|
||||
"@babel/plugin-syntax-dynamic-import",
|
||||
"@babel/plugin-syntax-import-meta",
|
||||
["@babel/plugin-proposal-class-properties", { "loose": true }],
|
||||
"@babel/plugin-proposal-json-strings"
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
If you're using the same configuration across many separate projects,
|
||||
keep in mind that you can also create your own custom presets with
|
||||
whichever plugins and presets you're looking to use.
|
||||
|
||||
```js
|
||||
module.exports = function() {
|
||||
return {
|
||||
plugins: [
|
||||
require("@babel/plugin-syntax-dynamic-import"),
|
||||
[require("@babel/plugin-proposal-decorators"), { "legacy": true }],
|
||||
[require("@babel/plugin-proposal-class-properties"), { "loose": true }],
|
||||
],
|
||||
presets: [
|
||||
// ...
|
||||
],
|
||||
};
|
||||
};
|
||||
```
|
||||
|
||||
**NOTE: Compatibility between `@babel/plugin-proposal-class-properties` and `@babel/plugin-proposal-decorators`**
|
||||
If you are including your plugins manually and using `@babel/plugin-proposal-class-properties`, make sure that `@babel/plugin-proposal-decorators` comes before `@babel/plugin-proposal-class-properties`.
|
||||
|
||||
When using the `legacy: true` option of `@babel/plugin-proposal-decorators`, `@babel/plugin-proposal-class-properties` must be used in `loose: true` mode.
|
||||
|
||||
If you are not using `@babel/plugin-proposal-decorators`, `loose` mode is not needed.
|
||||
@ -1,13 +0,0 @@
|
||||
{
|
||||
"name": "@babel/preset-stage-0",
|
||||
"version": "7.8.3",
|
||||
"description": "Babel preset for stage 0 plugins",
|
||||
"author": "Sebastian McKenzie <sebmck@gmail.com>",
|
||||
"homepage": "https://babeljs.io/",
|
||||
"license": "MIT",
|
||||
"publishConfig": {
|
||||
"access": "public"
|
||||
},
|
||||
"repository": "https://github.com/babel/babel/tree/master/packages/babel-preset-stage-0",
|
||||
"main": "lib/index.js"
|
||||
}
|
||||
@ -1,60 +0,0 @@
|
||||
export default function() {
|
||||
throw new Error(`
|
||||
As of v7.0.0-beta.55, we've removed Babel's Stage presets.
|
||||
Please consider reading our blog post on this decision at
|
||||
https://babeljs.io/blog/2018/07/27/removing-babels-stage-presets
|
||||
for more details. TL;DR is that it's more beneficial in the
|
||||
long run to explicitly add which proposals to use.
|
||||
|
||||
For a more automatic migration, we have updated babel-upgrade,
|
||||
https://github.com/babel/babel-upgrade to do this for you with
|
||||
"npx babel-upgrade".
|
||||
|
||||
If you want the same configuration as before:
|
||||
|
||||
{
|
||||
"plugins": [
|
||||
// Stage 0
|
||||
"@babel/plugin-proposal-function-bind",
|
||||
|
||||
// Stage 1
|
||||
"@babel/plugin-proposal-export-default-from",
|
||||
"@babel/plugin-proposal-logical-assignment-operators",
|
||||
["@babel/plugin-proposal-optional-chaining", { "loose": false }],
|
||||
["@babel/plugin-proposal-pipeline-operator", { "proposal": "minimal" }],
|
||||
["@babel/plugin-proposal-nullish-coalescing-operator", { "loose": false }],
|
||||
"@babel/plugin-proposal-do-expressions",
|
||||
|
||||
// Stage 2
|
||||
["@babel/plugin-proposal-decorators", { "legacy": true }],
|
||||
"@babel/plugin-proposal-function-sent",
|
||||
"@babel/plugin-proposal-export-namespace-from",
|
||||
"@babel/plugin-proposal-numeric-separator",
|
||||
"@babel/plugin-proposal-throw-expressions",
|
||||
|
||||
// Stage 3
|
||||
"@babel/plugin-syntax-dynamic-import",
|
||||
"@babel/plugin-syntax-import-meta",
|
||||
["@babel/plugin-proposal-class-properties", { "loose": false }],
|
||||
"@babel/plugin-proposal-json-strings"
|
||||
]
|
||||
}
|
||||
|
||||
If you're using the same configuration across many separate projects,
|
||||
keep in mind that you can also create your own custom presets with
|
||||
whichever plugins and presets you're looking to use.
|
||||
|
||||
module.exports = function() {
|
||||
return {
|
||||
plugins: [
|
||||
require("@babel/plugin-syntax-dynamic-import"),
|
||||
[require("@babel/plugin-proposal-decorators"), { "legacy": true }],
|
||||
[require("@babel/plugin-proposal-class-properties"), { "loose": false }],
|
||||
],
|
||||
presets: [
|
||||
// ...
|
||||
],
|
||||
};
|
||||
};
|
||||
`);
|
||||
}
|
||||
@ -1,3 +0,0 @@
|
||||
src
|
||||
test
|
||||
*.log
|
||||
@ -1,62 +0,0 @@
|
||||
# @babel/preset-stage-1
|
||||
|
||||
As of v7.0.0-beta.55, we've removed Babel's Stage presets. Please consider reading our [blog post](https://babeljs.io/blog/2018/07/27/removing-babels-stage-presets) on this decision for more details. TL;DR is that it's more beneficial in the long run to explicitly add which proposals to use.
|
||||
|
||||
---
|
||||
|
||||
For a more automatic migration, we have updated [babel-upgrade](https://github.com/babel/babel-upgrade) to do this for you (you can run `npx babel-upgrade`).
|
||||
|
||||
If you want the same configuration as before:
|
||||
|
||||
```jsonc
|
||||
{
|
||||
"plugins": [
|
||||
// Stage 1
|
||||
"@babel/plugin-proposal-export-default-from",
|
||||
"@babel/plugin-proposal-logical-assignment-operators",
|
||||
["@babel/plugin-proposal-optional-chaining", { "loose": false }],
|
||||
["@babel/plugin-proposal-pipeline-operator", { "proposal": "minimal" }],
|
||||
["@babel/plugin-proposal-nullish-coalescing-operator", { "loose": false }],
|
||||
"@babel/plugin-proposal-do-expressions",
|
||||
|
||||
// Stage 2
|
||||
["@babel/plugin-proposal-decorators", { "legacy": true }],
|
||||
"@babel/plugin-proposal-function-sent",
|
||||
"@babel/plugin-proposal-export-namespace-from",
|
||||
"@babel/plugin-proposal-numeric-separator",
|
||||
"@babel/plugin-proposal-throw-expressions",
|
||||
|
||||
// Stage 3
|
||||
"@babel/plugin-syntax-dynamic-import",
|
||||
"@babel/plugin-syntax-import-meta",
|
||||
["@babel/plugin-proposal-class-properties", { "loose": true }],
|
||||
"@babel/plugin-proposal-json-strings"
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
If you're using the same configuration across many separate projects,
|
||||
keep in mind that you can also create your own custom presets with
|
||||
whichever plugins and presets you're looking to use.
|
||||
|
||||
```js
|
||||
module.exports = function() {
|
||||
return {
|
||||
plugins: [
|
||||
require("@babel/plugin-syntax-dynamic-import"),
|
||||
[require("@babel/plugin-proposal-decorators"), { "legacy": true }],
|
||||
[require("@babel/plugin-proposal-class-properties"), { "loose": false }],
|
||||
],
|
||||
presets: [
|
||||
// ...
|
||||
],
|
||||
};
|
||||
};
|
||||
```
|
||||
|
||||
**NOTE: Compatibility between `@babel/plugin-proposal-class-properties` and `@babel/plugin-proposal-decorators`**
|
||||
If you are including your plugins manually and using `@babel/plugin-proposal-class-properties`, make sure that `@babel/plugin-proposal-decorators` comes before `@babel/plugin-proposal-class-properties`.
|
||||
|
||||
When using the `legacy: true` option of `@babel/plugin-proposal-decorators`, `@babel/plugin-proposal-class-properties` must be used in `loose: true` mode.
|
||||
|
||||
If you are not using `@babel/plugin-proposal-decorators`, `loose` mode is not needed.
|
||||
@ -1,13 +0,0 @@
|
||||
{
|
||||
"name": "@babel/preset-stage-1",
|
||||
"version": "7.8.3",
|
||||
"description": "Babel preset for stage 1 plugins",
|
||||
"author": "Sebastian McKenzie <sebmck@gmail.com>",
|
||||
"homepage": "https://babeljs.io/",
|
||||
"license": "MIT",
|
||||
"publishConfig": {
|
||||
"access": "public"
|
||||
},
|
||||
"repository": "https://github.com/babel/babel/tree/master/packages/babel-preset-stage-1",
|
||||
"main": "lib/index.js"
|
||||
}
|
||||
@ -1,57 +0,0 @@
|
||||
export default function() {
|
||||
throw new Error(`
|
||||
As of v7.0.0-beta.55, we've removed Babel's Stage presets.
|
||||
Please consider reading our blog post on this decision at
|
||||
https://babeljs.io/blog/2018/07/27/removing-babels-stage-presets
|
||||
for more details. TL;DR is that it's more beneficial in the
|
||||
long run to explicitly add which proposals to use.
|
||||
|
||||
For a more automatic migration, we have updated babel-upgrade,
|
||||
https://github.com/babel/babel-upgrade to do this for you with
|
||||
"npx babel-upgrade".
|
||||
|
||||
If you want the same configuration as before:
|
||||
|
||||
{
|
||||
"plugins": [
|
||||
// Stage 1
|
||||
"@babel/plugin-proposal-export-default-from",
|
||||
"@babel/plugin-proposal-logical-assignment-operators",
|
||||
["@babel/plugin-proposal-optional-chaining", { "loose": false }],
|
||||
["@babel/plugin-proposal-pipeline-operator", { "proposal": "minimal" }],
|
||||
["@babel/plugin-proposal-nullish-coalescing-operator", { "loose": false }],
|
||||
"@babel/plugin-proposal-do-expressions",
|
||||
|
||||
// Stage 2
|
||||
["@babel/plugin-proposal-decorators", { "legacy": true }],
|
||||
"@babel/plugin-proposal-function-sent",
|
||||
"@babel/plugin-proposal-export-namespace-from",
|
||||
"@babel/plugin-proposal-numeric-separator",
|
||||
"@babel/plugin-proposal-throw-expressions",
|
||||
|
||||
// Stage 3
|
||||
"@babel/plugin-syntax-dynamic-import",
|
||||
"@babel/plugin-syntax-import-meta",
|
||||
["@babel/plugin-proposal-class-properties", { "loose": false }],
|
||||
"@babel/plugin-proposal-json-strings"
|
||||
]
|
||||
}
|
||||
|
||||
If you're using the same configuration across many separate projects,
|
||||
keep in mind that you can also create your own custom presets with
|
||||
whichever plugins and presets you're looking to use.
|
||||
|
||||
module.exports = function() {
|
||||
return {
|
||||
plugins: [
|
||||
require("@babel/plugin-syntax-dynamic-import"),
|
||||
[require("@babel/plugin-proposal-decorators"), { "legacy": true }],
|
||||
[require("@babel/plugin-proposal-class-properties"), { "loose": false }],
|
||||
],
|
||||
presets: [
|
||||
// ...
|
||||
],
|
||||
};
|
||||
};
|
||||
`);
|
||||
}
|
||||
@ -1,3 +0,0 @@
|
||||
src
|
||||
test
|
||||
*.log
|
||||
@ -1,54 +0,0 @@
|
||||
# @babel/preset-stage-2
|
||||
|
||||
As of v7.0.0-beta.55, we've removed Babel's Stage presets. Please consider reading our [blog post](https://babeljs.io/blog/2018/07/27/removing-babels-stage-presets) on this decision for more details. TL;DR is that it's more beneficial in the long run to explicitly add which proposals to use.
|
||||
|
||||
---
|
||||
|
||||
For a more automatic migration, we have updated [babel-upgrade](https://github.com/babel/babel-upgrade) to do this for you (you can run `npx babel-upgrade`).
|
||||
|
||||
If you want the same configuration as before:
|
||||
|
||||
```jsonc
|
||||
{
|
||||
"plugins": [
|
||||
// Stage 2
|
||||
["@babel/plugin-proposal-decorators", { "legacy": true }],
|
||||
"@babel/plugin-proposal-function-sent",
|
||||
"@babel/plugin-proposal-export-namespace-from",
|
||||
"@babel/plugin-proposal-numeric-separator",
|
||||
"@babel/plugin-proposal-throw-expressions",
|
||||
|
||||
// Stage 3
|
||||
"@babel/plugin-syntax-dynamic-import",
|
||||
"@babel/plugin-syntax-import-meta",
|
||||
["@babel/plugin-proposal-class-properties", { "loose": true }],
|
||||
"@babel/plugin-proposal-json-strings"
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
If you're using the same configuration across many separate projects,
|
||||
keep in mind that you can also create your own custom presets with
|
||||
whichever plugins and presets you're looking to use.
|
||||
|
||||
```js
|
||||
module.exports = function() {
|
||||
return {
|
||||
plugins: [
|
||||
require("@babel/plugin-syntax-dynamic-import"),
|
||||
[require("@babel/plugin-proposal-decorators"), { "legacy": true }],
|
||||
[require("@babel/plugin-proposal-class-properties"), { "loose": false }],
|
||||
],
|
||||
presets: [
|
||||
// ...
|
||||
],
|
||||
};
|
||||
};
|
||||
```
|
||||
|
||||
**NOTE: Compatibility between `@babel/plugin-proposal-class-properties` and `@babel/plugin-proposal-decorators`**
|
||||
If you are including your plugins manually and using `@babel/plugin-proposal-class-properties`, make sure that `@babel/plugin-proposal-decorators` comes before `@babel/plugin-proposal-class-properties`.
|
||||
|
||||
When using the `legacy: true` option of `@babel/plugin-proposal-decorators`, `@babel/plugin-proposal-class-properties` must be used in `loose: true` mode.
|
||||
|
||||
If you are not using `@babel/plugin-proposal-decorators`, `loose` mode is not needed.
|
||||
@ -1,13 +0,0 @@
|
||||
{
|
||||
"name": "@babel/preset-stage-2",
|
||||
"version": "7.8.3",
|
||||
"description": "Babel preset for stage 2 plugins",
|
||||
"author": "Sebastian McKenzie <sebmck@gmail.com>",
|
||||
"homepage": "https://babeljs.io/",
|
||||
"license": "MIT",
|
||||
"publishConfig": {
|
||||
"access": "public"
|
||||
},
|
||||
"repository": "https://github.com/babel/babel/tree/master/packages/babel-preset-stage-2",
|
||||
"main": "lib/index.js"
|
||||
}
|
||||
@ -1,49 +0,0 @@
|
||||
export default function() {
|
||||
throw new Error(`
|
||||
As of v7.0.0-beta.55, we've removed Babel's Stage presets.
|
||||
Please consider reading our blog post on this decision at
|
||||
https://babeljs.io/blog/2018/07/27/removing-babels-stage-presets
|
||||
for more details. TL;DR is that it's more beneficial in the
|
||||
long run to explicitly add which proposals to use.
|
||||
|
||||
For a more automatic migration, we have updated babel-upgrade,
|
||||
https://github.com/babel/babel-upgrade to do this for you with
|
||||
"npx babel-upgrade".
|
||||
|
||||
If you want the same configuration as before:
|
||||
|
||||
{
|
||||
"plugins": [
|
||||
// Stage 2
|
||||
["@babel/plugin-proposal-decorators", { "legacy": true }],
|
||||
"@babel/plugin-proposal-function-sent",
|
||||
"@babel/plugin-proposal-export-namespace-from",
|
||||
"@babel/plugin-proposal-numeric-separator",
|
||||
"@babel/plugin-proposal-throw-expressions",
|
||||
|
||||
// Stage 3
|
||||
"@babel/plugin-syntax-dynamic-import",
|
||||
"@babel/plugin-syntax-import-meta",
|
||||
["@babel/plugin-proposal-class-properties", { "loose": false }],
|
||||
"@babel/plugin-proposal-json-strings"
|
||||
]
|
||||
}
|
||||
|
||||
If you're using the same configuration across many separate projects,
|
||||
keep in mind that you can also create your own custom presets with
|
||||
whichever plugins and presets you're looking to use.
|
||||
|
||||
module.exports = function() {
|
||||
return {
|
||||
plugins: [
|
||||
require("@babel/plugin-syntax-dynamic-import"),
|
||||
[require("@babel/plugin-proposal-decorators"), { "legacy": true }],
|
||||
[require("@babel/plugin-proposal-class-properties"), { "loose": false }],
|
||||
],
|
||||
presets: [
|
||||
// ...
|
||||
],
|
||||
};
|
||||
};
|
||||
`);
|
||||
}
|
||||
@ -1,3 +0,0 @@
|
||||
src
|
||||
test
|
||||
*.log
|
||||
@ -1,46 +0,0 @@
|
||||
# @babel/preset-stage-3
|
||||
|
||||
As of v7.0.0-beta.55, we've removed Babel's Stage presets. Please consider reading our [blog post](https://babeljs.io/blog/2018/07/27/removing-babels-stage-presets) on this decision for more details. TL;DR is that it's more beneficial in the long run to explicitly add which proposals to use.
|
||||
|
||||
---
|
||||
|
||||
For a more automatic migration, we have updated [babel-upgrade](https://github.com/babel/babel-upgrade) to do this for you (you can run `npx babel-upgrade`).
|
||||
|
||||
If you want the same configuration as before:
|
||||
|
||||
```json
|
||||
{
|
||||
"plugins": [
|
||||
"@babel/plugin-syntax-dynamic-import",
|
||||
"@babel/plugin-syntax-import-meta",
|
||||
["@babel/plugin-proposal-class-properties", { "loose": false }],
|
||||
"@babel/plugin-proposal-json-strings"
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
If you're using the same configuration across many separate projects,
|
||||
keep in mind that you can also create your own custom presets with
|
||||
whichever plugins and presets you're looking to use.
|
||||
|
||||
```js
|
||||
module.exports = function() {
|
||||
return {
|
||||
plugins: [
|
||||
require("@babel/plugin-syntax-dynamic-import"),
|
||||
[require("@babel/plugin-proposal-decorators"), { "legacy": true }],
|
||||
[require("@babel/plugin-proposal-class-properties"), { "loose": true }],
|
||||
],
|
||||
presets: [
|
||||
// ...
|
||||
],
|
||||
};
|
||||
};
|
||||
```
|
||||
|
||||
**NOTE: Compatibility between `@babel/plugin-proposal-class-properties` and `@babel/plugin-proposal-decorators`**
|
||||
If you are including your plugins manually and using `@babel/plugin-proposal-class-properties`, make sure that `@babel/plugin-proposal-decorators` comes before `@babel/plugin-proposal-class-properties`.
|
||||
|
||||
When using the `legacy: true` option of `@babel/plugin-proposal-decorators`, `@babel/plugin-proposal-class-properties` must be used in `loose: true` mode.
|
||||
|
||||
If you are not using `@babel/plugin-proposal-decorators`, `loose` mode is not needed.
|
||||
@ -1,13 +0,0 @@
|
||||
{
|
||||
"name": "@babel/preset-stage-3",
|
||||
"version": "7.8.3",
|
||||
"description": "Babel preset for stage 3 plugins",
|
||||
"author": "Sebastian McKenzie <sebmck@gmail.com>",
|
||||
"homepage": "https://babeljs.io/",
|
||||
"license": "MIT",
|
||||
"publishConfig": {
|
||||
"access": "public"
|
||||
},
|
||||
"repository": "https://github.com/babel/babel/tree/master/packages/babel-preset-stage-3",
|
||||
"main": "lib/index.js"
|
||||
}
|
||||
@ -1,42 +0,0 @@
|
||||
export default function() {
|
||||
throw new Error(`
|
||||
As of v7.0.0-beta.55, we've removed Babel's Stage presets.
|
||||
Please consider reading our blog post on this decision at
|
||||
https://babeljs.io/blog/2018/07/27/removing-babels-stage-presets
|
||||
for more details. TL;DR is that it's more beneficial in the
|
||||
long run to explicitly add which proposals to use.
|
||||
|
||||
For a more automatic migration, we have updated babel-upgrade,
|
||||
https://github.com/babel/babel-upgrade to do this for you with
|
||||
"npx babel-upgrade".
|
||||
|
||||
If you want the same configuration as before:
|
||||
|
||||
{
|
||||
"plugins": [
|
||||
"@babel/plugin-syntax-dynamic-import",
|
||||
"@babel/plugin-syntax-import-meta",
|
||||
["@babel/plugin-proposal-class-properties", { "loose": false }],
|
||||
"@babel/plugin-proposal-json-strings"
|
||||
]
|
||||
}
|
||||
|
||||
|
||||
If you're using the same configuration across many separate projects,
|
||||
keep in mind that you can also create your own custom presets with
|
||||
whichever plugins and presets you're looking to use.
|
||||
|
||||
module.exports = function() {
|
||||
return {
|
||||
plugins: [
|
||||
require("@babel/plugin-syntax-dynamic-import"),
|
||||
[require("@babel/plugin-proposal-decorators"), { "legacy": true }],
|
||||
[require("@babel/plugin-proposal-class-properties"), { "loose": false }],
|
||||
],
|
||||
presets: [
|
||||
// ...
|
||||
],
|
||||
};
|
||||
};
|
||||
`);
|
||||
}
|
||||
Loading…
x
Reference in New Issue
Block a user