Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[edge-functions/jwt-authentication] Fix for breaking changes in Next.…
…js canary (#443) Some following breaking changes were introduced in Next.js canary. This PR includes fixes for them. - vercel/next.js#41767 - vercel/next.js#41526 In addition to that, it also adds a runtime check to throw user-friendly error if `$JWT_SECRET_KEY` is missing. ### Description <!-- ✍️ Write a short summary of your work. Screenshots and videos are welcome! --> ### Demo URL <!-- Provide a URL to a live deployment where we can test your PR. If a demo isn't possible feel free to omit this section. --> ### Type of Change - [ ] New Example - [x] Example updates (Bug fixes, new features, etc.) - [ ] Other (changes to the codebase, but not to examples) ### New Example Checklist - [ ] 🛫 `npm run new-example` was used to create the example - [ ] 📚 The template wasn't used but I carefuly read the [Adding a new example](https://github.com/vercel/examples#adding-a-new-example) steps and implemented them in the example - [ ] 📱 Is it responsive? Are mobile and tablets considered?
- Loading branch information
486f834
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Successfully deployed to the following URLs:
edge-functions-jwt-authentication – ./edge-functions/jwt-authentication
edge-functions-jwt-authentication.vercel.app
edge-jwt.vercel.app
edge-functions-jwt-authentication-git-main.vercel.sh
edge-functions-jwt-authentication.vercel.sh
edge-jwt.vercel.sh
486f834
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Successfully deployed to the following URLs:
solutions-monorepo – ./solutions/monorepo/apps/app
solutions-monorepo.vercel.app
solutions-monorepo-git-main.vercel.sh
solutions-monorepo.vercel.sh