Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jun 19, 2025

This PR contains the following updates:

Package Change Age Confidence
styled-jsx 4.0.1 -> 5.1.7 age confidence

Release Notes

vercel/styled-jsx (styled-jsx)

v5.1.7

Compare Source

Bug Fixes
  • Check if adding to registry in useInsertionEffect fails and fall back to useLayoutEffect (#​857) (d7a5937)

v5.1.6

Compare Source

Bug Fixes

v5.1.5

Compare Source

Bug Fixes

v5.1.4

Compare Source

Bug Fixes

v5.1.3

Compare Source

Bug Fixes

v5.1.2

Compare Source

Bug Fixes

v5.1.1

Compare Source

Bug Fixes

v5.1.0

Compare Source

Features

v5.0.7

Compare Source

Bug Fixes

v5.0.6

Compare Source

Bug Fixes

v5.0.5

Compare Source

Improvements
Misc

v5.0.4

Compare Source

Bug Fixes

v5.0.3

Compare Source

Patches
  • declare module and fix conflict typing name #​805
  • improvement: add typing for style imports #​804
Documentation
  • docs: update typescript guide with babel plugin #​801
  • chore: remove git.io #​794

v5.0.2

Compare Source

Performance Improvements

v5.0.1

Compare Source

Bug Fixes

v5.0.0

Compare Source

Features
  • Introduce contextual styles (#​744)
  • Opt-in react 18 insertion effect hook when available (#​753)
  • Fallback to module level registry in browser (#​768)
Improvements
  • Make JSXStyle return a noop if the registry context is not provided (#​749)
  • Fix typings of nonce property
  • Pre-compile dependencies to reduce install size/time (#​770)
BREAKING CHANGES
APIs
  • styled-jsx/server import path is deprecated
  • flush and flushToHTML from styled-jsx/server APIs are deprecated
  • New component <StyledRegistry> is introduced
  • New APIs useStyleRegistry and createStyleRegistry are introduced
Usage

If you're only using styled-jsx purely client side, nothing will effect you.
If you're using styled-jsx inside Next.js without customization, Next.js will automatically handle the changes for you.

If you have your own customization with styled-jsx in Next.js, for example you have a custom _document:
By default, doing this will let Next.js collect styles and pass them down.

class Document extends React.Component {
  static async getInitialProps(ctx) {
    return await ctx.defaultGetInitialProps(ctx)
  }
}

Or for instance you're passing nonce property in getInitialProps of _document, this will let you configure it:

class Document extends React.Component {
  static async getInitialProps(ctx) {
-    return await ctx.defaultGetInitialProps(ctx)
+    return await ctx.defaultGetInitialProps(ctx, { nonce })
  }
}

If you're building the SSR solution yourself with other frameworks, please checkout the Server-Side Rendering section in readme.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@vercel
Copy link

vercel bot commented Jun 19, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
neontribe-www ❌ Failed (Inspect) Jun 30, 2025 4:22pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant