- 17 Dec, 2024 3 commits
-
-
vercel-release-bot authored
-
Zack Tanner authored
-
Zack Tanner authored
backport: fix(turbo): sassOptions silenceDeprecations was not overwritten with user options (#74005) Backports: - https://github.com/vercel/next.js/pull/73937Co-authored-by:
Jiwon Choi <devjiwonchoi@gmail.com> Co-authored-by:
Donny/강동윤 <kdy1997.dev@gmail.com>
-
- 16 Dec, 2024 3 commits
-
-
Zack Tanner authored
Backports: - https://github.com/vercel/next.js/pull/73908
-
eps1lon authored
- 10 Dec, 2024 34 commits
-
-
vercel-release-bot authored
-
vercel-release-bot authored
-
Jiachi Liu authored
Fix type error introduced in #73540
-
Benjamin Woodruff authored
docs(turbopack): Better document the Vc type, with references to ResolvedVc and VcOperation (#72524)    
-
Andrew Clark authored
During a navigation, if all the data has been prefetched, and the target route does not contain any dynamic data, then we should skip a request to the server. This uses the `isPartial` field I added in the previous PRs to track whether the prefetched data is complete or not.
-
vercel-release-bot authored
-
Zack Tanner authored
This was fixed upstream, so we can re-enable the deployment tests for it.
-
Andrew Clark authored
Currently, when the client prefetches a segment, the server responds with a 404 if it cannot fulfill the request. This updates it to respond with a 204 No Content instead, since it's not an error for the client to request a segment whose prefetch hasn't been generated. When responding with 204, the server also sends the 'x-nextjs-postponed' header, but only if PPR is enabled for the route. The client can use the absence of this header to distinguish between a regular cache miss and a miss due to PPR being disabled. In a later PR, I will update the client to use this information to fall back to the non-PPR behavior.
-
Steven authored
We regressed in https://github.com/vercel/next.js/pull/73483 since the LRU calculates the value based on the value, not the key (and we were not setting the value).
-
vercel-release-bot authored
-
Tobias Koppers authored
### What? This adds a workaround for a Node.js bug on MacOS which causes closing file watchers to be really slow: https://github.com/nodejs/node/issues/29949 It was fixed before here: https://github.com/vercel/next.js/pull/51826 But accidentically removed here: https://github.com/vercel/next.js/commit/c5a8e0989ea13af8d04bf6dda8d741c79b964abb#diff-0ff576bd02e76f96680accff48ecbe4126a7f6bc4eafa547b6d44dee49bab770L88
-
Zack Tanner authored
Returning an empty array from `generateStaticParams` should still be deployed as an ISR route to support the `dynamicParams = true` case, where a route can be generated & cached on demand. At the moment the only way to achieve this behavior is with `export const dynamic = 'force-static'`. As a result, these routes are being treated as dynamic and never return a cached response. This PR resolves the bug by fixing several distinct things: - `prerenderedRoutes` does not need to be an array > 0 to mark a route as being a static path. This will ensure the build output shows the correct symbol and adds the path to the list of prerenders. - we initialize `prerenderedRoutes` to an empty array if we determine that the leaf-most segment (the thing rendering the current page) has a `generateStaticParams` function - the function responsible for collecting segments associated with a page only considered the `children` branch, but for something like a parallel/interception route, those segments would be inside of a different parallel route key - the regex for determining if a function was dynamic didn't consider that the dynamic route might also contain an interception marker (eg `(.)`) This appears to have regressed in #68125 Closes NEXT-3905 --------- Co-authored-by:Wyatt Johnson <accounts+github@wyattjoh.ca>
-
Niklas Mischkulnig authored
Closes PACK-3537
-
Delba de Oliveira authored
**Do not merge until stable `after` lands in canary (#73605).** Closes: https://linear.app/vercel/issue/DOC-3818/[stable]-nextafter Redirect: https://github.com/vercel/front/pull/38704 --------- Co-authored-by:
Lee Robinson <me@leerob.io>
-
Tobias Koppers authored
### What? Fixes persistent caching for webpack in development Add a test case for persistent caching on Turbopack and webpack.
-
Delba de Oliveira authored
**Do not merge until 15.1 is released.** Currently these features are tagged as `canary`, but once 15.1 becomes stable, they'll be `experimental`. Closes: https://linear.app/vercel/issue/DOC-3928/update-forbidden-docs-to-add-experimental-tag
-
Delba de Oliveira authored
Going through the getting started pages with fresh eyes, picked up some nits.
-
Niklas Mischkulnig authored
Closes PACK-3535 - Adds some infrastructure for the single-graph-traversal stuff, ~~focusing on dev with layout segment optimization for now~~ - Migrate next/dynamic collection to it - This shouldn't make any observable change to the output
-
Tobias Koppers authored
### What? * avoid flagging "thread" span as incomplete * improve error message * add comments * fixup print_stats * fix lmdb feature
-
Tobias Koppers authored
### What? Fixes the lmdb feature and makes it compile fine
-
Delba de Oliveira authored
Closes: https://linear.app/vercel/issue/DOC-3929/allow-request-apis-in-after Adds example for using request APIs in `after`. Adds note about Server Component restriction. related: https://github.com/vercel/next.js/pull/73345
-
Sebastian "Sebbie" Silbermann authored
-
Tobias Koppers authored
### What? Collect trace events in a thread local buffer first and then send a batch of events to the writer thread. But there are some challenges to that: Events might be out of order in the trace file. Usually that should be fine since they have a timestamp, but * span ids might be reused faster than all events are send to the file. So we assign our own globally unique ids instead. * the trace server need to be able to process events out of order. So we queue up events when they are received for spans that are not created yet. And the thread local buffer might also have a problem when the thread is idle or hanging. This would cause events to never be written to the file. To fix that the writer thread will steal the outstanding events from the thread local buffers when it is idle for a second. This ensures that all events are eventually written, even in case of hanging threads.
-
Jam Balaya authored
## Description Follow up [the comment](https://github.com/vercel/next.js/pull/70567#issuecomment-2389725084) in #70567. > Let's go ahead and remove these Babel `style-jsx-...` examples. It's getting an error, and it's likely not worth the effort to fix/keep around as an example. In addition, [with-storybook-styled-jsx-scss](https://github.com/vercel/next.js/tree/canary/examples/with-storybook-styled-jsx-scss) example is no longer needed because the common [storybook example](https://github.com/vercel/next.js/tree/canary/examples/with-storybook) exists. ### Adding or Updating Examples - [x] The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - [x] Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.mdCo-authored-by:
Sam Ko <sam@vercel.com>
-
Jam Balaya authored
## Description The previous [nextjs-corporate-starter](https://github.com/strapi/nextjs-corporate-starter) has been archived. With the release of Strapi 5, launched an even more awesome demo/starter project called [LaunchPad](https://github.com/strapi/LaunchPad). You can learn more about the LaunchPad app from [the blog](https://strapi.io/blog/launchpad-demo-app). In addition, update [.gitignore](https://github.com/vercel/next.js/blob/canary/examples/cms-strapi/.gitignore). CC: @samcx ### Adding or Updating Examples - [x] The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - [x] Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.mdCo-authored-by:
Sam Ko <sam@vercel.com>
-
Jam Balaya authored
## Summary At #73211, `with-unstated` example was deleted. In addition, at #73243 `with-react-foundation` example was removed. So, I also remove them from [turbopack-dev-examples-manifest](https://github.com/vercel/next.js/blob/canary/test/turbopack-dev-examples-manifest.json). CC: @samcx Co-authored-by:
Sam Ko <sam@vercel.com>
-
suu3 authored
### What? Replaced the `GoogleTagManager` component with `GoogleAnalytics` in the `with-google-analytics` example. ### Why? The current implementation does not align with the [docs](https://nextjs.org/docs/app/building-your-application/optimizing/third-party-libraries#google-analytics), and a separate GTM example already exists. ### How? Replaced the `GoogleTagManager` component with `GoogleAnalytics`. Co-authored-by:
Sam Ko <sam@vercel.com>
-
Jam Balaya authored
## Description Follow up [the comment](https://github.com/vercel/next.js/pull/70663#issuecomment-2389724843) in #70663. > Let's go ahead and remove these Babel `style-jsx-...` examples. It's getting an error, and it's likely not worth the effort to fix/keep around as an example. In addition, [with-styled-components-babel](https://github.com/vercel/next.js/tree/canary/examples/with-styled-components-babel) example is no longer needed because the simple [with-styled-components example](https://github.com/vercel/next.js/tree/canary/examples/with-styled-components) exists. CC: @samcx ### Adding or Updating Examples - [x] The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - [x] Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.mdCo-authored-by:
Sam Ko <sam@vercel.com>
-
Jam Balaya authored
## Description #73344 updates the [image-legacy-component](https://github.com/vercel/next.js/tree/canary/examples/image-legacy-component) example for using the App Router. However, [`ViewSource`](https://github.com/vercel/next.js/blob/canary/examples/image-legacy-component/components/view-source.tsx) component isn't updated. Then I update the pathname. CC: @samcx ### Adding or Updating Examples - [x] The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - [x] Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.mdCo-authored-by:
Sam Ko <sam@vercel.com>
-
Jam Balaya authored
## What? Add missing related CMS examples and sort them. ## Why are [cms-keystonejs-embedded](https://github.com/vercel/next.js/tree/canary/examples/cms-keystonejs-embedded) and [cms-strapi](https://github.com/vercel/next.js/tree/canary/examples/cms-strapi) lacking? Because these have only README.md file. ## How? Update with the following text. ```md - [AgilityCMS](/examples/cms-agilitycms) - [Builder.io](/examples/cms-builder-io) - [ButterCMS](/examples/cms-buttercms) - [Contentful](/examples/cms-contentful) - [Cosmic](/examples/cms-cosmic) - [DatoCMS](/examples/cms-datocms) - [DotCMS](/examples/cms-dotcms) - [Drupal](/examples/cms-drupal) - [Enterspeed](/examples/cms-enterspeed) - [Ghost](/examples/cms-ghost) - [GraphCMS](/examples/cms-graphcms) - [Kontent.ai](/examples/cms-kontent-ai) - [MakeSwift](/examples/cms-makeswift) - [Payload](/examples/cms-payload) - [Plasmic](/examples/cms-plasmic) - [Prepr](/examples/cms-prepr) - [Prismic](/examples/cms-prismic) - [Sanity](/examples/cms-sanity) - [Sitecore XM Cloud](/examples/cms-sitecore-xmcloud) - [Sitefinity](/examples/cms-sitefinity) - [Storyblok](/examples/cms-storyblok) - [TakeShape](/examples/cms-takeshape) - [Tina](/examples/cms-tina) - [Umbraco](/examples/cms-umbraco) - [Umbraco heartcore](/examples/cms-umbraco-heartcore) - [Webiny](/examples/cms-webiny) - [WordPress](/examples/cms-wordpress) - [Blog Starter](/examples/blog-starter) ``` CC: @samcx ### Adding or Updating Examples - [x] The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - [x] Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.mdCo-authored-by:
Sam Ko <sam@vercel.com>
-
Jam Balaya authored
## Description Follow up #73255. A custom [\_app.js](https://nextjs.org/docs/advanced-features/custom-app) is **no more** used to wrap our app with the [`PlausibleProvider`](https://github.com/4lejandrito/next-plausible#plausibleprovider-props). Then delete it and convert [Header.js](https://github.com/vercel/next.js/blob/canary/examples/with-plausible/_components/Header.js) to Header.tsx alike other files. CC: @samcx ### Adding or Updating Examples - [x] The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - [x] Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.mdCo-authored-by:
Sam Ko <sam@vercel.com>
-
Jam Balaya authored
## Description Follow up #73347. Sync the app router file structure. CC: @samcx ### Adding or Updating Examples - [x] The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - [x] Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.mdCo-authored-by:
Sam Ko <sam@vercel.com>
-
Jam Balaya authored
## Description Follow up #73252. This example no more uses `<Document />` and `<head>`. So, I update it. CC: @samcx ### Adding or Updating Examples - [x] The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - [x] Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.mdCo-authored-by:
Sam Ko <sam@vercel.com>
-
PapatMayuri authored
This PR updates the with-ionic-typescript example for using the App Router. Here are the changes that have been made: - I renamed the `pages` folder and moved it to the `app` folder. - Added the `layout.tsx` file as part of the App Router. - Updated the `package.json` file. CC: @samcx --------- Co-authored-by:Sam Ko <sam@vercel.com>
-