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
43 lines
1.2 KiB
JSON
43 lines
1.2 KiB
JSON
{
|
|
"private": true,
|
|
"scripts": {
|
|
"dev": "next",
|
|
"build": "next build",
|
|
"start": "next start",
|
|
"type-check": "tsc",
|
|
"build:worker": "tsc --build temporal/tsconfig.json",
|
|
"build:worker.watch": "tsc --build --watch temporal/tsconfig.json",
|
|
"start:worker": "cross-env TS_NODE_PROJECT=\"temporal/tsconfig.json\" node --loader ts-node/esm temporal/src/worker.ts",
|
|
"start:worker.watch": "cross-env TS_NODE_PROJECT=\"temporal/tsconfig.json\" nodemon temporal/src/worker.ts"
|
|
},
|
|
"dependencies": {
|
|
"next": "latest",
|
|
"node-fetch": "^3.0.0",
|
|
"react": "^18.2.0",
|
|
"react-dom": "^18.2.0",
|
|
"temporalio": "^0.17.2"
|
|
},
|
|
"devDependencies": {
|
|
"@babel/core": "7.22.5",
|
|
"@tsconfig/node16": "^1.0.0",
|
|
"@types/node": "^12.12.21",
|
|
"@types/node-fetch": "^3.0.3",
|
|
"@types/react": "^17.0.2",
|
|
"@types/react-dom": "^17.0.1",
|
|
"@typescript-eslint/eslint-plugin": "^5.3.0",
|
|
"@typescript-eslint/parser": "^5.3.0",
|
|
"cross-env": "^7.0.3",
|
|
"nodemon": "^2.0.12",
|
|
"ts-node": "^10.2.1",
|
|
"typescript": "^4.4.2"
|
|
},
|
|
"nodemonConfig": {
|
|
"execMap": {
|
|
"ts": "node --loader ts-node/esm"
|
|
},
|
|
"ext": "ts",
|
|
"watch": [
|
|
"temporal/src"
|
|
]
|
|
}
|
|
}
|