chore(clerk-js): Update [DEV] minor & patch dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@emotion/react (source)	11.11.1 → 11.14.0
bundlewatch	^0.4.1 → ^0.4.2
minimatch	^10.0.3 → ^10.2.5

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

emotion-js/emotion (@​emotion/react)

v11.14.0

Compare Source

Minor Changes

• #​3284 a19d019 Thanks @​Andarist! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.

Patch Changes

• Updated dependencies [e1bf17e]:
  • @​emotion/use-insertion-effect-with-fallbacks@​1.2.0

v11.13.5

Compare Source

Patch Changes

• #​3270 77d930d Thanks @​emmatown! - Fix inconsistent hashes using development vs production bundles/exports conditions when using @emotion/babel-plugin with sourceMap: true (the default). This is particularly visible when using Emotion with the Next.js Pages router where the development condition is used when bundling code but not when importing external code with Node.js.

• Updated dependencies [77d930d]:

  • @​emotion/serialize@​1.3.3
  • @​emotion/utils@​1.4.2
  • @​emotion/babel-plugin@​11.13.5

v11.13.3

Compare Source

Patch Changes

• #​3232 0ce3ed0 Thanks @​ENvironmentSet! - Distribute css prop attachment over props that are union types

• Updated dependencies []:

  • @​emotion/serialize@​1.3.1

v11.13.0

Compare Source

Minor Changes

• #​3198 d8ff8a5 Thanks @​Andarist! - Migrated away from relying on process.env.NODE_ENV checks to differentiate between production and development builds.

  Development builds (and other environment-specific builds) can be used by using proper conditions (see here). Most modern bundlers/frameworks already preconfigure those for the user so no action has to be taken.

  Default files should continue to work in all environments.

• #​3215 a9f6912 Thanks @​Andarist! - Added edge-light and workerd conditions to package.json manifest to better serve users using Vercel Edge and Cloudflare Workers.

Patch Changes

• Updated dependencies [d8ff8a5, a9f6912]:
  • @​emotion/serialize@​1.3.0
  • @​emotion/use-insertion-effect-with-fallbacks@​1.1.0
  • @​emotion/utils@​1.4.0

v11.12.0

Compare Source

Patch Changes

• #​3206 d1994c4 Thanks @​DiegoAndai! - Improved compatibility with the upcoming @types/react for React 19 where the global JSX namespace doesn't exist anymore

• #​3208 56109e7 Thanks @​Andarist! - Only forward defined refs to improve compatibility with the upcoming React 19

• Updated dependencies [9ca22c6, a1e881b, 16d8a8c]:

  • @​emotion/serialize@​1.2.0
  • @​emotion/is-prop-valid@​1.3.0
  • @​emotion/utils@​1.3.0
  • @​emotion/babel-plugin@​11.12.0

v11.11.4

Compare Source

Patch Changes

• #​3159 5b82631d Thanks @​iegik! - Renamed an internal hasOwnProperty to hasOwn. This avoids problems in CommonJS environments when the consumer tries to prevent prototype pollution with Object.freeze(Object.prototype).

v11.11.3

Compare Source

Patch Changes

• #​3101 49c20b4f Thanks @​kyvong! - Fix Theme import for newer Typescript module resolution modes

• Updated dependencies [45c440fb]:

  • @​emotion/serialize@​1.1.3

---

Configuration

📅 Schedule: (in timezone GMT)

• Branch creation
  • "before 7am on the first day of the week"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	May 6, 2026 5:58pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 947da08

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8454

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8454

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8454

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8454

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@8454

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8454

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8454

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8454

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8454

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8454

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8454

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8454

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8454

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8454

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8454

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8454

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8454

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8454

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8454

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8454

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8454

commit: 947da08

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.