rsnext/packages/next/package.json

304 lines
8.7 KiB
JSON
Raw Normal View History

{
"name": "next",
2022-10-18 18:54:31 +02:00
"version": "12.3.2-canary.30",
2019-01-21 13:46:01 +01:00
"description": "The React Framework",
"main": "./dist/server/next.js",
"license": "MIT",
"repository": "vercel/next.js",
"bugs": "https://github.com/vercel/next.js/issues",
2018-10-01 01:34:54 +02:00
"homepage": "https://nextjs.org",
"types": "index.d.ts",
"files": [
"dist",
"app.js",
"app.d.ts",
"babel.js",
"babel.d.ts",
"client.js",
"client.d.ts",
"config.js",
"config.d.ts",
"constants.js",
"constants.d.ts",
"document.js",
"document.d.ts",
"dynamic.js",
"dynamic.d.ts",
"error.js",
"error.d.ts",
"future",
"legacy",
"script.js",
"script.d.ts",
"server.js",
"server.d.ts",
"head.js",
"head.d.ts",
"image.js",
"image.d.ts",
"link.js",
"link.d.ts",
"router.js",
"router.d.ts",
"jest.js",
"jest.d.ts",
"amp.js",
"amp.d.ts",
"index.d.ts",
"types/index.d.ts",
"types/global.d.ts",
"types/compiled.d.ts",
"image-types/global.d.ts",
"font",
"navigation.js",
"navigation.d.ts",
"headers.js",
"headers.d.ts"
],
"bin": {
"next": "./dist/bin/next"
},
"scripts": {
"dev": "taskr",
"release": "taskr release",
"build": "pnpm release && pnpm types",
"prepublishOnly": "cd ../../ && turbo run build",
"types": "tsc --declaration --emitDeclarationOnly --declarationDir dist",
"typescript": "tsec --noEmit",
"ncc-compiled": "ncc cache clean && taskr ncc"
},
"taskr": {
"requires": [
"./taskfile-ncc.js",
"./taskfile-swc.js"
]
},
"dependencies": {
2022-10-18 18:54:31 +02:00
"@next/env": "12.3.2-canary.30",
"@swc/helpers": "0.4.11",
"caniuse-lite": "^1.0.30001406",
"postcss": "8.4.14",
"styled-jsx": "5.0.7",
"use-sync-external-store": "1.2.0"
},
"peerDependencies": {
2021-01-04 16:31:56 +01:00
"fibers": ">= 3.1.0",
"node-sass": "^6.0.0 || ^7.0.0",
"react": "^17.0.2 || ^18.0.0-0",
"react-dom": "^17.0.2 || ^18.0.0-0",
2021-01-04 16:31:56 +01:00
"sass": "^1.3.0"
},
"peerDependenciesMeta": {
"node-sass": {
"optional": true
},
"sass": {
"optional": true
},
"fibers": {
"optional": true
}
},
"devDependencies": {
"@ampproject/toolbox-optimizer": "2.8.3",
"@babel/code-frame": "7.12.11",
"@babel/core": "7.18.0",
"@babel/eslint-parser": "7.18.2",
"@babel/generator": "7.18.0",
"@babel/plugin-proposal-class-properties": "7.14.5",
"@babel/plugin-proposal-export-namespace-from": "7.14.5",
"@babel/plugin-proposal-numeric-separator": "7.14.5",
"@babel/plugin-proposal-object-rest-spread": "7.14.7",
"@babel/plugin-syntax-bigint": "7.8.3",
"@babel/plugin-syntax-dynamic-import": "7.8.3",
"@babel/plugin-syntax-import-assertions": "7.16.7",
"@babel/plugin-syntax-jsx": "7.14.5",
"@babel/plugin-transform-modules-commonjs": "7.18.0",
"@babel/plugin-transform-runtime": "7.18.0",
"@babel/preset-env": "7.18.0",
"@babel/preset-react": "7.14.5",
"@babel/preset-typescript": "7.17.12",
"@babel/runtime": "7.15.4",
"@babel/traverse": "7.18.0",
"@babel/types": "7.18.0",
"@edge-runtime/primitives": "1.1.0-beta.37",
"@hapi/accept": "5.0.2",
"@napi-rs/cli": "2.12.0",
"@napi-rs/triples": "1.1.0",
2022-10-18 18:54:31 +02:00
"@next/polyfill-module": "12.3.2-canary.30",
"@next/polyfill-nomodule": "12.3.2-canary.30",
"@next/react-dev-overlay": "12.3.2-canary.30",
"@next/react-refresh-utils": "12.3.2-canary.30",
"@next/swc": "12.3.2-canary.30",
"@segment/ajv-human-errors": "2.1.2",
"@taskr/clear": "1.1.0",
"@taskr/esnext": "1.1.0",
"@taskr/watch": "1.1.0",
"@types/amphtml-validator": "1.0.0",
"@types/babel__code-frame": "7.0.2",
"@types/babel__core": "7.1.12",
"@types/babel__generator": "7.6.2",
"@types/babel__template": "7.4.0",
"@types/babel__traverse": "7.11.0",
"@types/bytes": "3.1.1",
"@types/ci-info": "2.0.0",
"@types/compression": "0.0.36",
"@types/content-disposition": "0.5.4",
2019-09-05 16:11:08 +02:00
"@types/content-type": "1.1.3",
"@types/cookie": "0.3.3",
2019-07-30 23:35:15 +02:00
"@types/cross-spawn": "6.0.0",
"@types/debug": "4.1.5",
"@types/fresh": "0.5.0",
"@types/glob": "7.1.1",
"@types/jsonwebtoken": "8.3.7",
"@types/lodash": "4.14.149",
"@types/lodash.curry": "4.1.6",
Add experimental SPR support (#8832) * initial commit for SPRv2 * Add initial SPR cache handling * update SPR handling * Implement SPR handling in render * Update tests, handle caching with serverless next start, add TODOs, and update manifest generating * Handle no prerender-manifest from not being used * Fix url.parse error * Apply suggestions from code review Co-Authored-By: Joe Haddad <joe.haddad@zeit.co> * Replace set with constants in next-page-config * simplify sprStatus.used * Add error if getStaticProps is used with getInitialProps * Remove stale TODO * Update revalidate values in SPR cache for non-seeded routes * Apply suggestions from code review * Remove concurrency type * Rename variable for clarity * Add copying prerender files during export * Add comment for clarity * Fix exporting * Update comment * Add additional note * Rename variable * Update to not re-export SPR pages from build * Hard navigate when fetching data fails * Remove default extension * Add brackets * Add checking output files to prerender tests * Adjust export move logic * Clarify behavior of export aggregation * Update variable names for clarity * Update tests * Add comment * s/an oxymoron/contradictory/ * rename * Extract error case * Add tests for exporting SPR pages and update /_next/data endpoint to end with .json * Relocate variable * Adjust route building * Rename to unstable * Rename unstable_getStaticParams * Fix linting * Only add this when a data request * Update prerender data tests * s/isServerless/isLikeServerless/ * Don't rely on query for `next start` in serverless mode * Rename var * Update renderedDuringBuild check * Add test for dynamic param with bracket * Fix serverless next start handling * remove todo * Adjust comment * Update calculateRevalidate * Remove cache logic from render.tsx * Remove extra imports * Move SPR cache logic to next-server * Remove old isDynamic prop * Add calling App getInitialProps for SPR pages * Update revalidate logic * Add isStale to SprCacheValue * Update headers for SPR * add awaiting pendingRevalidation * Dont return null for revalidation render * Adjust logic * Be sure to remove coalesced render * Fix data for serverless * Create a method coalescing utility * Remove TODO * Extract send payload helper * Wrap in-line * Move around some code * Add tests for de-duping and revalidating * Update prerender manifest test
2019-09-24 10:50:04 +02:00
"@types/lru-cache": "5.1.0",
"@types/micromatch": "4.0.2",
"@types/node-fetch": "2.6.1",
2020-03-29 19:17:06 +02:00
"@types/path-to-regexp": "1.7.0",
"@types/platform": "1.3.4",
2020-01-06 17:43:26 +01:00
"@types/react": "16.9.17",
"@types/react-dom": "16.9.4",
2019-09-05 16:11:08 +02:00
"@types/react-is": "16.7.1",
"@types/semver": "7.3.1",
2019-09-05 16:11:08 +02:00
"@types/send": "0.14.4",
"@types/shell-quote": "1.7.1",
"@types/tar": "4.0.3",
"@types/text-table": "0.2.1",
"@types/ua-parser-js": "0.7.36",
"@types/uuid": "8.3.1",
"@types/webpack-sources1": "npm:@types/webpack-sources@0.1.5",
"@types/ws": "8.2.0",
"@vercel/ncc": "0.34.0",
"@vercel/nft": "0.22.1",
"acorn": "8.5.0",
"ajv": "8.11.0",
"amphtml-validator": "1.0.35",
"anser": "1.4.9",
"arg": "4.1.0",
2021-12-20 16:28:17 +01:00
"assert": "2.0.0",
2020-03-29 00:27:09 +01:00
"async-retry": "1.2.3",
"async-sema": "3.0.0",
"babel-plugin-transform-define": "2.0.0",
"babel-plugin-transform-react-remove-prop-types": "0.4.24",
"browserify-zlib": "0.2.0",
"browserslist": "4.20.2",
"buffer": "5.6.0",
2022-02-25 11:15:18 +01:00
"bytes": "3.1.1",
"chalk": "2.4.2",
"ci-info": "watson/ci-info#f43f6a1cefff47fb361c88cf4b943fdbcaafe540",
[ESLint] Introduce a new setup process when `next lint` is run for the first time (#26584) This PR introduces an improved developer experience when `next lint` is run for the first time. ### Current behavior `eslint-config-next` is a required package that must be installed before proceeding with `next lint` or `next build`: ![image](https://user-images.githubusercontent.com/12476932/123468791-43088100-d5c0-11eb-9ad0-5beb80b6c968.png) Although this has helped many developers start using the new ESLint config, this has also resulted in a few issues: - Users are required to install the full config (`eslint-config-next`) even if they do not use it or use the Next.js plugin directly (`eslint-plugin-next`). - #26348 - There's some confusion on why `eslint-config-next` needs to be installed or how it should be used instead of `eslint-plugin-next`. - #26574 - #26475 - #26438 ### New behavior Instead of enforcing `eslint-config-next` as a required package, this PR prompts the user by asking what config they would like to start. This happens when `next lint` is run for the first time **and** if no ESLint configuration is detected in the application. <img src="https://user-images.githubusercontent.com/12476932/124331177-e1668a80-db5c-11eb-8915-38d3dc20f5d4.gif" width="800" /> - The CLI will take care of installing `eslint` or `eslint-config-next` if either is not already installed - Users now have the option to choose between a strict configuration (`next/core-web-vitals`) or just the base configuration (`next`) - For users that decide to create their own ESLint configuration, or already have an existing one, **installing `eslint-config-next` will not be a requirement for `next lint` or `next build` to run**. A warning message will just show if the Next.js ESLint plugin is not detected in an ESLint config. <img width="682" alt="Screen Shot 2021-06-25 at 3 02 12 PM" src="https://user-images.githubusercontent.com/12476932/123473329-6cc4a680-d5c6-11eb-9a57-d5c0b89a2732.png"> --- In addition, this PR also: - Fixes #26348 - Updates documentation to make it more clear what approach to take for new and existing ESLint configurations
2021-08-04 23:53:15 +02:00
"cli-select": "1.1.2",
"comment-json": "3.0.3",
2020-03-29 00:56:38 +01:00
"compression": "1.7.4",
2020-03-29 17:46:33 +02:00
"conf": "5.0.0",
"constants-browserify": "1.0.0",
"content-disposition": "0.5.3",
2020-03-29 00:56:38 +01:00
"content-type": "1.0.4",
2020-05-11 02:48:57 +02:00
"cookie": "0.4.1",
[ESLint] Introduce a new setup process when `next lint` is run for the first time (#26584) This PR introduces an improved developer experience when `next lint` is run for the first time. ### Current behavior `eslint-config-next` is a required package that must be installed before proceeding with `next lint` or `next build`: ![image](https://user-images.githubusercontent.com/12476932/123468791-43088100-d5c0-11eb-9ad0-5beb80b6c968.png) Although this has helped many developers start using the new ESLint config, this has also resulted in a few issues: - Users are required to install the full config (`eslint-config-next`) even if they do not use it or use the Next.js plugin directly (`eslint-plugin-next`). - #26348 - There's some confusion on why `eslint-config-next` needs to be installed or how it should be used instead of `eslint-plugin-next`. - #26574 - #26475 - #26438 ### New behavior Instead of enforcing `eslint-config-next` as a required package, this PR prompts the user by asking what config they would like to start. This happens when `next lint` is run for the first time **and** if no ESLint configuration is detected in the application. <img src="https://user-images.githubusercontent.com/12476932/124331177-e1668a80-db5c-11eb-8915-38d3dc20f5d4.gif" width="800" /> - The CLI will take care of installing `eslint` or `eslint-config-next` if either is not already installed - Users now have the option to choose between a strict configuration (`next/core-web-vitals`) or just the base configuration (`next`) - For users that decide to create their own ESLint configuration, or already have an existing one, **installing `eslint-config-next` will not be a requirement for `next lint` or `next build` to run**. A warning message will just show if the Next.js ESLint plugin is not detected in an ESLint config. <img width="682" alt="Screen Shot 2021-06-25 at 3 02 12 PM" src="https://user-images.githubusercontent.com/12476932/123473329-6cc4a680-d5c6-11eb-9a57-d5c0b89a2732.png"> --- In addition, this PR also: - Fixes #26348 - Updates documentation to make it more clear what approach to take for new and existing ESLint configurations
2021-08-04 23:53:15 +02:00
"cross-spawn": "6.0.5",
"crypto-browserify": "3.12.0",
"css.escape": "1.5.1",
"cssnano-simple": "3.0.1",
"data-uri-to-buffer": "3.0.1",
"debug": "4.1.1",
2020-03-29 01:18:22 +01:00
"devalue": "2.0.1",
"domain-browser": "4.19.0",
"edge-runtime": "1.1.0-beta.40",
"events": "3.3.0",
"find-cache-dir": "3.3.1",
2020-05-11 02:48:57 +02:00
"find-up": "4.1.0",
2020-03-29 01:27:13 +01:00
"fresh": "0.5.2",
"get-orientation": "1.1.2",
"glob": "7.1.7",
2020-03-29 01:29:14 +01:00
"gzip-size": "5.1.1",
"http-proxy": "1.18.1",
2021-12-20 16:28:17 +01:00
"https-browserify": "1.0.0",
"icss-utils": "5.1.0",
2020-03-30 03:37:41 +02:00
"ignore-loader": "0.1.2",
"image-size": "1.0.0",
2020-03-29 01:33:35 +01:00
"is-docker": "2.0.0",
2020-05-11 02:48:57 +02:00
"is-wsl": "2.2.0",
"jest-worker": "27.0.0-next.5",
"json5": "2.2.1",
2020-03-29 01:37:45 +01:00
"jsonwebtoken": "8.5.1",
"loader-utils2": "npm:loader-utils@2.0.0",
"loader-utils3": "npm:loader-utils@3.1.3",
2020-03-29 01:43:59 +01:00
"lodash.curry": "4.1.1",
2020-03-29 01:46:22 +01:00
"lru-cache": "5.1.1",
"micromatch": "4.0.4",
"mini-css-extract-plugin": "2.4.3",
"nanoid": "3.1.32",
"native-url": "0.3.4",
"neo-async": "2.6.1",
"node-fetch": "2.6.7",
"node-html-parser": "5.3.3",
"ora": "4.0.4",
"os-browserify": "0.3.0",
"p-limit": "3.1.0",
"path-browserify": "1.0.1",
2020-03-29 19:17:06 +02:00
"path-to-regexp": "6.1.0",
"platform": "1.3.6",
"postcss-flexbugs-fixes": "5.0.2",
"postcss-modules-extract-imports": "3.0.0",
"postcss-modules-local-by-default": "4.0.0",
"postcss-modules-scope": "3.0.0",
"postcss-modules-values": "4.0.0",
"postcss-preset-env": "7.4.3",
"postcss-safe-parser": "6.0.0",
"postcss-scss": "4.0.3",
"postcss-value-parser": "4.2.0",
"process": "0.11.10",
2022-01-03 22:46:09 +01:00
"punycode": "2.1.1",
"querystring-es3": "0.2.1",
"raw-body": "2.4.1",
"react": "18.2.0",
"react-dom": "18.2.0",
"react-is": "17.0.2",
"react-builtin": "npm:react@0.0.0-experimental-a8c16a004-20221012",
"react-dom-builtin": "npm:react-dom@0.0.0-experimental-a8c16a004-20221012",
"react-refresh": "0.12.0",
"react-server-dom-webpack": "0.0.0-experimental-a8c16a004-20221012",
"regenerator-runtime": "0.13.4",
"sass-loader": "12.4.0",
"schema-utils2": "npm:schema-utils@2.7.1",
"schema-utils3": "npm:schema-utils@3.0.0",
"semver": "7.3.2",
2020-03-29 03:40:29 +02:00
"send": "0.17.1",
2022-01-03 22:46:09 +01:00
"setimmediate": "1.0.5",
"shell-quote": "1.7.3",
2020-03-29 05:41:35 +02:00
"source-map": "0.6.1",
"stacktrace-parser": "0.1.10",
"stream-browserify": "3.0.0",
"stream-http": "3.1.1",
2020-03-29 05:05:26 +02:00
"string-hash": "1.1.3",
2021-12-20 16:28:17 +01:00
"string_decoder": "1.3.0",
"strip-ansi": "6.0.0",
"tar": "6.1.11",
2019-03-24 14:34:44 +01:00
"taskr": "1.1.0",
"terser": "5.14.1",
"text-table": "0.2.0",
"timers-browserify": "2.0.12",
"tty-browserify": "0.0.1",
"ua-parser-js": "0.7.28",
feat(experimental): option to polyfill `fetch` using `undici` in Node.js <18 (#40318) This PR adds a new `experimental.enableUndici` option to let the developer switch from `next-fetch` to `undici` as the underlying polyfill for `fetch` in Node.js. In the current implementation, Next.js makes sure that `fetch` is always available by using `node-fetch`. However, we do not polyfill in Node.js 18+, since those versions come with their own `fetch` implementation already, built-in. Node.js 18+ uses `undici` under the hood, so letting the developer use `undici` earlier could make the migration easier later on. Eventually, we hope to be able to stop polyfilling `fetch` in an upcoming major version of Next.js, shipping less code. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples) Co-authored-by: Balázs Orbán <info@balazsorban.com> Co-authored-by: Sukka <isukkaw@gmail.com> Co-authored-by: JJ Kasper <jj@jjsweb.site> Co-authored-by: Steven <steven@ceriously.com>
2022-09-27 22:37:28 +02:00
"undici": "5.10.0",
"unistore": "3.4.1",
"util": "0.12.4",
2021-12-20 16:28:17 +01:00
"uuid": "8.3.2",
"vm-browserify": "1.1.2",
"watchpack": "2.4.0",
"web-vitals": "3.0.0",
2022-08-17 15:12:52 +02:00
"webpack": "5.74.0",
"webpack-sources1": "npm:webpack-sources@1.4.3",
"webpack-sources3": "npm:webpack-sources@3.2.3",
"ws": "8.2.3"
},
"resolutions": {
"browserslist": "4.20.2",
"caniuse-lite": "1.0.30001406"
},
"engines": {
"node": ">=14.0.0"
}
}