Bump @clerk/nextjs from 4.25.6 to 4.27.7

[dependabot]

Bumps @clerk/nextjs from 4.25.6 to 4.27.7.

Release notes

Sourced from @​clerk/nextjs's releases.

@​clerk/nextjs@​4.27.7

Patch Changes

• Use dynamic imports in <ClerkProvider /> which you import from @clerk/nextjs. (#2292) by @​LekoArts

  Users on Next.js 12 and older can run into errors like these:

  error - ./node_modules/@clerk/nextjs/dist/esm/app-router/client/ClerkProvider.js:10:22
  Module not found: Can't resolve 'next/navigation'

  The aforementioned <ClerkProvider /> component contains code for both Next.js 12 (+ older) and Next.js 13 (+ newer). On older versions it can't find the imports only available in newer versions.

  If you're seeing these errors, you have to do two things:

  1. Update @clerk/nextjs to this version

  2. Update your next.config.js to ignore these imports:

     const webpack = require('webpack');
     /** @​type {import('next').NextConfig} */
     const nextConfig = {
     reactStrictMode: true,
     webpack(config) {
     config.plugins.push(
     new webpack.IgnorePlugin({ resourceRegExp: /^next/(navigation|headers|compat/router)$/ }),
     );
     return config;
     },
     };
     module.exports = nextConfig;

     It is safe to ignore these modules as your Next.js 12 app won't hit these code paths.

@​clerk/nextjs@​4.27.6

Patch Changes

• Updated dependencies [a62479810]:
  • @​clerk/clerk-react@​4.29.0
  • @​clerk/types@​3.59.0
  • @​clerk/backend@​0.35.1
  • @​clerk/clerk-sdk-node@​4.13.1

@​clerk/nextjs@​4.27.5

Patch Changes

... (truncated)

Changelog

Sourced from @​clerk/nextjs's changelog.

4.27.7

Patch Changes

• Use dynamic imports in <ClerkProvider /> which you import from @clerk/nextjs. (#2292) by @​LekoArts

  Users on Next.js 12 and older can run into errors like these:

  error - ./node_modules/@clerk/nextjs/dist/esm/app-router/client/ClerkProvider.js:10:22
  Module not found: Can't resolve 'next/navigation'

  The aforementioned <ClerkProvider /> component contains code for both Next.js 12 (+ older) and Next.js 13 (+ newer). On older versions it can't find the imports only available in newer versions.

  If you're seeing these errors, you have to do two things:

  1. Update @clerk/nextjs to this version

  2. Update your next.config.js to ignore these imports:

     const webpack = require('webpack');
     /** @​type {import('next').NextConfig} */
     const nextConfig = {
     reactStrictMode: true,
     webpack(config) {
     config.plugins.push(
     new webpack.IgnorePlugin({ resourceRegExp: /^next/(navigation|headers|compat/router)$/ }),
     );
     return config;
     },
     };
     module.exports = nextConfig;

     It is safe to ignore these modules as your Next.js 12 app won't hit these code paths.

4.27.6

Patch Changes

• Updated dependencies [a62479810]:
  • @​clerk/clerk-react@​4.29.0
  • @​clerk/types@​3.59.0
  • @​clerk/backend@​0.35.1
  • @​clerk/clerk-sdk-node@​4.13.1

4.27.5

... (truncated)

Commits

• eb94116 chore(repo): Version packages (#2320)
• ada4bd0 fix(nextjs): Use dynamic imports in ClerkProvider (#2292)
• 7657cd3 chore(repo): Version packages (#2295)
• 11e61cc chore(repo): Version packages (#2271)
• b94f32a chore(repo): Version packages (#2262)
• 11fdbcb revert(backend): Introduce OrganizationPermissionAPI and OrganizationRoleAPI ...
• fc43f12 fix(nextjs): Skip NextResponse normalization in mergeResponses if possible (#...
• 549098c chore(repo): Version packages (#2235)
• c6950d7 chore(repo): Version packages (#2183)
• aaaf24a feat(backend): Introduce OrganizationRoleAPI (#2177) (#2187)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
emoji-twitter	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 13, 2023 9:40am

[dependabot]

Superseded by #167.