1. 18 Aug, 2025 11 commits
    • nextjs-bot's avatar
      v15.4.2-canary.53 · bec38efd
      nextjs-bot authored
      bec38efd
    • Ben Gubler's avatar
      fix: make sure validator.ts uses relative paths for imports (#82761) · 8c11037e
      Ben Gubler authored
      Previously, `.next/types/validator.ts` looked like this after a build:
      
      ```typescript
      // Validate /Users/you/code/next.js/test/e2e/app-dir/typed-routes/app/dashboard/@team/page.tsx
      {
        const handler = {} as typeof import("/Users/you/code/next.js/test/e2e/app-dir/typed-routes/app/dashboard/@team/page.js")
        handler satisfies AppPageConfig<"/dashboard">
      }
      ```
      
      Now, it looks like this:
      
      ```typescript
      // Validate ../../app/dashboard/@team/page.tsx
      {
        const handler = {} as typeof import("../../app/dashboard/@team/page.js")
        handler satisfies AppPageConfig<"/dashboard">
      }
      ```
      
      This can be important for security reasons.
      8c11037e
    • Jiachi Liu's avatar
      4efa10f0
    • Steven's avatar
      chore(test): update sharp api test (#82740) · a90827be
      Steven authored
      Testing to see if sharp works with turbopack
      a90827be
    • Will Binns-Smith's avatar
      `create-next-app`: use Turbopack for both dev and build (#82753) · 480a0e1d
      Will Binns-Smith authored
      Previously, we asked users if they want to use Turbopack for `next dev`.
      Now, we ask if they want to use Turbopack, and if they do, we use it for
      both dev and build. It’s also listed as `(recommended)` like App Router.
      
      Test Plan: `pnpm build`, `./node_modules/.bin/create-next-app
      ~/path/to/app`. Choose the Turbopack option. Verify the app uses
      Turbopack for both dev and build.
      480a0e1d
    • zoomdong's avatar
      fix(turbopack): webpack-loaders failed to resolve relative path (#82720) · 4669a153
      zoomdong authored
      fixed: #82106 
      
      The error was cause by the follow reason, when pass:
      
      ```ts
      const nextConfig: NextConfig = {
        /* config options here */
        turbopack: {
          rules: {
            '*.txt': {
              loaders: ['./test-file-loader.js'],
              as: '*.js',
            },
          }
        }
      };
      ```
      
      and the project directory as follows:
      
      ```bash
      src
       |_ app
            |_ index.tsx
            |_ text.txt
      ```
      
      The loader will deal the `text.txt` under `src/app`, then the loader
      will resolve path like:
      
      ```ts
      require.resolve('./test-file-loader.js', paths: ['/Users/next-app/src/app'])
      ```
      
      Because the resource dir the `dirname(resoucePath)`, and the
      resourcePath is `/Users/next-app/src/app/text.txt`, this will never
      resolve the right loader path here.
      
      So I just add a more `path` param(which is `contextDir`) for the
      require.resolve function, it will help the loader to find the right path
      here.
      4669a153
    • Vercel Release Bot's avatar
      Update Rspack production test manifest (#82732) · b421c9ff
      Vercel Release Bot authored
      This auto-generated PR updates the production integration test manifest used when testing Rspack.
      b421c9ff
    • Niklas Mischkulnig's avatar
      Turbopack: use bail instead of panic (#82745) · a406b7a3
      Niklas Mischkulnig authored
      This behaves more gracefully due to eventual consistency
      a406b7a3
    • Luke Sandberg's avatar
      [turbopack] Remove a debug assertions in client references endpoint (#82725) · 508b1a46
      Luke Sandberg authored
      Remove a debug assertion code in the `GlobalBuildInformation` implementation that was validating client references for endpoints.  This was inserted as a sanity check that two traversals were doing the same thing, but this is overkill and can be trigged accidentally by an eventual consistency condition.  Just drop them.
      
      If an application is edited during this computation it is possible that the module graph that GlobalBuildInformation has access to is different than the set of references that `find_server_entries` will identified, this transient condition could trigger the panic.
      508b1a46
    • Tobias Koppers's avatar
      Turbopack: fix race condition in test case (#82728) · 43db9163
      Tobias Koppers authored
      ### What?
      
      Fixes a race condition in the test case.
      
      Since we are using a single value for multiple Vcs (via ReadRef::cell) the counter can have multiple invalidators.
      43db9163
    • Tobias Koppers's avatar
      Turbopack: Stop persisting background task correctly on stop (#82727) · 2bddb916
      Tobias Koppers authored
      ### What?
      
      Fixes a race condition with the persisting background tasks when stopping the backend.
      2bddb916
  2. 17 Aug, 2025 2 commits
  3. 16 Aug, 2025 6 commits
  4. 15 Aug, 2025 17 commits
  5. 14 Aug, 2025 4 commits