1. 01 Nov, 2023 5 commits
  2. 31 Oct, 2023 24 commits
  3. 30 Oct, 2023 11 commits
    • vercel-release-bot's avatar
      v14.0.2-canary.0 · 5eb66072
      vercel-release-bot authored
      5eb66072
    • OJ Kwon's avatar
      fix(metadata): align metadata suffix hash between turbopack (#57544) · cce9f0d3
      OJ Kwon authored
      ### What?
      
      Wraps up metadata-dynamic-routes tests fixes for the turbopack. There is 1 remaining failing test due to lacks of supporting `import.meta.url` which need to be addressed separately.
      
      I spent amount of time why turbopack cannot find the route for the dynamic metadata for a certain route. In the end, found there are mismatching expectations for the route due to different hash for the certain route. We do use the same djb2 hash between next.js and turbopack both, so it was quite confusing why we don't get deterministic hash.
      
      After trying some experiments, found out root cause was how 2 different runtimes handle overflow for given type of numbers. In rust + turbpack we use u32 and do 32-bit hash calculation for given string, while in js we implicitly used number type as is, in result overflow occurs with default 53-bit float. 
      
      Originally I tried to adjust hash in turbopack side to preserve js hash as-is, but so far I found it was non trivial to do so as rust there's no out of the box types we can coerce to the js number type. In result, unlike other fixes in turbopack this PR changes how js hash is being generated. I hope this woulndn't be a breaking changes; expect so since this is a metadata specific hash that we do not have written spec for it.
      
      Closes WEB-1890
      cce9f0d3
    • vercel-release-bot's avatar
      v14.0.1 · 4df888a5
      vercel-release-bot authored
      4df888a5
    • vercel-release-bot's avatar
      v14.0.1-canary.5 · 41dec2cb
      vercel-release-bot authored
      41dec2cb
    • Josh Story's avatar
    • JJ Kasper's avatar
      Remove extra CI step and lock Node.js version (#57769) · 676d1ee4
      JJ Kasper authored
      Seems this command is causing intermittent issues and we don't actually need this information so removes it
      676d1ee4
    • moka-ayumu's avatar
      Modify tailwindcss related dependency of `create-next-app` (#57262) · 0623a4f7
      moka-ayumu authored
      ### What?
      If the version of `autoprefixer` is 10.0.0 and the version of `tailwindcss` is less than 3.3.0, the error `RangeError: Maximum call stack size exceeded` occurs when you create with tailwindcss & typescript and run it.
      
      ### Why?
      The exact reason is unknown, but it appears to be a compatibility issue. Also, currently configuring tailwindcss with ts makes the tailwind config file in ts, which is supported since tailwindcss version 3.3.0. (In js, it works even if you set the version of `autoprefixer` to 10.0.1 and lower the version of tailwindcss.)
      
      ### How?
      Simply default the minimum version of `autoprefixer` to 10.0.1 and the minimum version of `tailwindcss` to 3.3.0.
      
      0623a4f7
    • Leah's avatar
      fix(turbopack): don't match empty route groups (#57647) · 6dc7c3c4
      Leah authored
      ### What?
      
      Previously the matching just used the last match for children which could lead to empty groups or groups without page matches overriding the actual page.
      
      This PR makes sure this doesn't happen and emits an issue (which unfortunately doesn't get displayed yet) in case there are 2 `page` matches which would go into the children slot.
      
      Closes WEB-1895
      6dc7c3c4
    • vercel-release-bot's avatar
      v14.0.1-canary.4 · 9d49afc5
      vercel-release-bot authored
      9d49afc5
    • Zack Tanner's avatar
      fix gsp tracing issue (#57766) · 9128b586
      Zack Tanner authored
      This removes the ignores for dev react bundles which was added as an
      optimization but causes issues when react is imported from an ESM module
      since all requires are being analyzed for named exports.
      
      Fixes #57582
      9128b586
    • Jiachi Liu's avatar
      Improve error for missing default export in dynamic metadata routes (#57711) · 3553c651
      Jiachi Liu authored
      Displaying hints of "missing default export" if you didn't properly export the `default` handler for og image 
      
      ```
         ▲ Next.js 14.0.1-canary.2
         - Local:        http://localhost:3000
      
       ✓ Ready in 1089ms
       ✓ Compiled /opengraph-image/[[...__metadata_id__]]/route in 211ms (44 modules)
       ⨯ Error: Default export is missing in "/Users/huozhi/workspace/next.js/test/e2e/app-dir/metadata-dynam
      ic-routes/app/opengraph-image.tsx"
          at eval (webpack:///app/opengraph-image.tsx?3407:11:1)
          at (app-metadata-route)/../../../../packages/next/dist/build/webpack/loaders/next-metadata-route-lo
      ader.js?page=%2Fopengraph-image%2F%5B%5B...__metadata_id__%5D%5D%2Froute&isDynamic=1!./app/opengraph-im
      age.tsx?__next_metadata_route__ (/Users/huozhi/workspace/next.js/test/e2e/app-dir/metadata-dynamic-rout
      es/.next/server/app/opengraph-image/[[...__metadata_id__]]/route.js:362:1)
          at __webpack_require__ (/Users/huozhi/workspace/next.js/test/e2e/app-dir/metadata-dynamic-routes/.n
      ext/server/webpack-runtime.js:33:42)
      ```
      3553c651