archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rsnext/package.json

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

275 lines
11 KiB
JSON
Raw Permalink Normal View History

initial source
2016-10-06 01:52:50 +02:00
{
Monorepo (#5341) - Implements Lerna - Moves all source code into `packages/next` - Keeps integration tests in the root directory
2018-10-01 01:02:10 +02:00
"name": "nextjs-project",
the way towards webpack 5 typings (#29105) Co-authored-by: sokra <sokra@users.noreply.github.com>
2021-09-21 19:17:16 +02:00
"version": "0.0.0",
Monorepo (#5341) - Implements Lerna - Moves all source code into `packages/next` - Keeps integration tests in the root directory
2018-10-01 01:02:10 +02:00
"private": true,
Revert "chore: remove workspace from `package.json` since we have `pnpm-works…" (#38376) Revert "chore: remove workspace from `package.json` since we have `pnpm-works… (#38166)" This reverts commit a37abc62ee7b0f176290b6de8ee6a2a4d4419dbc.
2022-07-06 17:08:00 +02:00
"workspaces": [
"packages/*"
],
initial source
2016-10-06 01:52:50 +02:00
"scripts": {
feat(turbo): use turbo gen instead of plop (#53684) ### What? Use [Turborepo generators](https://turbo.build/repo/docs/core-concepts/monorepos/code-generation#custom-generators) instead of plop. Turborepo generators are built on top of plop, but include some additional tooling to make working in monorepos easier. It also supports zero config typescript for configs. ### Why? Same Team! ### How? Ported the existing plopfile to a turbo generator config Co-authored-by: Jiachi Liu <4800338+huozhi@users.noreply.github.com>
2023-11-03 02:25:18 +01:00
"new-error": "turbo gen error",
"new-test": "turbo gen test",
chore: cross-platform `rm -rf` script (#49529) - Closes https://github.com/vercel/next.js/issues/42433 - Closes https://github.com/vercel/next.js/pull/43105 - Closes https://github.com/vercel/next.js/pull/49522
2023-05-10 03:14:37 +02:00
"clean": "lerna clean -y && lerna bootstrap && lerna run clean && lerna exec 'node ../../scripts/rm.mjs dist'",
Increase remote cache timeout for swc builds (#51270) These occasionally timeout and start building even when they don't need to so this increases them a bit from the default.
2023-06-14 06:31:40 +02:00
"build": "turbo run build --remote-cache-timeout 60 --summarize true",
Monorepo (#5341) - Implements Lerna - Moves all source code into `packages/next` - Keeps integration tests in the root directory
2018-10-01 01:02:10 +02:00
"lerna": "lerna",
chore: make sure polyfills are built for `pnpm dev` (#41062) Re-lands #40335 but without modifying the lock file. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a 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 a 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/examples/adding-examples.md)
2022-09-30 16:54:38 +02:00
"dev": "turbo run dev --parallel",
chore: simplify package scripts (#45226) <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change that you're making: --> ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/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` - [ ] [e2e](https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm build && pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-02-08 00:30:02 +01:00
"test-types": "tsc",
Ensure test-unit includes package unit tests (#46707) Seems the unit tests from our packages haven't been running as a few haven't been updated and had failing assertions.
2023-03-03 00:09:48 +01:00
"test-unit": "jest test/unit/ packages/next/ packages/font",
Update to leverage pnpm for monorepo (#37259) * Update to leverage pnpm for monorepo * update compiled * update stats action * update ci install step * update ci * add test dep * update invoking scripts * update caching * skip cache for now * update dep * update packages and fix babel * update compiled * update lint * update test * update ci * update pnpm store caching * update path for windows * update restore-key config * update caching * remove extra build azure stage * re-add checkout * update setting pnpm store * bump * remove azure caching as pnpm is faster to download * update contributing * apply suggestions * remove install-peers * prepublish -> prepublishOnly * prepublish -> prepublishOnly more * more yarn -> pnpm references * more yarn -> pnpm references take 2 * use workspace protocol for root package.json Co-authored-by: Steven <steven@ceriously.com>
2022-05-29 06:35:16 +02:00
"test-dev": "cross-env NEXT_TEST_MODE=dev pnpm testheadless",
Skip test/integration development tests during Turbopack build test run (#63671) ## What? Follow-up to #63665. Ensures development tests are skipped during the production build run for Turbopack (i.e. used to create the turbopack-build-tests-manifest). Adds `pnpm test-dev-turbo` and `pnpm test-start-turbo` (and their `testonly` equivalent) for running tests. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> Closes NEXT-2915
2024-03-25 18:37:34 +01:00
"test-dev-turbo": "cross-env NEXT_TEST_MODE=dev TURBOPACK=1 TURBOPACK_DEV=1 pnpm testheadless",
Update to leverage pnpm for monorepo (#37259) * Update to leverage pnpm for monorepo * update compiled * update stats action * update ci install step * update ci * add test dep * update invoking scripts * update caching * skip cache for now * update dep * update packages and fix babel * update compiled * update lint * update test * update ci * update pnpm store caching * update path for windows * update restore-key config * update caching * remove extra build azure stage * re-add checkout * update setting pnpm store * bump * remove azure caching as pnpm is faster to download * update contributing * apply suggestions * remove install-peers * prepublish -> prepublishOnly * prepublish -> prepublishOnly more * more yarn -> pnpm references * more yarn -> pnpm references take 2 * use workspace protocol for root package.json Co-authored-by: Steven <steven@ceriously.com>
2022-05-29 06:35:16 +02:00
"test-start": "cross-env NEXT_TEST_MODE=start pnpm testheadless",
Skip test/integration development tests during Turbopack build test run (#63671) ## What? Follow-up to #63665. Ensures development tests are skipped during the production build run for Turbopack (i.e. used to create the turbopack-build-tests-manifest). Adds `pnpm test-dev-turbo` and `pnpm test-start-turbo` (and their `testonly` equivalent) for running tests. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> Closes NEXT-2915
2024-03-25 18:37:34 +01:00
"test-start-turbo": "cross-env NEXT_TEST_MODE=start TURBOPACK=1 TURBOPACK_BUILD=1 pnpm testheadless",
Update to leverage pnpm for monorepo (#37259) * Update to leverage pnpm for monorepo * update compiled * update stats action * update ci install step * update ci * add test dep * update invoking scripts * update caching * skip cache for now * update dep * update packages and fix babel * update compiled * update lint * update test * update ci * update pnpm store caching * update path for windows * update restore-key config * update caching * remove extra build azure stage * re-add checkout * update setting pnpm store * bump * remove azure caching as pnpm is faster to download * update contributing * apply suggestions * remove install-peers * prepublish -> prepublishOnly * prepublish -> prepublishOnly more * more yarn -> pnpm references * more yarn -> pnpm references take 2 * use workspace protocol for root package.json Co-authored-by: Steven <steven@ceriously.com>
2022-05-29 06:35:16 +02:00
"test-deploy": "cross-env NEXT_TEST_MODE=deploy pnpm testheadless",
add `testonly` variants for all test modes and refactored `test` as alias of `testheadless` (#44528) So that we don't need to use `NEXT_TEST_MODE=...` ever again manually.
2023-01-03 23:43:55 +01:00
"testonly-dev": "cross-env NEXT_TEST_MODE=dev pnpm testonly",
Skip test/integration development tests during Turbopack build test run (#63671) ## What? Follow-up to #63665. Ensures development tests are skipped during the production build run for Turbopack (i.e. used to create the turbopack-build-tests-manifest). Adds `pnpm test-dev-turbo` and `pnpm test-start-turbo` (and their `testonly` equivalent) for running tests. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> Closes NEXT-2915
2024-03-25 18:37:34 +01:00
"testonly-dev-turbo": "cross-env NEXT_TEST_MODE=dev TURBOPACK=1 TURBOPACK_DEV=1 pnpm testonly",
add `testonly` variants for all test modes and refactored `test` as alias of `testheadless` (#44528) So that we don't need to use `NEXT_TEST_MODE=...` ever again manually.
2023-01-03 23:43:55 +01:00
"testonly-start": "cross-env NEXT_TEST_MODE=start pnpm testonly",
Skip test/integration development tests during Turbopack build test run (#63671) ## What? Follow-up to #63665. Ensures development tests are skipped during the production build run for Turbopack (i.e. used to create the turbopack-build-tests-manifest). Adds `pnpm test-dev-turbo` and `pnpm test-start-turbo` (and their `testonly` equivalent) for running tests. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> Closes NEXT-2915
2024-03-25 18:37:34 +01:00
"testonly-start-turbo": "cross-env NEXT_TEST_MODE=start TURBOPACK=1 TURBOPACK_BUILD=1 pnpm testonly",
add `testonly` variants for all test modes and refactored `test` as alias of `testheadless` (#44528) So that we don't need to use `NEXT_TEST_MODE=...` ever again manually.
2023-01-03 23:43:55 +01:00
"testonly-deploy": "cross-env NEXT_TEST_MODE=deploy pnpm testonly",
"test": "pnpm testheadless",
add test-turbo command (#64284) ### What? align integration tests with e2e test command-wise ### Why? ### How? Closes PACK-2929 --------- Co-authored-by: Balázs Orbán <info@balazsorban.com>
2024-04-10 18:53:52 +02:00
"test-turbo": "cross-env TURBOPACK=1 TURBOPACK_DEV=1 TURBOPACK_BUILD=1 pnpm testheadless",
chore: simplify package scripts (#45226) <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change that you're making: --> ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/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` - [ ] [e2e](https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm build && pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-02-08 00:30:02 +01:00
"testonly": "jest --runInBand",
Update to leverage pnpm for monorepo (#37259) * Update to leverage pnpm for monorepo * update compiled * update stats action * update ci install step * update ci * add test dep * update invoking scripts * update caching * skip cache for now * update dep * update packages and fix babel * update compiled * update lint * update test * update ci * update pnpm store caching * update path for windows * update restore-key config * update caching * remove extra build azure stage * re-add checkout * update setting pnpm store * bump * remove azure caching as pnpm is faster to download * update contributing * apply suggestions * remove install-peers * prepublish -> prepublishOnly * prepublish -> prepublishOnly more * more yarn -> pnpm references * more yarn -> pnpm references take 2 * use workspace protocol for root package.json Co-authored-by: Steven <steven@ceriously.com>
2022-05-29 06:35:16 +02:00
"testheadless": "cross-env HEADLESS=true pnpm testonly",
Migrate PR stats action into Next.js repo (#13177) * Migrate PR stats into Next.js repo * Update running prettier in local mode
2020-05-21 14:07:27 +02:00
"genstats": "cross-env LOCAL_STATS=true node .github/actions/next-stats-action/src/index.js",
Add error handling for error being thrown in _app getinitialProps (#6680) * Fix handling of undefined being thrown in getInitialProps and update integration test * Update test * Move test to app-document
2019-03-17 17:43:03 +01:00
"git-reset": "git reset --hard HEAD",
"git-clean": "git clean -d -x -e node_modules -e packages -f",
type check tests (and convert next-test-utils.js to ts) (#51071) Enables type checking for tests in CI and fixes a bunch of things related to that
2023-06-23 19:42:50 +02:00
"typescript": "tsc --noEmit",
chore: make sure polyfills are built for `pnpm dev` (#41062) Re-lands #40335 but without modifying the lock file. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a 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 a 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/examples/adding-examples.md)
2022-09-30 16:54:38 +02:00
"lint-typescript": "turbo run typescript",
[lint] Allow lint warnings to pass in CI (#66140) To allow us to incrementally adopt more comprehensive linting rules, this pull request disables the previous behaviour of failing CI when any warnings were discovered. Instead, this modifies the previous warnings to be errors which will preserve the previous linting behaviour. As we enable new lint rules, they can be added as warnings which will gently nudge us towards fixing in related pull requests.
2024-06-10 21:57:46 +02:00
"lint-eslint": "eslint . --ext js,jsx,ts,tsx --config .eslintrc.json --no-eslintrc",
Revert "chore: drop `npm-run-all`" (#62700) Reverts vercel/next.js#62642 Closes NEXT-2650
2024-02-29 22:59:24 +01:00
"lint-no-typescript": "run-p prettier-check lint-eslint lint-language",
Add CI check to validate externals doc (#62968) This avoids the need to manually check when these get out of sync by having an automated check to keep them in sync when one or the other is updated. x-ref: https://github.com/vercel/next.js/pull/62966 Closes NEXT-2734
2024-03-07 02:00:25 +01:00
"types-and-precompiled": "run-p lint-typescript check-precompiled validate-externals-doc",
"validate-externals-doc": "node ./scripts/validate-externals-doc.js",
Revert "chore: drop `npm-run-all`" (#62700) Reverts vercel/next.js#62642 Closes NEXT-2650
2024-02-29 22:59:24 +01:00
"lint": "run-p test-types lint-typescript prettier-check lint-eslint lint-language",
[lint] Allow lint warnings to pass in CI (#66140) To allow us to incrementally adopt more comprehensive linting rules, this pull request disables the previous behaviour of failing CI when any warnings were discovered. Instead, this modifies the previous warnings to be errors which will preserve the previous linting behaviour. As we enable new lint rules, they can be added as warnings which will gently nudge us towards fixing in related pull requests.
2024-06-10 21:57:46 +02:00
"lint-fix": "pnpm prettier-fix && eslint . --ext js,jsx,ts,tsx --fix --config .eslintrc.json --no-eslintrc",
chore: Add Alex to lint documentation (#26354) This Pull Request adds [Alex](https://alexjs.com/) to our documentation. It catches insensitive, inconsiderate writing. The original PR (https://github.com/vercel/next.js/pull/25821) is too large so I have decided to break it down into smaller PRs. This PR is the first part. Then I will continue to add the rest of the documentation in smaller PRs. ## More Information on Alex: https://alexjs.com/ https://github.com/get-alex/alex ## Documentation / Examples - [x] Make sure the linting passes
2021-06-22 18:03:12 +02:00
"lint-language": "alex .",
Include all files in Prettier (#17050) This uses the "Expand directories" feature introduces in Prettier 2.0 to automatically format all supported file types. Also, I fixed some badly formatted files.
2020-09-14 04:53:19 +02:00
"prettier-check": "prettier --check .",
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
"check-examples": "./scripts/check-examples.sh",
"get-test-timings": "node run-tests.js --timings --write-timings -g 1/1",
Include all files in Prettier (#17050) This uses the "Expand directories" feature introduces in Prettier 2.0 to automatically format all supported file types. Also, I fixed some badly formatted files.
2020-09-14 04:53:19 +02:00
"prettier-fix": "prettier --write .",
Add declaration files to the contributing guide (#7885)
2019-07-11 02:59:53 +02:00
"types": "lerna run types --stream",
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
"check-precompiled": "./scripts/check-pre-compiled.sh",
Update to leverage turbo for build/prepublish (#37280) * Update to leverage turbo for build/prepublish * update path * remove extra turbo config
2022-05-31 02:05:27 +02:00
"prepublishOnly": "turbo run build",
Do not clear the console (#6758) * Do not clear the console Its rude to clear the console, you may be sharing output with other processes even in tty mode. * Remove unused dependency * Dedupe and cleanup dev output without clearing * use logError * Remove exit handler * Add next helper * Add log helpers * Switch store to log helpers and a shallow object compare * Update other files to use new logging utility * request => build * Update ready on messages * Use case insensitive matching
2019-04-09 17:52:03 +02:00
"lint-staged": "lint-staged",
Update repo scripts to separate folder (#26787)
2021-07-01 13:41:27 +02:00
"next-with-deps": "./scripts/next-with-deps.sh",
Disable telemetry for `pnpm next` when contributing locally (#44610) This PR fixes telemetry so it no longer reports `pnpm next` when contributing to Next.js
2023-01-05 22:27:05 +01:00
"next": "cross-env NEXT_TELEMETRY_DISABLED=1 node --trace-deprecation --enable-source-maps packages/next/dist/bin/next",
"next-no-sourcemaps": "cross-env NEXT_TELEMETRY_DISABLED=1 node --trace-deprecation packages/next/dist/bin/next",
chore: cross-platform `rm -rf` script (#49529) - Closes https://github.com/vercel/next.js/issues/42433 - Closes https://github.com/vercel/next.js/pull/43105 - Closes https://github.com/vercel/next.js/pull/49522
2023-05-10 03:14:37 +02:00
"clean-trace-jaeger": "node scripts/rm.mjs test/integration/basic/.next && TRACE_TARGET=JAEGER pnpm next build test/integration/basic",
Disable telemetry for `pnpm next` when contributing locally (#44610) This PR fixes telemetry so it no longer reports `pnpm next` when contributing to Next.js
2023-01-05 22:27:05 +01:00
"debug": "cross-env NEXT_TELEMETRY_DISABLED=1 node --inspect packages/next/dist/bin/next",
chore: fix postinstall when using tarball (#60443) The postinstall script was failing In the case when you download [a zip](https://codeload.github.com/vercel/next.js/zip/refs/heads/canary) of the repo. This PR fixes it so that `git config` can fail silently in that case when the repo is not using git. - Related to https://github.com/nodejs/citgm/pull/1044 Closes NEXT-2036
2024-01-09 23:37:49 +01:00
"postinstall": "node scripts/git-configure.mjs && node scripts/install-native.mjs",
chore: update to `pnpm@8.6.11` (#50923) https://github.com/pnpm/pnpm/releases/tag/v8.0.0
2023-08-04 21:40:20 +02:00
"version": "pnpm install --no-frozen-lockfile && IS_PUBLISH=yes ./scripts/check-pre-compiled.sh && git add .",
refactor: remove unnecessary `lint-staged` operations (#65861) ### Why? The current `lint-staged` hook uses [function signature](https://github.com/lint-staged/lint-staged?tab=readme-ov-file#function-signature) to target the **staged files** and has extra steps for handling those files that seem to have been passed on from a [5-year-old legacy code](https://github.com/vercel/next.js/pull/9245). The entire process is unnecessary today since `lint-staged` only runs on the staged files. ### How? This PR removed unnecessary logic, removed some no-effect flags, and [removed `git add`](https://github.com/lint-staged/lint-staged?tab=readme-ov-file#v10). > If your task previously contained a git add step, please remove this. --------- Co-authored-by: Sam Ko <sam@vercel.com>
2024-05-30 02:56:30 +02:00
"prepare": "husky",
Update google fonts (#48984) ### What? * Update google fonts for `next/font` with `scripts/update-google-fonts.js.` * Add npm script `pnpm update-google-fonts` ### How? Run `pnpm update-google-fonts`
2023-04-29 17:03:22 +02:00
"sync-react": "node ./scripts/sync-react.js",
chore: add `swc-build-native` script at root package.json (#67345) When developing in Next.js repo, the maintainers / contributors sometimes need to build swc native files. Added a script `swc-build-native` to run the command `pnpm --filter=@next/swc build-native` which was verbose to run.
2024-07-01 16:10:07 +02:00
"update-google-fonts": "node ./scripts/update-google-fonts.js",
"swc-build-native": "pnpm --filter=@next/swc build-native"
initial source
2016-10-06 01:52:50 +02:00
},
Monorepo (#5341) - Implements Lerna - Moves all source code into `packages/next` - Keeps integration tests in the root directory
2018-10-01 01:02:10 +02:00
"devDependencies": {
ci: add job summary to the test suite runs (#56742) This PR adds Github Actions summaries to the test suite that runs in the CI so that you can easily visualise which tests failed + what the relevant log was instead of parsing the logs yourself. Example here https://github.com/vercel/next.js/actions/runs/6495658699 ![CleanShot 2023-10-12 at 14 57 32@2x](https://github.com/vercel/next.js/assets/11064311/7d65496b-6e28-460a-8bef-3f2e91266d00)
2023-10-12 15:57:09 +02:00
"@actions/core": "1.10.1",
Update Babel dependencies (#51962) ### 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
2023-10-17 04:25:57 +02:00
"@babel/core": "7.22.5",
"@babel/eslint-parser": "7.22.5",
"@babel/generator": "7.22.5",
"@babel/parser": "7.22.5",
"@babel/plugin-proposal-object-rest-spread": "7.20.7",
"@babel/preset-flow": "7.22.5",
"@babel/preset-react": "7.22.5",
Upgrade to latest @edge-runtime packages (#62955) This upgrades to the latest edge-runtime packages as it includes exposing `performance`. This was reverted previously as our publishes were failing with a specific change that has since been removed upstream. Closes NEXT-2730
2024-03-06 20:43:48 +01:00
"@edge-runtime/jest-environment": "2.3.10",
Fix emotion-js transform for server components (#54284) ### What & Why emotion-js has its own [jsx transform](https://emotion.sh/docs/typescript#emotionreact) which is being applied when `compiler.emotion` is enabled in `next.config.js`. Thanks to emotion-js team that provided an emotion-js example setup with app router [here](https://github.com/emotion-js/emotion/issues/2928#issuecomment-1319792703), so that we can use it as test example with app router. Based on the setup, we create a test case working with emotion js but failed with error mentioned in #41994 that some client hooks appearing in server components. That is because the emotion-js jsx factory includes some client hooks. ### How For server components, css-in-js is not recommended to apply so we disabled the transform before, the emotion jsx factory is a separate config that should also not be applied in server components. So in this case we still use react jsx factory instead of the emotion-js one for server components then it won't error. The test case can also be used as an example for basic emotion-js use case with app router. Fixes #41994 Closes NEXT-1368
2023-08-20 05:14:16 +02:00
"@emotion/cache": "11.11.0",
"@emotion/react": "11.11.1",
Add Tailwind and PurgeCSS Test (#9714)
2019-12-12 00:54:40 +01:00
"@fullhuman/postcss-purgecss": "1.3.0",
Add additional tests for @next/mdx (#45585)Co-authored-by: Shu Ding <g@shud.in> Adds additional integration tests for `@next/mdx`. - Test mdx-rs - Test `mdx-components.tsx` - Tests development and production. Previously it only checked development. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: --> ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/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` - [ ] [e2e](https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm build && pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) --------- Co-authored-by: Shu Ding <g@shud.in>
2023-02-11 13:37:00 +01:00
"@mdx-js/loader": "2.2.1",
"@mdx-js/react": "2.2.1",
Update to leverage pnpm for monorepo (#37259) * Update to leverage pnpm for monorepo * update compiled * update stats action * update ci install step * update ci * add test dep * update invoking scripts * update caching * skip cache for now * update dep * update packages and fix babel * update compiled * update lint * update test * update ci * update pnpm store caching * update path for windows * update restore-key config * update caching * remove extra build azure stage * re-add checkout * update setting pnpm store * bump * remove azure caching as pnpm is faster to download * update contributing * apply suggestions * remove install-peers * prepublish -> prepublishOnly * prepublish -> prepublishOnly more * more yarn -> pnpm references * more yarn -> pnpm references take 2 * use workspace protocol for root package.json Co-authored-by: Steven <steven@ceriously.com>
2022-05-29 06:35:16 +02:00
"@next/bundle-analyzer": "workspace:*",
"@next/env": "workspace:*",
"@next/eslint-plugin-next": "workspace:*",
Add next font package (#40227) For some context: https://vercel.slack.com/archives/CGU8HUTUH/p1662124179102509 Adds `@next/font` package. `scripts/update-google-fonts.js` generates functions and metadata for all available google fonts. The metadata is used in `loader.ts` to validate font options (from #40221). It then fetches the CSS from google fonts, downloads the font files and emits them as static assets. The actual integration with `packages/next` and integration tests depends on #40221, will follow up with new PR. Co-authored-by: JJ Kasper <jj@jjsweb.site>
2022-09-22 00:10:24 +02:00
"@next/font": "workspace:*",
Update to leverage pnpm for monorepo (#37259) * Update to leverage pnpm for monorepo * update compiled * update stats action * update ci install step * update ci * add test dep * update invoking scripts * update caching * skip cache for now * update dep * update packages and fix babel * update compiled * update lint * update test * update ci * update pnpm store caching * update path for windows * update restore-key config * update caching * remove extra build azure stage * re-add checkout * update setting pnpm store * bump * remove azure caching as pnpm is faster to download * update contributing * apply suggestions * remove install-peers * prepublish -> prepublishOnly * prepublish -> prepublishOnly more * more yarn -> pnpm references * more yarn -> pnpm references take 2 * use workspace protocol for root package.json Co-authored-by: Steven <steven@ceriously.com>
2022-05-29 06:35:16 +02:00
"@next/mdx": "workspace:*",
"@next/plugin-storybook": "workspace:*",
"@next/polyfill-module": "workspace:*",
"@next/polyfill-nomodule": "workspace:*",
"@next/swc": "workspace:*",
refactor smooth scroll bailout logic in app navigations (#53186) This refactors the changes from my previous PR to allow smooth scrolling for the appDir case -- `componentDidUpdate` isn't a reliable way to check if only the hash has changed. This adds a property to `focusAndScrollRef` and compares canonicalUrls (sans hash fragment) - Original https://github.com/vercel/next.js/pull/52915 Co-authored-by: Tim Neutkens <6324199+timneutkens@users.noreply.github.com>
2023-07-27 16:39:51 +02:00
"@next/third-parties": "workspace:*",
Add OTEL tests (#47149)
2023-03-16 17:35:07 +01:00
"@opentelemetry/api": "1.4.1",
Fix not found css not being preloaded while navigation (#53906) ### Problem One style of `not-found` has `precendence` property with "undefined" value, which can't be handled by React Float, then during navigation the style could not load properly, lead to the style missing in issue #53210. ### Solution Always enable `precendence` for all links, so all the css styles of page and convention components can be hoist by react properly. Float will decide which one should be handled. Previously this change only applies to template, actually we can apply it to all components so that they can all be handled properly especially during client navigation. Related react change: https://github.com/facebook/react/pull/27265 Fixes #53210
2023-08-23 15:07:30 +02:00
"@picocss/pico": "1.5.10",
Add replay.io test suite dependencies (#60381) ## What? Adds the missing dependencies for recording the Next.js test suite in Replay that @jaril added. ### Steps to use it 1. Clear all local replays using `pnpm replay rm-all` 1. Run the test locally using the `RECORD_REPLAY=1` environment variables. I.e. `RECORD_REPLAY=1 pnpm test-dev test/e2e/app-dir/app/index.test.ts` 1. Upload all the replays to your workspace using your the API key: `RECORD_REPLAY_API_KEY=keyhere pnpm replay upload-all` 1. Check the uploaded replays in your workspace, while uploading it provides the URLs. You can check if the replay was recorded correctly using `pnpm replay ls` <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> Closes NEXT-2014
2024-01-08 17:05:05 +01:00
"@replayio/jest": "27.2.35",
"@replayio/playwright": "1.1.8",
"@replayio/replay": "0.20.1",
Omit svg static imports if custom webpack config is defined (#26281) This PR does a couple things: 1. Omit svg static imports if the user has defined custom webpack config with svg rule 2. Change TS type to `any` for svg imports to avoid conflicts with other plugins The idea is that some users want to use `next/image` with static imports for most image types but not for svg and instead inline those images with a plugin. - Fixes #25950 - Fixes #26130 - Fixes #26176 - Fixes #26196 - Fixes #26067 ## Bug - [x] Related issues linked using Fixes #26130 - [x] Integration tests added
2021-06-18 02:40:22 +02:00
"@svgr/webpack": "5.5.0",
dep: upgrade @swc/core v1.2.148 , @swc/cli v0.1.55 (#35054) ## Feature Upgrades `@swc/core` to `1.2.148`, which includes this critical fix https://github.com/swc-project/swc/pull/3824 Also upgrades `@swc/cli` to `v0.1.55`
2022-03-05 22:45:30 +01:00
"@swc/cli": "0.1.55",
Update `@swc/core` npm package to `v1.6.6` (#67379) ### What? Update `@swc/core` to the latest. ### Why? To keep in sync.
2024-07-03 02:54:28 +02:00
"@swc/core": "1.6.6",
build: Update `@swc/core` to `v1.5.0` (#65022) ### What? Update `@swc/core` npm package. ### Why? To keep in sync. ### How? Closes https://linear.app/vercel/issue/SWC-119/
2024-04-26 07:46:59 +02:00
"@swc/helpers": "0.5.11",
feat(turbopack-ecmascript): use import attributes for annotations (#59370)
2024-05-16 04:58:43 +02:00
"@swc/types": "0.1.7",
fix(next-swc): skips client/server only checks when running with Jest to unblock testing (#54891) Co-authored-by: Jiachi Liu <inbox@huozhi.im>
2023-09-04 13:53:41 +02:00
"@testing-library/jest-dom": "6.1.2",
Bump `@testing-library/react` to 15.0.3 (from 13.x) (#65119) Closes NEXT-3247
2024-04-29 11:11:27 +02:00
"@testing-library/react": "^15.0.5",
[actions] Enforce body limit using Transform stream (#64694) <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> ### What? This ensures that the body limit option is enforced on all request bodies sent to the Node.js runtime, not just the multipart field size limits. ### Why? The documentation states that this should limit the body size, previously it only limited the field size. ### How? This uses a `Transform` stream from Node.js. [Based on my benchmarks](https://gist.github.com/wyattjoh/c470d98095da2f95f5920396aba2a206) using the transform stream added next to no overhead, yet it did simplify the implementation quite a bit. Assuming this is due to the already performant stream support within Node.js. Closes NEXT-3151
2024-04-19 00:04:20 +02:00
"@types/busboy": "1.5.3",
SSG Preview Mode (#10459) * checkpoint: api impl * Add support for tryGetPreviewData * snapshot: server(less) support * Add X-Prerender-Bypass-Mode header support * Pass preview data to getStaticProps call * add TODO * setPreviewData * 100k iterations * Handle jwt error * Write out preview values * forgot file * set preview props * Send preview props * add preview props * Pass around more data * update yarn lock * Fail on Invalid Prerender Manifest * Make Missing Prerender Manifest Fatal * fix ts errors * fix test * Fix setting cookies + maxage * Secure is not needed as we encrypt necessary data * Set on domain root * Set cookie max ages * Render a fallback on-demand for non-dynamic pages * Test preview mode * remove old build * remove snapshots * Add serverless tests * use afterAll * Remove object assigns * fix cookie spread * add comment
2020-02-12 02:16:42 +01:00
"@types/cheerio": "0.22.16",
type check tests (and convert next-test-utils.js to ts) (#51071) Enables type checking for tests in CI and fixes a bunch of things related to that
2023-06-23 19:42:50 +02:00
"@types/cookie": "0.3.3",
"@types/cross-spawn": "6.0.0",
Experimental: React Refresh Support (#12008) * Add Fast Refresh Support * Add Basic Acceptance Test * Increase delay * fix version * Ignore test files * Update packages/next/build/webpack/loaders/next-babel-loader.js * Copy tests * Redo test style * drop directory * fix compile * fix remove function * Update helpers
2020-04-19 19:58:31 +02:00
"@types/fs-extra": "8.1.0",
type check tests (and convert next-test-utils.js to ts) (#51071) Enables type checking for tests in CI and fixes a bunch of things related to that
2023-06-23 19:42:50 +02:00
"@types/glob": "7.1.1",
Update image tests files from *.js to *.ts (#39663) Let's utilize typescript for our tests
2022-08-17 01:29:55 +02:00
"@types/html-validator": "5.0.3",
Add support for rewriting to external resources (#10041) * Add support for rewriting to external resources * Update rewrite proxying test Co-authored-by: Tim Neutkens <tim@timneutkens.nl> Co-authored-by: Joe Haddad <timer150@gmail.com>
2020-02-04 20:08:03 +01:00
"@types/http-proxy": "1.17.3",
chore: upgrade `jest` (#56909) ### What? Upgrade jest to its latest version ### Why? #56899 fails because historically Jest stripped the globals in Node.js, but 28+ isn't doing that anymore. If we upgrade, we don't have to keep track of Node.js globals and when they are added. This will be useful in removing even more polyfills for things that are natively shipped in Node.js now. ### How? Jest 29 introduced a change to the snapshot format: https://jestjs.io/blog/2022/08/25/jest-29 First, I tried setting the old compat option to not require updating snapshots, but some tests were still failing: https://dev.azure.com/nextjs/next.js/_build/results?buildId=70633&view=logs&j=8af7cf9c-43a1-584d-6f5c-57bad8880974&t=7ae70e63-3625-50f4-6764-5b3e72b4bd7a&l=273 So going through the pain now instead.
2023-10-19 19:38:24 +02:00
"@types/jest": "29.5.5",
Upgrade typescript to 5.3 (#64043) Closes NEXT-2997 --------- Co-authored-by: eps1lon <sebastian.silbermann@vercel.com>
2024-04-17 18:35:29 +02:00
"@types/node": "20.12.3",
Subresource Integrity for App Directory (#39729) <!-- Thanks for opening a PR! Your contribution is much appreciated. In order to make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change that you're making: --> This serves to add support for [Subresource Integrity](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity) hashes for scripts added from the new app directory. This also has support for utilizing nonce values passed from request headers (expected to be generated per request in middleware) in the bootstrapping scripts via the `Content-Security-Policy` header as such: ``` Content-Security-Policy: script-src 'nonce-2726c7f26c' ``` Which results in the inline scripts having a new `nonce` attribute hash added. These features combined support for setting an aggressive Content Security Policy on scripts loaded. ## 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. - [x] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm lint` - [x] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples) Co-authored-by: Steven <steven@ceriously.com>
2022-09-09 00:17:15 +02:00
"@types/node-fetch": "2.6.1",
Bump React types to 19 rc (#66186)
2024-05-27 18:19:41 +02:00
"@types/react": "npm:types-react@19.0.0-rc.0",
"@types/react-dom": "npm:types-react-dom@19.0.0-rc.0",
chore: upgrade to TypeScript 5.2.2 (#55105) ### What? Upgrade TypeScript to the latest version as of this PR. **This does not affect users, as the change is only for our repository.** ### Why? Part of some upcoming PRs to try to clean up cookie handling, now that `getSetCookie` is available. Since we use `undici`, which [implements it](https://github.com/nodejs/undici/pull/1915), we can get rid of some code to rely more on the platform. This PR is needed to get the types for `Headers#getSetCookie` which was added in 5.2 ### How? I needed to update some dependency types to get build to pass, but other than that, only needed to bump from `5.1.6` to `5.2.2`, so hopefully all is fine.
2023-09-07 20:46:05 +02:00
"@types/relay-runtime": "14.1.13",
amp-bind data injection (#6840)
2019-04-02 16:09:34 +02:00
"@types/string-hash": "1.1.1",
Upgrade `@types/react` to latest 18.x (#48645) Required for https://github.com/vercel/next.js/pull/48641 [React 18 types changelog](https://github.com/DefinitelyTyped/DefinitelyTyped/pull/56210) Revealed some bugs in `React.Children` typings that were hidden due to `{}` being part of `ReactNode` before 18.x types. The rest is mostly missing `children` props types.
2023-04-21 11:33:23 +02:00
"@types/trusted-types": "2.0.3",
chore: bump typescript-eslint to 6.14 (#59514)
2023-12-12 11:27:15 +01:00
"@typescript-eslint/eslint-plugin": "6.14.0",
"@typescript-eslint/parser": "6.14.0",
Run and report benchmarks (#66851) Using `@vercel/devlow-bench`, this benchmarks changes landed on canary and reports results to Datadog.
2024-06-18 20:11:15 +02:00
"@vercel/devlow-bench": "0.3.1",
Use @vercel/fetch for run-tests requests (#27815) * Use @vercel/fetch for run-tests requests * update precompileld
2021-08-06 17:20:05 +02:00
"@vercel/fetch": "6.1.1",
Upgrade @vercel/og (#60205) Upgrade `@vercel/og` to `0.6.2` for wasm oversize problem
2024-01-04 13:02:40 +01:00
"@vercel/og": "0.6.2",
Upgrade dependencies (#7412) * :arrow_up: Upgrade workspace dependencies * Run new prettier against examples * Upgrade some next-server packages * Upgrade Next.js dependencies * Upgrade webpack deps * Upgrade async sema * Fix compilation * Revert broken plugin
2019-05-23 09:52:36 +02:00
"abort-controller": "3.0.0",
chore: Add Alex to lint documentation (#26354) This Pull Request adds [Alex](https://alexjs.com/) to our documentation. It catches insensitive, inconsiderate writing. The original PR (https://github.com/vercel/next.js/pull/25821) is too large so I have decided to break it down into smaller PRs. This PR is the first part. Then I will continue to add the rest of the documentation in smaller PRs. ## More Information on Alex: https://alexjs.com/ https://github.com/get-alex/alex ## Documentation / Examples - [x] Make sure the linting passes
2021-06-22 18:03:12 +02:00
"alex": "9.1.0",
Revert "Vendor @vercel/og and expose ImageResponse (#47657" (#47711) Reverts vercel/next.js#47657
2023-03-30 21:24:02 +02:00
"amphtml-validator": "1.0.35",
Optimize test setup (#8644) * Tweak test set-up * Update azure config * Add cleaning test files and windows handling * Limit windows test to one at a time * Tweak test settings * Update tests splitting * remove custom concurrency for azure * Test Azure var * Update Azure config * bump * Simplify cleaning up
2019-09-10 19:11:55 +02:00
"async-sema": "3.0.1",
Upgrade react@beta (#65845) Ensures `useMemoCache` is available for the React Compiler. Required for #65804 without having to manually enable experimental React through e.g. taint: true. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> --------- Co-authored-by: Jiachi Liu <inbox@huozhi.im>
2024-05-16 21:59:47 +02:00
"babel-plugin-react-compiler": "0.0.0-experimental-c23de8d-20240515",
chore(deps): update `browserslist` and `caniuse-lite` (#60827) Closes #57872 Closes NEXT-2152
2024-01-18 17:14:38 +01:00
"browserslist": "4.22.2",
Update test config (#43661) Updates our test config to take advantage of more concurrency and also updates to leverage the playwright docker image to reduce flakes from actions/setup-node stalling or playwright dependencies stalling on `apt install`. This reduces our test times from upwards of 30 minutes down to back around 15 minutes.
2022-12-04 04:49:00 +01:00
"buffer": "5.6.0",
Pinned dependencies
2017-02-16 23:53:39 +01:00
"cheerio": "0.22.0",
Upgrade deps (#12700)
2020-05-11 02:48:57 +02:00
"cookie": "0.4.1",
Bypass OPTIONS handling for API routes (#12978)
2020-05-16 23:15:12 +02:00
"cors": "2.8.5",
Upgrade dependencies (#7412) * :arrow_up: Upgrade workspace dependencies * Run new prettier against examples * Upgrade some next-server packages * Upgrade Next.js dependencies * Upgrade webpack deps * Upgrade async sema * Fix compilation * Revert broken plugin
2019-05-23 09:52:36 +02:00
"coveralls": "3.0.3",
Update to leverage pnpm for monorepo (#37259) * Update to leverage pnpm for monorepo * update compiled * update stats action * update ci install step * update ci * add test dep * update invoking scripts * update caching * skip cache for now * update dep * update packages and fix babel * update compiled * update lint * update test * update ci * update pnpm store caching * update path for windows * update restore-key config * update caching * remove extra build azure stage * re-add checkout * update setting pnpm store * bump * remove azure caching as pnpm is faster to download * update contributing * apply suggestions * remove install-peers * prepublish -> prepublishOnly * prepublish -> prepublishOnly more * more yarn -> pnpm references * more yarn -> pnpm references take 2 * use workspace protocol for root package.json Co-authored-by: Steven <steven@ceriously.com>
2022-05-29 06:35:16 +02:00
"create-next-app": "workspace:*",
Css optimizations (#16539) Co-authored-by: JJ Kasper <jj@jjsweb.site>
2020-12-01 19:02:07 +01:00
"critters": "0.0.6",
Add selenium-webdriver and testing cross-browser in PRs (#9821) * Migrate from wd to selenium-webdriver * Add chaining for next-webdriver * Re-add browserStackLocal global for teardown * Add additional element methods * Use freshWindow helper for chrome * Add selenium-server * Add cross-env for windows compat * Fix single quote windows * Update production preload tests * Update preload tests count * Update CircleCi for testing other browsers * Update CI configs * Update config * Add browser.url command * Add more methods * Update xcode version * Make sure to add chromedriver to path * Add forceExit flag * Update config * Update config * Disable safari * Fix bug in test * Add teardown logging * Update jest teardown * Move testing ie11 to Azure * Update job names * Remove force exiting on long teardown * Update Azure config * Re-add safari testing with BrowserStack * Update config * Update prefetch tests for ie11 * Update prefetch for safari and ids for ie11 testing * trigger prefetching manually in ie
2019-12-26 21:01:22 +01:00
"cross-env": "6.0.3",
Remove cross-spawn (#6450)
2019-02-26 21:57:32 +01:00
"cross-spawn": "6.0.5",
Update dd-trace used for internal tools (#54214) This is only used for internal tools :thumbsup:
2023-08-18 15:55:22 +02:00
"dd-trace": "4.12.0",
Move resolve-url-loader into Next.js (#32932) * Move resolve-url-loader into Next.js Fixes #32157 Moves resolve-url-loader into Next.js and strips out all features that are not used like `rework` support. Will reduce install size as well as allow for optimizing the approach in the near future. * Update precompiled * Use loader-utils 2 * Update trace test * Revert "Update trace test" This reverts commit 7c09a07871cc0ab72d5fcd4151a2d8efbc1aad8f. * Add es5-ext as it's used in trace tests * Update join-function.js * Update bundle5.js
2022-01-02 23:16:17 +01:00
"es5-ext": "0.10.53",
CSS Support Customization (#9502) * CSS Support Customization * Sort imports * Correct PostCSS plugin loading * Add css customization test * Test "bad" css configuration * Add load config test * adjust spacing * adjust spacing 2x * Only allow config through JSON * Support excluding false plugins * Test tailwind css behavior * Test plugin exclusion * Fix unit test * Fix config file * Remove more variants * Update test cases
2019-11-25 22:52:29 +01:00
"escape-string-regexp": "2.0.0",
chore: update ESLint and plugins to latest (#61544) Bumping ESLint to the newest version. Related: #61525 Closes NEXT-2336
2024-02-02 02:06:02 +01:00
"eslint": "8.56.0",
add version step for publish
2022-05-29 21:59:38 +02:00
"eslint-config-next": "workspace:*",
chore: update ESLint and plugins to latest (#61544) Bumping ESLint to the newest version. Related: #61525 Closes NEXT-2336
2024-02-02 02:06:02 +01:00
"eslint-formatter-codeframe": "7.32.1",
"eslint-plugin-eslint-plugin": "5.2.1",
"eslint-plugin-import": "2.29.1",
"eslint-plugin-jest": "27.6.3",
"eslint-plugin-jsdoc": "48.0.4",
"eslint-plugin-react": "7.33.2",
"eslint-plugin-react-hooks": "4.6.0",
Fix missing trace script devDependencies (#38172) Adds missing devDependencies required by the `trace-to-tree.mjs` script used here to the workspace root. https://github.com/vercel/next.js/blob/c64af8aa34775b700bf22f62585ffe514f8b2004/scripts/trace-to-tree.mjs#L2-L3
2022-06-29 22:57:51 +02:00
"event-stream": "4.0.1",
Add Create Next App package (#8018) * Add Create Next App package * Fix Create Next App tests * Fix company name * Update package.json
2019-07-17 22:53:56 +02:00
"execa": "2.0.3",
fix: InferGetServerSidePropsType and InferGetStaticPropsType (#40635) ## Problem Currently the Next.js infer utility (`InferGetServerSidePropsType` and `InferGetStaticPropsType`) types can lead to a wrong inferred types (`never`). This happens if these functions return something different than: `{props: {}}`. **Example:** `getServerSideProps` ```typescript export async function getServerSideProps({ query }: GetServerSidePropsContext) { if (query.foo) { return { notFound: true, } } return { props: { foo: "bar" }, } } type PageProps = InferGetServerSidePropsType<typeof getServerSideProps> // => type PageProps = never ``` **Example:** `getStaticProps` ```typescript import type { InferGetStaticPropsType, GetStaticPropsContext } from 'next' export async function getStaticProps(context: GetStaticPropsContext) { if (context.params?.bar) { return { notFound: true, } } return { props: { foo: 'bar', }, } } type PageProps = InferGetStaticPropsType<typeof getStaticProps> // => type PageProps = never ``` This is because the first infer condition of the utility type is not satified leading to a never result. ```typescript export type InferGetServerSidePropsType<T> = T extends GetServerSideProps< infer P, // <- NOT SATISFIED any > ? P : T extends ( context?: GetServerSidePropsContext<any> ) => Promise<GetServerSidePropsResult<infer P>> ? P : never // <- NOT SATISFIED ``` ## Solution I have experimented with different solutions ending with a much simpler type, that is faster to execute, easier to read and universally usable for both prop variations. ```typescript /** * Flow: * - Make sure getStaticProps is a function * - Get its return type * - Extract the one that contains {props: any} * - Return the props */ export type InferGetStaticPropsType<T extends (args: any) => any> = Extract< Awaited<ReturnType<T>>, { props: any } >['props'] ``` ## Bug - [x] Related issues: fixes #36615, #15913, https://twitter.com/leeerob/status/1563540593003106306 - [x] Type tests added ## Future thoughts Since `InferGetStaticPropsType` and `InferGetServerSidePropsType` are now the same, it's api could be merged into one utility type (e.g: InferNextProps). I recommend doing this in a different PR. ## Additional info I have tested this approach using the following [external package](https://www.npmjs.com/package/infer-next-props-type) (@timneutkens sorry for the late PR). Since about 12 Month I haven't received any negative feedback (issues) regarding this approach. Co-authored-by: JJ Kasper <jj@jjsweb.site>
2022-09-21 00:25:01 +02:00
"expect-type": "0.14.2",
Upgrade dependencies (#7412) * :arrow_up: Upgrade workspace dependencies * Run new prettier against examples * Upgrade some next-server packages * Upgrade Next.js dependencies * Upgrade webpack deps * Upgrade async sema * Fix compilation * Revert broken plugin
2019-05-23 09:52:36 +02:00
"express": "4.17.0",
Add runtime to hotUpdateMainFilename (#26256) Updates the hotUpdateChunk to include `[runtime]` for web workers support. Fixes #26152 Fixes #19865 Fixes #26144 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added ## 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. ## Documentation / Examples - [ ] Make sure the linting passes
2021-06-18 19:12:20 +02:00
"faker": "5.5.3",
Add support for legacy server npm modules (#7898) Notably, this PR fixes `faunadb` which relies on `formidable`. n.b. `formidable` is an unmaintained legacy npm package that uses practices not compatible with the modern ecosystem.
2019-07-11 19:02:43 +02:00
"faunadb": "2.6.1",
Update test config (#43661) Updates our test config to take advantage of more concurrency and also updates to leverage the playwright docker image to reduce flakes from actions/setup-node stalling or playwright dependencies stalling on `apt install`. This reduces our test times from upwards of 30 minutes down to back around 15 minutes.
2022-12-04 04:49:00 +01:00
"find-up": "4.1.0",
Update firebase to fix install errors on node 14 (#13493) Running ``` yarn ``` in the project while on node.js 14 results into errors with the `grpc` dependency of `firebase`. Updating `firebase` fixes that.
2020-05-29 01:23:35 +02:00
"firebase": "7.14.5",
feat(trace): postprocess trace reporter for datadog (#35032) * feat(trace): include clocktime for span * build(package): bump up devdependencies * feat(trace): postprocess trace reporter for datadog * build(package): update precompile pkgs * update compiled Co-authored-by: JJ Kasper <jj@jjsweb.site>
2022-03-08 17:15:09 +01:00
"flat": "5.0.2",
remove mkdirp, bump fs-extra to 9.0.0 (#11251) * bump mkdirp to 1.0.3, which support promise * fix mkdirp in spr-cache.ts * bump fs-extra to 9.0.0 * remove mkdirp
2020-03-21 17:02:05 +01:00
"fs-extra": "9.0.0",
Upgrade deps (#12700)
2020-05-11 02:48:57 +02:00
"get-port": "5.1.1",
test(fixture): improve finding ports to reduce flaky (#55151) ### What Found a flaky test like https://github.com/vercel/next.js/actions/runs/6125719281/job/16628276301?pr=55118#step:29:174, `get-port` throws by port is not available. Peeking bit, there seems an upstream fix hope to improve the situation but unfortunately it happened after get-port switched to native esm only, so bumping is non trivial work. Instead adapting get-port-please as a replacwement but leave get-port as fallback for a while to verify its stability. Once we are certain, we can remove old get-port entirely.
2023-09-11 23:48:29 +02:00
"get-port-please": "3.1.1",
Migrate PR stats action into Next.js repo (#13177) * Migrate PR stats into Next.js repo * Update running prettier in local mode
2020-05-21 14:07:27 +02:00
"glob": "7.1.6",
"gzip-size": "5.1.1",
fix(next/image): render valid html according to W3C (#33825) ## Bug - [x] Fixes #33809 - [x] Related to #33218 - [x] Integration tests added: Usage of [html-validator](https://www.npmjs.com/package/html-validator) to validate the HTML. - [x] Errors have helpful link attached, see `contributing.md` (N/A)
2022-02-01 01:13:46 +01:00
"html-validator": "5.1.18",
Update test config (#43661) Updates our test config to take advantage of more concurrency and also updates to leverage the playwright docker image to reduce flakes from actions/setup-node stalling or playwright dependencies stalling on `apt install`. This reduces our test times from upwards of 30 minutes down to back around 15 minutes.
2022-12-04 04:49:00 +01:00
"http-proxy": "1.18.1",
refactor: remove unnecessary `lint-staged` operations (#65861) ### Why? The current `lint-staged` hook uses [function signature](https://github.com/lint-staged/lint-staged?tab=readme-ov-file#function-signature) to target the **staged files** and has extra steps for handling those files that seem to have been passed on from a [5-year-old legacy code](https://github.com/vercel/next.js/pull/9245). The entire process is unnecessary today since `lint-staged` only runs on the staged files. ### How? This PR removed unnecessary logic, removed some no-effect flags, and [removed `git add`](https://github.com/lint-staged/lint-staged?tab=readme-ov-file#v10). > If your task previously contained a git add step, please remove this. --------- Co-authored-by: Sam Ko <sam@vercel.com>
2024-05-30 02:56:30 +02:00
"husky": "9.0.11",
feat(next/image)!: remove `squoosh` in favor of `sharp` as optional dependency (#63321) ## History Previously, we added support for `squoosh` because it was a wasm implementation that "just worked" on all platforms when running `next dev` for the first time. However, it was slow so we always recommended manually installing `sharp` for production use cases running `next build` and `next start`. Now that [`sharp` supports webassembly](https://sharp.pixelplumbing.com/install#webassembly), we no longer need to maintain `squoosh`, so it can be removed. We also don't need to make the user install sharp manually because it can be installed under `optionalDependencies`. I left it optional in case there was some platform that still needed to manually install the wasm variant with `npm install --cpu=wasm32 sharp` such as codesandbox/stackblitz (I don't believe sharp has any fallback built in yet). Since we can guarantee `sharp`, we can also remove `get-orientation` dep and upgrade `image-size` dep. I also moved an [existing `sharp` test](https://github.com/vercel/next.js/pull/56674) into its own fixture since it was unrelated to image optimization. ## Related Issues - Fixes https://github.com/vercel/next.js/issues/41417 - Related https://github.com/vercel/next.js/pull/54670 - Related https://github.com/vercel/next.js/issues/54708 - Related https://github.com/vercel/next.js/issues/44804 - Related https://github.com/vercel/next.js/issues/48820 - Related https://github.com/vercel/next.js/pull/61810 - Related https://github.com/vercel/next.js/pull/61696 - Related https://github.com/vercel/next.js/issues/44685 - Closes https://github.com/vercel/next.js/issues/64362 ## Breaking Change This is a breaking change because newer versions of `sharp` no longer support `yarn@1`. - https://github.com/lovell/sharp/issues/3750 The workaround is to install with `yarn --ignore-engines` flag. Also note that Vercel no longer defaults to yarn when no lockfile is found - https://github.com/vercel/vercel/pull/11131 - https://github.com/vercel/vercel/pull/11242 Closes NEXT-2823
2024-04-25 20:01:56 +02:00
"image-size": "1.1.1",
Fix animated png bypass from Image Optimization API (#35120) - Fixes #34807 - Related commit https://github.com/qzb/is-animated/commit/69dad3cdf9622cc0bde4ee8c716366b0eef7e627 Co-authored-by: JJ Kasper <22380829+ijjk@users.noreply.github.com>
2022-03-07 21:29:11 +01:00
"is-animated": "2.0.2",
Add tests for isomorphic-unfetch bundling issue (#5805) * Add tests for isomorphic-unfetch bundling issue * Remove unneeded extra option * Remove isomorphic-fetch
2018-12-04 10:59:12 +01:00
"isomorphic-unfetch": "3.0.0",
chore: upgrade `jest` (#56909) ### What? Upgrade jest to its latest version ### Why? #56899 fails because historically Jest stripped the globals in Node.js, but 28+ isn't doing that anymore. If we upgrade, we don't have to keep track of Node.js globals and when they are added. This will be useful in removing even more polyfills for things that are natively shipped in Node.js now. ### How? Jest 29 introduced a change to the snapshot format: https://jestjs.io/blog/2022/08/25/jest-29 First, I tried setting the old compat option to not require updating snapshots, but some tests were still failing: https://dev.azure.com/nextjs/next.js/_build/results?buildId=70633&view=logs&j=8af7cf9c-43a1-584d-6f5c-57bad8880974&t=7ae70e63-3625-50f4-6764-5b3e72b4bd7a&l=273 So going through the pain now instead.
2023-10-19 19:38:24 +02:00
"jest": "29.7.0",
"jest-environment-jsdom": "29.7.0",
"jest-extended": "4.0.2",
ci(workflow): enable test trace upload (#51107) ### What? WEB-1150. This PR is an attempt to upload next.js's test results into datadog test trace to track its status. Originally it tried to use automatic trace injection (dd-trace/ci/init). However, due to some of custom environments / setup we use it was not compatible out of the box. Instead, this PR injects a new test reportert to generate junit report, then upload it at once at the end of the testing pipeline. The reporter is configured to run when necessary variables set, local run should not be affected. One thing to note is this report will not count retry results, as it'll create duplicated test entry with multiple results since we runts jest per individual test. This'll allow to detect flaky test easier, but also it means we'll get bit of skewed test results compare to the real world as first failure will be accounted as test fail immediately.
2023-06-12 19:14:13 +02:00
"jest-junit": "16.0.0",
Update json5 dependency to latest (#44548) Updates to latest version of the dependency.
2023-01-04 00:45:05 +01:00
"json5": "2.2.3",
Update Turbopack test manifest from GitHub Actions artifact (#58394) ### What? We can use the GitHub actions artifact (which is already produced right now) instead of a separate git branch to get the latest test results. This also means we don't have a dependency back to the turbo repo for the daily tests. Closes PACK-1951
2023-11-24 16:48:12 +01:00
"kleur": "^4.1.0",
Make fetch polyfill work with ky-universal (#12804)
2020-05-12 21:58:21 +02:00
"ky": "0.19.1",
"ky-universal": "0.6.0",
Upgrade to lerna 4 (#22039) Co-authored-by: Tim Neutkens <timneutkens@me.com>
2021-02-12 13:34:25 +01:00
"lerna": "4.0.0",
refactor: remove unnecessary `lint-staged` operations (#65861) ### Why? The current `lint-staged` hook uses [function signature](https://github.com/lint-staged/lint-staged?tab=readme-ov-file#function-signature) to target the **staged files** and has extra steps for handling those files that seem to have been passed on from a [5-year-old legacy code](https://github.com/vercel/next.js/pull/9245). The entire process is unnecessary today since `lint-staged` only runs on the staged files. ### How? This PR removed unnecessary logic, removed some no-effect flags, and [removed `git add`](https://github.com/lint-staged/lint-staged?tab=readme-ov-file#v10). > If your task previously contained a git add step, please remove this. --------- Co-authored-by: Sam Ko <sam@vercel.com>
2024-05-30 02:56:30 +02:00
"lint-staged": "15.2.2",
Update test config (#43661) Updates our test config to take advantage of more concurrency and also updates to leverage the playwright docker image to reduce flakes from actions/setup-node stalling or playwright dependencies stalling on `apt install`. This reduces our test times from upwards of 30 minutes down to back around 15 minutes.
2022-12-04 04:49:00 +01:00
"lodash": "4.17.20",
Fix build stalling with styled-jsx plugins (#12952)
2020-05-15 23:15:15 +02:00
"lost": "8.3.1",
Migrate PR stats action into Next.js repo (#13177) * Migrate PR stats into Next.js repo * Update running prettier in local mode
2020-05-21 14:07:27 +02:00
"minimatch": "3.0.4",
Initial optimizeLibraries experimental flag (#8345) * Add experimental optimizeLibraries flag, currently prunes Moment.js locales * expose moment for use in assertion * try with the same setup as the production integration test * Apply optimiztaions in dev and on server so they're consistent. * fix build (oh dear) * Update index.test.js * Rename flag to future.excludeDefaultMomentLocales * Adjust impl
2019-08-20 21:19:45 +02:00
"moment": "^2.24.0",
Update to leverage pnpm for monorepo (#37259) * Update to leverage pnpm for monorepo * update compiled * update stats action * update ci install step * update ci * add test dep * update invoking scripts * update caching * skip cache for now * update dep * update packages and fix babel * update compiled * update lint * update test * update ci * update pnpm store caching * update path for windows * update restore-key config * update caching * remove extra build azure stage * re-add checkout * update setting pnpm store * bump * remove azure caching as pnpm is faster to download * update contributing * apply suggestions * remove install-peers * prepublish -> prepublishOnly * prepublish -> prepublishOnly more * more yarn -> pnpm references * more yarn -> pnpm references take 2 * use workspace protocol for root package.json Co-authored-by: Steven <steven@ceriously.com>
2022-05-29 06:35:16 +02:00
"nanoid": "3.1.30",
add version step for publish
2022-05-29 21:59:38 +02:00
"next": "workspace:*",
chore(deps): upgrade `node-fetch` (#33466) Fixes #33462 Tried upgrading to v3, but we rely on the `timeout` property: https://github.com/vercel/next.js/blob/e5dee17f776dcc79ebb269f7b7341fa6e2b6c3f1/packages/next/telemetry/post-payload.ts#L12 Which was removed since it's non-standard: https://github.com/node-fetch/node-fetch/blob/main/docs/v3-UPGRADE-GUIDE.md#the-timeout-option-was-removed I wanted to keep this PR minimal, so I did not try to work around the above. ## 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 `yarn lint`
2022-01-19 17:48:11 +01:00
"node-fetch": "2.6.7",
feat(turbo): use turbo gen instead of plop (#53684) ### What? Use [Turborepo generators](https://turbo.build/repo/docs/core-concepts/monorepos/code-generation#custom-generators) instead of plop. Turborepo generators are built on top of plop, but include some additional tooling to make working in monorepos easier. It also supports zero config typescript for configs. ### Why? Same Team! ### How? Ported the existing plopfile to a turbo generator config Co-authored-by: Jiachi Liu <4800338+huozhi@users.noreply.github.com>
2023-11-03 02:25:18 +01:00
"node-plop": "0.31.1",
Revert "chore: drop `npm-run-all`" (#62700) Reverts vercel/next.js#62642 Closes NEXT-2650
2024-02-29 22:59:24 +01:00
"npm-run-all": "4.1.5",
Add CSS Resolve Test (#9724)
2019-12-12 16:51:38 +01:00
"nprogress": "0.2.0",
Add update fonts workflow (#53645) This adds a workflow to auto update our fonts data so we can stay up to date easier. Closes: https://github.com/vercel/next.js/pull/53246 Closes: https://github.com/vercel/next.js/pull/53510
2023-08-07 02:11:03 +02:00
"octokit": "3.1.0",
refactor tests for readability (#51051) You'll probably want to disable whitespace in the diff ## Description This allows for better editor support by using `describe` or functions called `describe` with the same syntax instead of custom names. Changes: - `nextTestSetup` can be used instead of `createNextDescribe` keeping the same behaviour but being called inside a `describe` "block" (not applied everywhere) - `getSnapshotTestDescribe` replaced with a custom `describe.each` - `sandbox` helper function for `acceptance`/`acceptance-app` merged into a single shared one - `outdent` to remove the indent from inline files in tests which helps with consistent snapshots
2023-06-21 21:47:21 +02:00
"outdent": "0.8.0",
Redesign PostCSS Configuration Loading (#9704) * Redesign PostCSS Configuration Loading * Test array configuration * Test new configuration handling * Remove unnecessary async
2019-12-11 17:51:10 +01:00
"pixrem": "5.0.0",
refactor(tests): make chain more "correct" (#51728) ### Why? I really dislike the way `.chain` works right now, it shouldn't mutate the `BrowserInterface`, this PR changes it so it's just a pure chain without weird side effects. One example with the current version (before this PR): ``` const el = browser.elementByCss('#version-2') await el.text() // throws await el.text() ``` ### Additional Changes - removes selenium (which is completely unused) - updates playwright - makes the playwright tracing not error all the time
2024-02-14 20:14:24 +01:00
"playwright": "1.41.2",
"playwright-chromium": "1.41.2",
chore: bump `postcss` (#56225) Co-authored-by: JJ Kasper <22380829+ijjk@users.noreply.github.com>
2023-09-29 23:57:35 +02:00
"postcss": "8.4.31",
Fix build stalling with styled-jsx plugins (#12952)
2020-05-15 23:15:15 +02:00
"postcss-nested": "4.2.1",
Redesign PostCSS Configuration Loading (#9704) * Redesign PostCSS Configuration Loading * Test array configuration * Test new configuration handling * Remove unnecessary async
2019-12-11 17:51:10 +01:00
"postcss-pseudoelements": "5.0.0",
CSS Support Customization (#9502) * CSS Support Customization * Sort imports * Correct PostCSS plugin loading * Add css customization test * Test "bad" css configuration * Add load config test * adjust spacing * adjust spacing 2x * Only allow config through JSON * Support excluding false plugins * Test tailwind css behavior * Test plugin exclusion * Fix unit test * Fix config file * Remove more variants * Update test cases
2019-11-25 22:52:29 +01:00
"postcss-short-size": "4.0.0",
"postcss-trolling": "0.1.7",
Updates prettier to latest version. (#51000) There are some incoming docs / MDX changes where prettier will throw an error when using the older version. Updating prettier before I bring in those changes. Looks like the most notable change is adding parentheses around `typeof` checks in TypeScript. **Before** ``` export type Locale = typeof i18n['locales'][number] ``` **After** ``` export type Locale = (typeof i18n)['locales'][number] ```
2023-06-09 16:58:19 +02:00
"prettier": "3.2.5",
Migrate PR stats action into Next.js repo (#13177) * Migrate PR stats into Next.js repo * Update running prettier in local mode
2020-05-21 14:07:27 +02:00
"pretty-bytes": "5.3.0",
"pretty-ms": "7.0.0",
Make traces in development reliable (#28990) Co-authored-by: Jiachi Liu <inbox@huozhi.im>
2021-09-13 15:49:29 +02:00
"random-seed": "0.3.0",
Update React from `1df34bdf62` to `6230622a1a` (#66726) <details> <summary>React upstream changes</summary> - https://github.com/facebook/react/pull/29835 </details>
2024-06-11 02:06:12 +02:00
"react": "19.0.0-rc-6230622a1a-20240610",
Update repo to use react 18 by default (#35888) This updates our `yarn next` command to leverage react v18 by default and removes the need for the test require hook/config modifying when testing react 18. There are some fixtures we need to investigate react 18 support in follow-ups: - `test/integration/client-navigation-a11y` - `test/integration/critical-css` - `test/integration/custom-error-page-exception` - `test/integration/font-optimization` - AMP specific tests
2022-04-05 23:51:47 +02:00
"react-17": "npm:react@17.0.2",
Update React from `1df34bdf62` to `6230622a1a` (#66726) <details> <summary>React upstream changes</summary> - https://github.com/facebook/react/pull/29835 </details>
2024-06-11 02:06:12 +02:00
"react-builtin": "npm:react@19.0.0-rc-6230622a1a-20240610",
"react-dom": "19.0.0-rc-6230622a1a-20240610",
Update repo to use react 18 by default (#35888) This updates our `yarn next` command to leverage react v18 by default and removes the need for the test require hook/config modifying when testing react 18. There are some fixtures we need to investigate react 18 support in follow-ups: - `test/integration/client-navigation-a11y` - `test/integration/critical-css` - `test/integration/custom-error-page-exception` - `test/integration/font-optimization` - AMP specific tests
2022-04-05 23:51:47 +02:00
"react-dom-17": "npm:react-dom@17.0.2",
Update React from `1df34bdf62` to `6230622a1a` (#66726) <details> <summary>React upstream changes</summary> - https://github.com/facebook/react/pull/29835 </details>
2024-06-11 02:06:12 +02:00
"react-dom-builtin": "npm:react-dom@19.0.0-rc-6230622a1a-20240610",
"react-dom-experimental-builtin": "npm:react-dom@0.0.0-experimental-6230622a1a-20240610",
"react-experimental-builtin": "npm:react@0.0.0-experimental-6230622a1a-20240610",
Make synced react-is version more obvious (#67189)
2024-06-26 11:16:47 +02:00
"react-is-builtin": "npm:react-is@19.0.0-rc-6230622a1a-20240610",
Update React from `1df34bdf62` to `6230622a1a` (#66726) <details> <summary>React upstream changes</summary> - https://github.com/facebook/react/pull/29835 </details>
2024-06-11 02:06:12 +02:00
"react-server-dom-turbopack": "19.0.0-rc-6230622a1a-20240610",
"react-server-dom-turbopack-experimental": "npm:react-server-dom-turbopack@0.0.0-experimental-6230622a1a-20240610",
"react-server-dom-webpack": "19.0.0-rc-6230622a1a-20240610",
"react-server-dom-webpack-experimental": "npm:react-server-dom-webpack@0.0.0-experimental-6230622a1a-20240610",
Remove experiment (#9945) * Remove experiment * Add back ssr-prepass for serverless test * Update size as they both decreased Co-authored-by: JJ Kasper <jj@jjsweb.site>
2020-01-04 17:40:18 +01:00
"react-ssr-prepass": "1.0.8",
dep: upgrade @swc/core v1.2.148 , @swc/cli v0.1.55 (#35054) ## Feature Upgrades `@swc/core` to `1.2.148`, which includes this critical fix https://github.com/swc-project/swc/pull/3824 Also upgrades `@swc/cli` to `v0.1.55`
2022-03-05 22:45:30 +01:00
"react-virtualized": "9.22.3",
Relay Support in Rust Compiler (#33702) Reverts vercel/next.js#33699 This re-opens the support for relay in swc, although we need to narrow in the causes for the build failures in https://github.com/vercel/next.js/runs/4950448889?check_suite_focus=true Co-authored-by: Andrey Lunyov <102968+alunyov@users.noreply.github.com>
2022-02-01 19:18:55 +01:00
"relay-compiler": "13.0.2",
"relay-runtime": "13.0.2",
Bump `release` to 6.3.1 (#37995)
2022-06-24 22:02:40 +02:00
"release": "6.3.1",
Upgrade dependencies (#7412) * :arrow_up: Upgrade workspace dependencies * Run new prettier against examples * Upgrade some next-server packages * Upgrade Next.js dependencies * Upgrade webpack deps * Upgrade async sema * Fix compilation * Revert broken plugin
2019-05-23 09:52:36 +02:00
"request-promise-core": "1.1.2",
Update test set-up to leverage playwright when able to (#28634) Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2021-09-13 14:36:25 +02:00
"resolve-from": "5.0.0",
Replace node-sass test dependency with sass (#39053) * Replace node-sass test dependency with sass * breakup css/scss tests for more parallelism * update compiled
2022-07-27 06:12:54 +02:00
"sass": "1.54.0",
Upgrade og dependencies (#59541) Upgrade `@vercel/og` to 0.6.1 Closes NEXT-1857
2023-12-21 14:50:57 +01:00
"satori": "0.10.9",
Update React from `1df34bdf62` to `6230622a1a` (#66726) <details> <summary>React upstream changes</summary> - https://github.com/facebook/react/pull/29835 </details>
2024-06-11 02:06:12 +02:00
"scheduler-builtin": "npm:scheduler@0.25.0-rc-6230622a1a-20240610",
"scheduler-experimental-builtin": "npm:scheduler@0.0.0-experimental-6230622a1a-20240610",
Do not alias Node modules for webpack 4 (#16452) Fixes #16259 Caused by #16022 Follow up issue: #16450 This PR skips polyfilling Node modules in webpack 4 which are ignored by the `browsers` key.
2020-08-21 20:50:24 +02:00
"seedrandom": "3.0.5",
Update to leverage pnpm for monorepo (#37259) * Update to leverage pnpm for monorepo * update compiled * update stats action * update ci install step * update ci * add test dep * update invoking scripts * update caching * skip cache for now * update dep * update packages and fix babel * update compiled * update lint * update test * update ci * update pnpm store caching * update path for windows * update restore-key config * update caching * remove extra build azure stage * re-add checkout * update setting pnpm store * bump * remove azure caching as pnpm is faster to download * update contributing * apply suggestions * remove install-peers * prepublish -> prepublishOnly * prepublish -> prepublishOnly more * more yarn -> pnpm references * more yarn -> pnpm references take 2 * use workspace protocol for root package.json Co-authored-by: Steven <steven@ceriously.com>
2022-05-29 06:35:16 +02:00
"semver": "7.3.7",
Update to latest shell-quote (#30621)
2021-10-29 18:12:46 +02:00
"shell-quote": "1.7.3",
Update test config (#43661) Updates our test config to take advantage of more concurrency and also updates to leverage the playwright docker image to reduce flakes from actions/setup-node stalling or playwright dependencies stalling on `apt install`. This reduces our test times from upwards of 30 minutes down to back around 15 minutes.
2022-12-04 04:49:00 +01:00
"strip-ansi": "6.0.0",
Pick esm main fields and condition names first for RSC server layer (#50548) For RSC server layer so far we bundle all dependencies, ESM format is the better one rather than CJS to analyze and tree-shake out the unused parts. This PR changes pick the condition names that are in ESM format first for server layer. Also fixes the misorder of condition names of edge runtime, `conditionNames` should only contain either ESM or CJS, previously the main fields are mixed with conditon names which is not expected for webpack, we separate them now. Since we're picking ESM instead CJS now, the error of require `exports * from` doesn't exist anymore, but if you're using a CJS dependency which require a ESM package, it will error. This is the existing behavior for our webpack configuration but could happen on server layer bundling Other related changes: * Imports are hoisted in ESM, so migrate`enhanceGlobals` to a imported module * Use `...` to pick the proper imports by import expression, and prefer the `react-server` / `edge-light` condition names for corresponding cases * Remove edge SSR duplicated `middleware` export checking
2023-06-08 18:24:03 +02:00
"styled-components": "6.0.0-rc.3",
Bump styled-jsx to 5.1.6 (#66185)
2024-05-27 18:05:32 +02:00
"styled-jsx": "5.1.6",
ncc 0.25.0 upgrade and fixes (#18873) This upgrades to ncc@0.25.0 and fixes the previous bugs including: * ncc not referenced correctly in build * Babel type errors * node-fetch, etag, chalk and raw-body dependencies not building with ncc - these have been "un-ncc'd" for now. As they are relatively small dependencies, this doesn't seem too much of an issue and we can follow up in the tracking ncc issue at https://github.com/vercel/ncc/issues/612. * `yarn dev` issues Took a lot of bisecting, but the overall diff isn't too bad here in the end.
2020-11-06 03:33:14 +01:00
"styled-jsx-plugin-postcss": "3.0.2",
chore(deps): bump `swr` to 2.2.4 (#61480) - Closes https://github.com/vercel/next.js/pull/61478 Closes NEXT-2319
2024-02-01 01:29:04 +01:00
"swr": "^2.2.4",
feat(cli): introduce `--tailwind` flag (#46927) ### What? This PR introduces a new `--tailwind` flag to the `create-next-app` CLI, to make it easier to bootstrap a Next.js app with Tailwind CSS pre-configured. This is going to be the **default**. To opt-out of Tailwind CSS, you can use the `--no-tailwind` flag. ### Why? Tailwind CSS is one of the most popular styling solutions right now, and we would like to make it easier to get started. Currently, the closest you can come to this is by running `pnpm create next-app -e with-tailwindcss` which will clone the https://github.com/vercel/next.js/tree/canary/examples/with-tailwindcss example. But that example is not configured for the App Router. This PR will let you add Tailwind CSS to both `app/`, `pages/`, and start out with TypeScript or JavaScript via the CLI prompts. (Some community feedback https://twitter.com/dev_jonaskaas/status/1632367991827443713, https://twitter.com/samselikoff/status/1634662473331617794) ### How? We are adding 4 new templates to the CLI bundle. > Note: The styling is not pixel-perfect compared to the current templates (using CSS modules) to require fewer overrides, but I tried to match it as close as possible. Here are a few screenshots: <details> <summary><b>Current, light</b></summary> <img src="https://user-images.githubusercontent.com/18369201/224733372-9dba86fe-9191-471d-ad9f-ab904c47f544.png"/> </details> <details> <summary><b>Tailwind (new), light</b></summary> <img src="https://user-images.githubusercontent.com/18369201/224733610-038d9d0f-634d-4b69-b5c2-a5056b56760c.png"/> </details> <details> <summary><b>Current, dark, responsive</b></summary> <img src="https://user-images.githubusercontent.com/18369201/224733790-9b4d730c-0336-4dbe-bc10-1cae1d7fd145.png"/> </details> <details> <summary><b>Tailwind (new), dark, responsive</b></summary> <img src="https://user-images.githubusercontent.com/18369201/224734375-28384bbc-2c3a-4125-8f29-c102f3b7aa1d.png"/> </details> #### For reviewers This introduces 4 new templates, with a very similar code base to the original ones. To keep the PR focused, I decided to copy over duplicate code, but we could potentially create a shared folder for files that are the same across templates to somewhat reduce the CLI size. Not sure if it's worth it, let me know. Probably fine for now, but something to consider if we are adding more permutations in the future. --- ~Work remaining:~ - [x] app+ts - [x] layout - [x] dark mode - [x] media queries - [x] animations - [x] app+js - [x] pages+ts - [x] pages+js - [x] prompt/config - [x] deprecate Tailwind CSS example in favor of CLI - [x] update docs - [x] add test - [x] add [Prettier plugin](https://github.com/tailwindlabs/prettier-plugin-tailwindcss) Closes NEXT-772 Related #45814, #44286
2023-03-16 16:06:27 +01:00
"tailwindcss": "3.2.7",
Upgrade dependencies (#2998)
2017-09-27 20:11:02 +02:00
"taskr": "1.1.0",
Bump tree-kill from 1.2.1 to 1.2.2 (#18139) Bumps [tree-kill](https://github.com/pkrumins/node-tree-kill) from 1.2.1 to 1.2.2. - [Release notes](https://github.com/pkrumins/node-tree-kill/releases) - [Commits](https://github.com/pkrumins/node-tree-kill/compare/v1.2.1...v1.2.2) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2020-10-23 09:52:37 +02:00
"tree-kill": "1.2.2",
Integrate tsec into the linting process (#33746) * Integrate tsec into the linting process * Update tsec-exemptions.json
2022-02-25 01:59:18 +01:00
"tsec": "0.2.1",
chore: bump turbo to 2.0.6-canary.0 (#67270)
2024-06-28 10:15:22 +02:00
"turbo": "2.0.6-canary.0",
Upgrade TypeScript to 5.5.3 (#67454)
2024-07-05 14:19:41 +02:00
"typescript": "5.5.3",
Update test config (#43661) Updates our test config to take advantage of more concurrency and also updates to leverage the playwright docker image to reduce flakes from actions/setup-node stalling or playwright dependencies stalling on `apt install`. This reduces our test times from upwards of 30 minutes down to back around 15 minutes.
2022-12-04 04:49:00 +01:00
"unfetch": "4.2.0",
Refactor test setup (#5391) - [x] Move jest config from npm scripts to `jest.config.js` - [x] Remove obsolete cross-env package (we don't need it anymore 🎉) - [x] Fix bug where tests are not waiting for webdriver to be ready.
2018-10-12 15:32:17 +02:00
"wait-port": "0.2.2",
chore: upgrade webpack to 5.90.0 (#61109) Dependency: upgrade webpack to latest to benefit from the bug fixes and underlying improvements Closes NEXT-2220
2024-01-25 20:18:12 +01:00
"webpack": "5.90.0",
Update test config (#43661) Updates our test config to take advantage of more concurrency and also updates to leverage the playwright docker image to reduce flakes from actions/setup-node stalling or playwright dependencies stalling on `apt install`. This reduces our test times from upwards of 30 minutes down to back around 15 minutes.
2022-12-04 04:49:00 +01:00
"webpack-bundle-analyzer": "4.7.0",
Remove notifications emitted during pnpm dev (#43801) Co-authored-by: Tim Neutkens <tim@timneutkens.nl> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2022-12-07 17:11:29 +01:00
"whatwg-fetch": "3.0.0",
Enable PPR tests for test suites (#59030) Cherry-picks #58708 without the dependency on https://github.com/vercel/next.js/pull/58779 Co-authored-by: Wyatt Johnson <633002+wyattjoh@users.noreply.github.com>
2023-11-29 04:22:45 +01:00
"ws": "8.2.3",
"yargs": "16.2.0"
Add engines to package.json (#5585) Based on this PR https://github.com/zeit/next.js/pull/5520 there should be `engines` definition in package.json as first warn. Why i choose Node 8 as minimum? @timneutkens said (https://github.com/zeit/next.js/pull/5520/files#r228330327) that next.js should work on version 7.5 but automated tests in TravisCI are with versions 8 and 10. Version 7 was development branch. I think only production ready should be recommended.
2018-11-03 17:42:43 +01:00
},
Add yarn check to tests (#9163) * Add yarn check to tests * Update yarn.lock * Update lockfile some more * Use resolutions to bump browserslist
2019-10-23 03:02:59 +02:00
"resolutions": {
chore: upgrade webpack to 5.90.0 (#61109) Dependency: upgrade webpack to latest to benefit from the bug fixes and underlying improvements Closes NEXT-2220
2024-01-25 20:18:12 +01:00
"webpack": "5.90.0",
chore(deps): update `browserslist` and `caniuse-lite` (#60827) Closes #57872 Closes NEXT-2152
2024-01-18 17:14:38 +01:00
"browserslist": "4.22.2",
"caniuse-lite": "1.0.30001579",
Upgrade typescript to 5.3 (#64043) Closes NEXT-2997 --------- Co-authored-by: eps1lon <sebastian.silbermann@vercel.com>
2024-04-17 18:35:29 +02:00
"@types/node": "20.12.3",
Update Babel dependencies (#51962) ### 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
2023-10-17 04:25:57 +02:00
"@babel/core": "7.22.5",
"@babel/parser": "7.22.5",
"@babel/types": "7.22.5",
"@babel/traverse": "7.22.5",
Bump React types to 19 rc (#66186)
2024-05-27 18:19:41 +02:00
"@types/react": "npm:types-react@19.0.0-rc.0",
"@types/react-dom": "npm:types-react-dom@19.0.0-rc.0",
Update React from `1df34bdf62` to `6230622a1a` (#66726) <details> <summary>React upstream changes</summary> - https://github.com/facebook/react/pull/29835 </details>
2024-06-11 02:06:12 +02:00
"react": "19.0.0-rc-6230622a1a-20240610",
"react-dom": "19.0.0-rc-6230622a1a-20240610",
"react-is": "19.0.0-rc-6230622a1a-20240610",
"scheduler": "0.25.0-rc-6230622a1a-20240610"
Add yarn check to tests (#9163) * Add yarn check to tests * Update yarn.lock * Update lockfile some more * Use resolutions to bump browserslist
2019-10-23 03:02:59 +02:00
},
Add engines to package.json (#5585) Based on this PR https://github.com/zeit/next.js/pull/5520 there should be `engines` definition in package.json as first warn. Why i choose Node 8 as minimum? @timneutkens said (https://github.com/zeit/next.js/pull/5520/files#r228330327) that next.js should work on version 7.5 but automated tests in TravisCI are with versions 8 and 10. Version 7 was development branch. I think only production ready should be recommended.
2018-11-03 17:42:43 +01:00
"engines": {
Bump minimum Node.js version to 18.18 (up from 18.17) (#67274)
2024-07-05 11:21:57 +02:00
"node": ">=18.18.0",
chore: update pnpm to 9.4.0 (#64945) ## Why? Notable change of v9 is Corepack is enabled by default. So we can ensure all package manage/resolved exact same version of pnpm. - [**v9.0.0**](https://github.com/pnpm/pnpm/releases/tag/v9.0.0): Discontinued support for Node.js v16 and introduced Corepack compatibility checks. New configuration updates include enabling `dedupe-injected-deps` and changing the lockfile to version 9, with better readability and resistance to Git conflicts. ... - [**v9.4.0**](https://github.com/pnpm/pnpm/releases/tag/v9.4.0) - Kudos to @ryota-murakami for the original :pr:! → https://github.com/vercel/next.js/pull/64854 ## Changes - https://pnpm.io/npmrc#link-workspace-packages defaults to `false` now, so setting it to `true` Closes NEXT-3211
2024-06-28 13:41:35 +02:00
"pnpm": "9.4.0"
Update to use latest version of pnpm (#37794) * Update to use latest version of pnpm * add packageManager field
2022-06-17 19:36:37 +02:00
},
chore: update pnpm to 9.4.0 (#64945) ## Why? Notable change of v9 is Corepack is enabled by default. So we can ensure all package manage/resolved exact same version of pnpm. - [**v9.0.0**](https://github.com/pnpm/pnpm/releases/tag/v9.0.0): Discontinued support for Node.js v16 and introduced Corepack compatibility checks. New configuration updates include enabling `dedupe-injected-deps` and changing the lockfile to version 9, with better readability and resistance to Git conflicts. ... - [**v9.4.0**](https://github.com/pnpm/pnpm/releases/tag/v9.4.0) - Kudos to @ryota-murakami for the original :pr:! → https://github.com/vercel/next.js/pull/64854 ## Changes - https://pnpm.io/npmrc#link-workspace-packages defaults to `false` now, so setting it to `true` Closes NEXT-3211
2024-06-28 13:41:35 +02:00
"packageManager": "pnpm@9.4.0",
[Memory] Add option to reduce memory usage caused by duplicate strings in webpack-sources (#66003) This PR adds a flag to Next.js to enable Webpack options to improve memory usage. See https://github.com/webpack/webpack-sources/pull/155 for a full description of the changes and impact on memory. This PR adds a patch to `webpack-sources` temporarily that contains the fixes as the real changes are iterated on to merge upstream in the `webpack/webpack-sources` repository. After that is done, the patch will be reverted and the latest `webpack-sources` version will be updated in Next.js.
2024-05-22 22:30:05 +02:00
"pnpm": {
"patchedDependencies": {
"webpack-sources@3.2.3": "patches/webpack-sources@3.2.3.patch"
}
}
initial source
2016-10-06 01:52:50 +02:00
}
Reference in a new issue Copy permalink