Commits

Breadcrumbs

History for

oncanary

User selector

All users

Datepicker

All time

Commit History

Commits on Aug 28, 2024

• Partial Fallback Prerendering (#68958)

  wyattjoh

  committedAug 28, 2024
  f4c1a40

Commits on Jul 13, 2024

• Fix typescript setup for packages/font and turbo/generators (#67687)

  unstubbable

  committedJul 13, 2024
  5bb3995

Commits on Jul 4, 2024

• Upgrade TypeScript to v5.5.2 (#67113)

  devjiwonchoi

  committedJul 4, 2024
  ce9670f

Commits on Jun 3, 2024

• Fix broken BrowserInterface type (#66461)

  unstubbable

  committedJun 3, 2024
  994d8ee

Commits on Dec 19, 2023

• chore: extends from shared base tsconfig (#59776)

  huozhi

  committedDec 19, 2023
  9d94372

Commits on Dec 13, 2023

• types: cover the tests with root tsconfig.json (#59550)

  huozhi

  committedDec 13, 2023
  61a7db6

Commits on Dec 8, 2023

• Use new JSX transform (#56294)

  

  3 peoplecommittedDec 8, 2023
  79a8d01

Commits on Oct 19, 2023

• chore: upgrade jest (#56909)

  balazsorban44

  committedOct 19, 2023
  33db463

Commits on Sep 28, 2023

• After: <img width="564" alt="CleanShot 2023-09-27 at 13 34 48@2x" src=https://github.com/vercel/next.js/commits/canary/"https://github.com/vercel/next.js/assets/11064311/c3d3f5d6-e1f6-4969-bd11-dcd191d34ce6"> <!-- 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 # -->" class="color-fg-default" href="https://github.com/vercel/next.js/commit/c2fd08063c804dcfc6e3f12cd454d7a73184504c">perf: replace zod with superstruct (#56083 After: <img width="564" alt="CleanShot 2023-09-27 at 13 34 48@2x" src=https://github.com/vercel/next.js/commits/canary/"https://github.com/vercel/next.js/assets/11064311/c3d3f5d6-e1f6-4969-bd11-dcd191d34ce6"> <!-- 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 # -->" class="color-fg-default" href="https://github.com/vercel/next.js/commit/c2fd08063c804dcfc6e3f12cd454d7a73184504c">)

  feedthejim

  committedSep 28, 2023
  c2fd080

Commits on Sep 24, 2023

• Move client-navigation test to test/development (#55888)

  timneutkens

  committedSep 24, 2023
  ea148f3

Commits on Jun 23, 2023

• type check tests (and convert next-test-utils.js to ts) (#51071)

  ForsakenHarmony

  committedJun 23, 2023
  5d54eaa

Commits on Jun 21, 2023

• refactor tests for readability (#51051)

  ForsakenHarmony

  committedJun 21, 2023
  c1c3675

Commits on Mar 13, 2023

• Integrate next-* crates from Turbopack (#47019)

  

  jridgewell

  authored and

  sokra

  committedMar 13, 2023
  8ae2df0

Commits on Jun 30, 2022

• Adds tests to ensure eslint-plugin-next's available rules are properly exported and recommended rules are correctly defined. (#38183)

  

  manovotny

  and

  ijjk

  committedJun 30, 2022
  edd395a

Commits on May 29, 2022

• Ignore popstate with invalid state (#37110)

  

  Hannes Bornö

  and

  ijjk

  committedMay 29, 2022
  5739edc

Commits on Sep 13, 2021

• Update test set-up to leverage playwright when able to (#28634)

  

  ijjk

  and

  kodiakhq[bot]

  committedSep 13, 2021
  a92a5ca

Commits on Aug 24, 2021

• Move unit tests to one folder and migrate them to TypeScript (#28427)

  ijjk

  committedAug 24, 2021
  005b13f

Loading