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(backend): Support the Vercel edge-light runtime key #841

Merged
merged 1 commit into from
Feb 20, 2023

Conversation

nikosdouvlis
Copy link
Member

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Packages affected

  • @clerk/clerk-js
  • @clerk/clerk-react
  • @clerk/nextjs
  • @clerk/remix
  • @clerk/types
  • @clerk/themes
  • @clerk/localizations
  • @clerk/clerk-expo
  • @clerk/backend
  • @clerk/clerk-sdk-node
  • @clerk/shared
  • @clerk/fastify
  • gatsby-plugin-clerk
  • build/tooling/chore

Description

  • npm test runs as expected.
  • npm run build runs as expected.

The edge-light runtime key was recently added as a condition name for the edge runtime in this PR: vercel/next.js#45188

However, this PR also introduced a change (which might not be intentional): the node runtime key is now a valid condition key for the edge runtime, so it matches before our default import.

This PR adds the edge-light key before node so that we guarantee that the correct imports will always be used.

The edge-light runtime key was recently added as a condition name for the edge runtime in this PR: vercel/next.js#45188

However, this PR also introduced a change (which might not be intentional): the `node` runtime key is now a valid condition key for the edge runtime, so it matches before our `default` import.

This PR adds the `edge-light` key before `node` so that we guarantee that the correct imports will always be used.
Copy link

@jit-ci jit-ci bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Great news! Jit hasn't found any security issues in your PR. Good Job! 🏆

@nikosdouvlis nikosdouvlis merged commit 48e937d into main Feb 20, 2023
@nikosdouvlis nikosdouvlis deleted the nikos/js-203-fix-middleware-again-for-nextjs branch February 20, 2023 22:45
@clerk clerk deleted a comment from linear bot Feb 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant