1. 07 Dec, 2023 11 commits
  2. 06 Dec, 2023 24 commits
  3. 05 Dec, 2023 5 commits
    • vercel-release-bot's avatar
      v14.0.4-canary.43 · 6387c9cb
      vercel-release-bot authored
      6387c9cb
    • Shu Ding's avatar
      Clean up builtin `modularizeImports` configs (#59294) · 1436a360
      Shu Ding authored
      Most of them can now be handled by `optimizePackageImports` as I
      manually tested them locally. The main benefit is that structural
      updates from these libs won't affect our internal configurations
      anymore, as they're automatic with the new approach. The little downside
      is that the automatic way is a bit slower than the `modularizeImports`
      config as it needs to do extra analyzation. But overall, this is a good
      direction.
      
      Depends on #59254.
      1436a360
    • Zack Tanner's avatar
      fix interception routes with dynamic segments (#59273) · 78a2eb0b
      Zack Tanner authored
      ### What?
      Using an interception marker next to a dynamic segment does not behave
      properly when deployed to Vercel
      
      ### Why?
      The named route regex that gets created is not accounting for the
      interception marker, which is causing the non-intercepted route to match
      the intercepted serverless function.
      
      ### How?
      This factors in the interception marker when building the named route
      regex so that the non-intercepted route regex properly matches when
      loading the non-intercepted page.
      
      Deployment verified here: https://test-intercept-mu.vercel.app/
      
      Closes NEXT-1786
      Fixes #54650
      78a2eb0b
    • vercel-release-bot's avatar
      v14.0.4-canary.42 · 2003f5f8
      vercel-release-bot authored
      2003f5f8
    • Shu Ding's avatar
      Fix barrel optimization to ignore layers (#59254) · 6790004d
      Shu Ding authored
      Fixes #57624. The recent issue was an unexpected side effect caused by
      https://github.com/vercel/next.js/commit/305bb015060e82be3e6ae59a3d063c11a3e207f9,
      which only affects specific packages like `@mui/material`.
      
      The problem was that the entry file of `@mui/material` has `"use
      client"` at top, which affects the compilation result to output
      reference info only (when on the RSC layer), instead of keeping the
      original export statements. And the fix here is to ignore all layer info
      and React specific transforms here, as barrel optimization isn't related
      to all these framework features at all. To keep all directives
      unchanged, the SWC transform needs to parse and pass that info to the
      Webpack loader.
      
      This PR adds a test to ensure that `@mui/material` is working as
      expected (less than 1500 modules compiled). Without this feature it'll
      be ~2400 modules.
      
      Closes NEXT-1793, closes NEXT-1762.
      6790004d