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
24 lines
552 B
JSON
24 lines
552 B
JSON
{
|
|
"private": true,
|
|
"scripts": {
|
|
"dev": "next dev",
|
|
"build": "next build",
|
|
"start": "next start",
|
|
"extract": "NODE_ENV=development lingui extract",
|
|
"compile": "lingui compile"
|
|
},
|
|
"dependencies": {
|
|
"@lingui/react": "^3.17.1",
|
|
"next": "latest",
|
|
"react": "^18.2.0",
|
|
"react-dom": "^18.2.0"
|
|
},
|
|
"devDependencies": {
|
|
"@babel/core": "7.22.5",
|
|
"@lingui/cli": "^3.17.1",
|
|
"@lingui/core": "3.17.1",
|
|
"@lingui/loader": "3.17.1",
|
|
"@lingui/macro": "^3.17.1",
|
|
"babel-plugin-macros": "^3.1.0"
|
|
}
|
|
}
|