Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: vercel/next.js
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v15.2.2
Choose a base ref
...
head repository: vercel/next.js
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v15.2.3
Choose a head ref
  • 9 commits
  • 57 files changed
  • 4 contributors

Commits on Mar 17, 2025

  1. [metadata] re-insert icons to head for streamed metadata (#76915) 

    ### What

Re-insert the metadata icons under body tag into head tag to ensure they
can be proper displayed.

### Why

* For chromium based browsers (Chrome, Edge, etc.) and Safari, icons
need to stay under `<head>` to be picked up by the browser. Firefox
doesn't have this requirement.
* Firefox will always render svg > icon > png, so it doesn't matter to
it.


Made a test in https://icons-order-test.vercel.app/, you can play with
the test cases here. These links can see the comparsion of the approach
in the this PR.

During deployment it's very hard to verify Safari as it's pretty broken.
But deploymet works well.
After we re-insert the icon from body into head, they can be properly
displayed across all the browsers.

Note: We insert the script during streaming rather than using a jsx
element right after metadata to avoid the hydration errors

Closes #76810
Closes NDX-951
    @huozhi
    huozhi committed Mar 17, 2025
    Configuration menu
    Copy the full SHA
    88deb12 View commit details
    Browse the repository at this point in the history

  2. [ts-hint] fix vscode type hint plugin enabling (#77099) 

    ### What

Fix the enabling of ts hint plugin in vscode. This is a regression
introduced in #76300, where we use the plugin config `{ "name": "next"
}` to directly check if it has a `enabled` property, and determine if we
should enable the plugin. This PR fixed the way of reading plugin config
and keep it enabled by default.

Fixes 76980
    @huozhi
    huozhi committed Mar 17, 2025
    Configuration menu
    Copy the full SHA
    1e1ff40 View commit details
    Browse the repository at this point in the history

  3. [metadata] remove the default segement check for metadata rendering (#… 

    …77119)

### What

Remove the default segment checks for metadata rendering. When the
`default.js` is rendered, it should still have the metadata. It was a
condition added due to possible of duplicated metadata, but it's
resolved by other conditions such as only rendering in child slot, and
hoisting metadata into rsc head for navigation.
    @huozhi
    huozhi committed Mar 17, 2025
    Configuration menu
    Copy the full SHA
    4698ad6 View commit details
    Browse the repository at this point in the history

  4. Update middleware request header (#77201) 

    This just adds an additional header to our internal filtering list for
middleware.
    @ijjk @huozhi
    ijjk authored and huozhi committed Mar 17, 2025
    Configuration menu
    Copy the full SHA
    52a078d View commit details
    Browse the repository at this point in the history

  5. Ensure deploymentId is used for CSS preloads (#77210) 

    This just ensures we use the deployment ID if configured for preload CSS
links.

x-ref: [slack
thread](https://vercel.slack.com/archives/C03S8ED1DKM/p1742146672858189)
    @ijjk @huozhi
    ijjk authored and huozhi committed Mar 17, 2025
    Configuration menu
    Copy the full SHA
    8151cb6 View commit details
    Browse the repository at this point in the history

  6. Add dev warning for cross-origin and stabilize allowedDevOrigins (#77044 

    )

Adding a warning when we block cross-origin requests in dev so users are
aware this is why easier and know how to allow the origin through as
custom setups can use different origins and it be valid.

x-ref:
#76880 (comment)

---------

Co-authored-by: Jiachi Liu <inbox@huozhi.im>
Co-authored-by: Zack Tanner <1939140+ztanner@users.noreply.github.com>
    @ijjk @huozhi @ztanner
    3 people committed Mar 17, 2025
    Configuration menu
    Copy the full SHA
    5e59da1 View commit details
    Browse the repository at this point in the history

  7. unify allowed origin detection handling (#77053) 

    This unifies the CSRF origin detection to mirror what we do for server
action origins, which supports things like wildcard matches (below the
domain level)

Fixes #76999
    @ztanner @huozhi
    ztanner authored and huozhi committed Mar 17, 2025
    Configuration menu
    Copy the full SHA
    adf5462 View commit details
    Browse the repository at this point in the history

  8. Update default allowed origins list (#77212) 

    Per feedback in #76880 this
ensures we ocnsider `*.localhost` as allowed by default for the dev
origins list.
    @ijjk @huozhi
    ijjk authored and huozhi committed Mar 17, 2025
    1 Configuration menu
    Copy the full SHA
    2fcae1d View commit details
    Browse the repository at this point in the history

  9. v15.2.3

    @vercel-release-bot
    vercel-release-bot committed Mar 17, 2025
    Configuration menu
    Copy the full SHA
    535e26d View commit details
    Browse the repository at this point in the history
Loading