db214214d6
### What? Update Babel packages across the board ### Why? Since you ship vendored presets and plugins it's impossible for people to update this stuff at their own pace - independently from Next. So users of `next/babel` are currently stuck with old versions and, for example, they might not be able to use the TS `satisfies` operator. ### How? I just updated ranges (to pinned ones) where I could find them, run `corepack pnpm i` and re-run build scripts in the `packages/next`. Fixes #43799
36 lines
674 B
JSON
36 lines
674 B
JSON
{
|
|
"private": true,
|
|
"scripts": {
|
|
"dev": "next",
|
|
"build": "next build",
|
|
"start": "next start"
|
|
},
|
|
"dependencies": {
|
|
"kea": "^0.28.4",
|
|
"next": "latest",
|
|
"next-redux-wrapper": "^2.0.0",
|
|
"prop-types": "^15.6.0",
|
|
"react": "^18.2.0",
|
|
"react-dom": "^18.2.0",
|
|
"react-redux": "^5.0.6",
|
|
"redux": "^4.0.0",
|
|
"reselect": "^3.0.1"
|
|
},
|
|
"devDependencies": {
|
|
"@babel/core": "7.22.5",
|
|
"@babel/plugin-proposal-decorators": "7.22.5"
|
|
},
|
|
"babel": {
|
|
"presets": [
|
|
"next/babel"
|
|
],
|
|
"plugins": [
|
|
[
|
|
"@babel/plugin-proposal-decorators",
|
|
{
|
|
"legacy": true
|
|
}
|
|
]
|
|
]
|
|
}
|
|
}
|