Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update all non-major dependencies (patch) #183

Merged
merged 1 commit into from
Dec 13, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 11, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@clerk/nextjs (source) 4.27.5 -> 4.27.7 age adoption passing confidence
@iconify-json/material-symbols 1.1.66 -> 1.1.67 age adoption passing confidence
@iconify-json/mingcute 1.1.13 -> 1.1.14 age adoption passing confidence
@types/react (source) ^18.2.43 -> ^18.2.44 age adoption passing confidence
vite (source) 5.0.7 -> 5.0.8 age adoption passing confidence

Release Notes

clerk/javascript (@​clerk/nextjs)

v4.27.7

Compare Source

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/@&#8203;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');
      
      /** @&#8203;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.

v4.27.6

Compare Source

Patch Changes
vitejs/vite (vite)

v5.0.8

Compare Source


Configuration

📅 Schedule: Branch creation - "after 9pm,before 9am" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the renovate label Dec 11, 2023
@renovate renovate bot enabled auto-merge (rebase) December 11, 2023 22:29
Copy link

vercel bot commented Dec 11, 2023

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

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
shiro ⬜️ Ignored (Inspect) Visit Preview Dec 13, 2023 1:00am

@renovate renovate bot force-pushed the renovate/patch-all-minor-patch branch 2 times, most recently from c80de50 to 96601cc Compare December 12, 2023 15:07
@renovate renovate bot force-pushed the renovate/patch-all-minor-patch branch from 96601cc to 23647c0 Compare December 13, 2023 01:00
@Innei Innei merged commit 83175e8 into main Dec 13, 2023
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant