- 10 Jan, 2025 29 commits
-
-
vercel-release-bot authored
-
Jiachi Liu authored
### What Introduce an experimental config `experimental.htmlLimitedBots` (type `Regex`) which can used for controlling the metadata streaming behavior for different bots, if the bots user agent is matching the regex, it will serve blocking metadata forcedly. This gives users some control to opt-out streaming metadata for some clients or bots which cannot handle it. Output another manifest `response-config-manfiest.json` containing the customized UA, which is potentially used for the platform serving Next.js to control the returned response for certain UA. But it's mostly for PPR case which we'll tackle later. Closes NDX-635 Closes NDX-599
-
Sam Ko authored
## Why? We currently have no automated process for handling stale issues. This PR adds an automated process for this.
-
Andrew Clark authored
Fixes a bug in the handling of stale times in the client Segment Cache, when prefetching a PPR-enabled route. The stale time sent by the server is in seconds, but I was handling it as if it were in milliseconds. This caused the entry to expire almost immediately. I didn't notice this sooner because the main test apps I've been working with don't have PPR enabled, and the non-PPR path was converting the values correctly. The existing e2e tests also didn't catch it because they run fast enough that the entries don't expire.
-
Jiwon Choi authored
This PR added a `.cursorignore` file to ignore **27,500 files** for Cursor to index. ```.gitignore # The reverse pattern did not work. * !packages/** ``` ### Before  ### After 
-
mikeboensel authored
-
Jiachi Liu authored
-
Sebastian "Sebbie" Silbermann authored
-
Hendrik Liebau authored
When using a Node.js module that is [supported in the Edge runtime](https://vercel.com/docs/functions/runtimes/edge-runtime#compatible-node.js-modules), we must not emit a warning during build.
-
Jiwon Choi authored
This PR added style for Runtime Error Code Frame. The file icon will follow up and will be replaced with correct icons (e.g. js, ts, etc.) > [!NOTE] > Does not fully align with Figma due to restrictions on how `@babel/code-frame` handles colors and spacing. ### Light  ### Dark  Closes NDX-650 --------- Co-authored-by:
Jiachi Liu <inbox@huozhi.im>
-
Jiwon Choi authored
This PR added style for Call Stack and applied the following: - Changed call stack rendering logic - Display the stack of the first frame - Removed unused CSS - Ported component CSS from the `RuntimeError` component to respecting components. ### Light https://github.com/user-attachments/assets/2f93e01f-1c3f-49c7-b5a5-b5434370be85 ### Dark https://github.com/user-attachments/assets/2db6cb1f-4701-416d-95c8-c14c128035ae Closes NDX-610 --------- Co-authored-by:
Jiachi Liu <inbox@huozhi.im>
-
Jiwon Choi authored
This PR added Turbopack styling. ### Light  ### Dark  Closes NDX-636 --------- Co-authored-by:
Jiachi Liu <inbox@huozhi.im>
-
Jiwon Choi authored
This PR decoupled the `Dialog` component with the "Error" overlay. Removed unused styles in the progress.
-
Jiwon Choi authored
This PR fixed the followings: - `versionInfo` was omitted in the `Errors` component. - The border radius of the Error type label chip is 6px in design but was 8px in dev. - Removed unnecessary margins and paddings that took unexpected space. ### Light  ### Dark 
-
Tobias Koppers authored
### What? Improves memory usage by changing the way data is stored in the new backend. Instead of keeping a map `enum CachedDataItemKey` -> `enum CachedDataItemValue`, it uses a Vec `enum CachedDataItemStorage` which keeps a single storage for every `enum CachedDataItemType`. The storage is strongly types and e. g. stores a map `TaskId` -> `()`, which makes it more memory efficient while still not wasting memory for unused types. It also calls `shrink_to_fit` after task completion and `shrink_amortized` after removing items, to reduce the unnecessary capacity.
-
Sebastian "Sebbie" Silbermann authored
-
Donny/강동윤 authored
### What? Update swc crates to https://github.com/swc-project/swc/releases/tag/swc_core%40v10.1.0 ### Why? To apply https://github.com/vercel/next.js/pull/73696 and parallelization improvements. ### How?
-
Jiwon Choi authored
This PR added style for the version staleness indicator. The "Turbopack-ness" will be added in the follow up PR. ### Light  ### Dark  Closes NDX-575
-
Mat Mannion authored
### What? A minor fix to the `package.json` for `@vercel/og`; there is a typo on the SPDX license ID for MPL-2.0 which is causing the license ID to not be correctly extracted by some automated tooling (one example is https://github.com/CycloneDX/cyclonedx-webpack-plugin, meaning that the license ID isn't correctly identified). ### Why? For apps that use automated tooling to generate an exhaustive list of dependencies, it's useful to have the license identified automatically and for this to be a valid SPDX identifier to be able to group dependencies together. Co-authored-by:
Jiachi Liu <inbox@huozhi.im>
-
Jiwon Choi authored
This PR added style for pagination and has no logic difference. Changed the filename from `ErrorPagination` to `error-overlay-pagination` for consistency. ### Light  ### Dark  Closes NDX-576
-
Jiwon Choi authored
This PR moved existing pagination and version info to a floating header above the overlay. Moved the Bottom Stacks inside the dialog component and modified position as well.  Closes NDX-634
-
Hendrik Liebau authored
This reduces the high CPU usage that was caused by TUI during idle time significantly when running `pnpm dev` in the Next.js repo. ### Running `pnpm dev -F next` in 4 git worktrees concurrently (as you do) #### Before <img width="852" alt="before" src="https://github.com/user-attachments/assets/17c811c8-38dd-4373-abfb-8a41415df372" /> #### After <img width="852" alt="after" src="https://github.com/user-attachments/assets/58913f78-8fc4-4b7c-a052-ff27e8c1cc06" />
-
Niklas Mischkulnig authored
-
Sebastian "Sebbie" Silbermann authored
Will be stacked on next React sync which includes `unstable_ViewTransition`. Allows using React's `unstable_ViewTransition` Component behind the `experimental.viewTransition` flag. Right now it just opts into React's experimental build but may later house Next.js specific features like Transition Types for navigations.
-
Jiwon Choi authored
This PR added stories for Error containers: `Errors`, `BuildError`, `RootLayoutMissingTagsError`. Note: Filenames are Pascal for now to benefit the vscode file nesting. Will change all to kebab in once.
-
Jude Gao authored
# Add Issue Count Indicator to Next.js Dev Tools Logo ### What? Adds a visual indicator showing the number of issues in the Next.js dev tools logo. The logo now displays a red circle with the issue count when there are active issues, and changes color to indicate error states.  ### Why? Improves developer experience by providing immediate visual feedback about the presence and number of issues without requiring interaction with the dev tools panel. ### How? - Created a new `NextLogo` component with issue count display - Added Storybook stories to showcase different states (no issues, single issue, multiple issues) - Implemented dynamic styling based on issue count - Added a red circular badge that appears when issues are present - Updated the logo colors to reflect error states
-
Arindam Majumder authored
### What? Added a new option for `create-next-app` to create a headless API app. This includes: - Adding a `--api` flag for `create-next-app` to create a headless app. - Modifying the template to include only the required assets (no `public/`, `app/page.*`, etc.). - Ensuring the app includes only the required dependencies (no `@types/react`, `react`, etc.). ### Why? This feature allows users to initialize projects with headless API templates, making it easier to set up projects that require backend functionality without frontend components. ### How? - Added the `--api` flag to the `create-next-app` command. - Modified the template to exclude unnecessary assets and dependencies. - Included exemplary usage of `route.js` features with comments for user guidance. - Implemented HTTP Methods and Parameters for request validation. Closes #68118 Closes NEXT-3633 Closes NDX-120 --------- Signed-off-by:
Arindam Majumder <arindammajumder2020@gmail.com> Co-authored-by:
Mert Can Altin <mertgold60@gmail.com> Co-authored-by:
Jiwon Choi <devjiwonchoi@gmail.com> Co-authored-by:
Tim_Z <z22zhong@uwaterloo.ca> Co-authored-by:
Tim_Z <43297139+Tim-Zj@users.noreply.github.com> Co-authored-by:
Ahmed Abdelbaset <A7med3bdulBaset@gmail.com> Co-authored-by:
Lee Robinson <me@leerob.io> Co-authored-by:
Ephraim Atta-Duncan <ephraimduncan68@gmail.com> Co-authored-by:
Zack Tanner <1939140+ztanner@users.noreply.github.com>
-
Jude Gao authored
### What? Removes unused props and simplifies the error boundary implementation in the React Dev Overlay component. ### Why? The overlay had unnecessary complexity with unused props like `preventDisplay` and `globalOverlay` that weren't providing value. Simplifying the implementation makes the code more maintainable and easier to understand. ### How? - Removed `preventDisplay` and `globalOverlay` props from ReactDevOverlay - Simplified ErrorBoundary component by removing global overlay handling - Updated type definitions for ErrorDebug component - Cleaned up error display logic in hooks - Updated tests to reflect new component structure
-
Sam Ko authored
## Why? We have regenerated the token with necessary permission as `STALE_TOKEN`.
-
- 09 Jan, 2025 11 commits
-
-
Jiachi Liu authored
* revert https://github.com/vercel/next.js/pull/74686 as it should already being skipped * add flaky test to turbopack dev manifest There's an issue that the skipped tests in manifest are still get executed. This PR only adds them into the manifest. The CI issue will be addressed separately
-
vercel-release-bot authored
-
Jiachi Liu authored
-
Benjamin Woodruff authored
<!-- 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 # -->
-
Sebastian Markbåge authored
This has the View Transitions fix for CSS modules.
-
Jiachi Liu authored
### What Refactor the code that responsible for global client error handling, since they could touch shared state so they shouldn't be forked in new error overlay as hooks or utils. Hence I deleted the forked ones, and move the existing used ones to the `/errors/` to avoid getting duplicated.
-
Jiachi Liu authored
-
Benjamin Woodruff authored
<!-- 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 # -->
-
Benjamin Woodruff authored
<!-- 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 # -->
-
Jude Gao authored
Adding a `DevToolsIndicator` to the bottom left corner of the screen, replacing the old `ErrorIndicator` and `StaticIndicator`. This PR brings us 80% of the way to our goal. The remaining tasks are marked with TODOs. https://github.com/user-attachments/assets/40061638-7184-4051-85ec-ec6e80ca5102
-
Vercel Release Bot authored
-