Fix cross-origin warnings and update dependencies #228
+1,374
−979
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Updated @headlessui/react from 2.2.7 to 2.2.9 - Updated @hookform/resolvers from 5.2.1 to 5.2.2 - Updated @types/node from 24.3.0 to 24.8.1 - Updated @types/react from 19.1.12 to 19.2.2 - Updated @types/react-dom from 19.1.9 to 19.2.2 - Updated eslint-config-next from 15.5.2 to 15.5.6 - Updated jest-environment-jsdom from 30.1.2 to 30.2.0 - Updated lucide-react from 0.542.0 to 0.546.0 - Updated next from 15.5.2 to 15.5.6 - Updated next-intl from 4.3.5 to 4.3.12 - Updated react from 19.1.1 to 19.2.0 - Updated react-dom from 19.1.1 to 19.2.0 - Updated react-hook-form from 7.62.0 to 7.65.0 - Updated typescript from 5.9.2 to 5.9.3 - Updated zod from 4.1.5 to 4.1.12 - Updated @eslint/compat from 1.3.2 to 1.4.0 - Updated @eslint/js from 9.34.0 to 9.38.0 - Updated @playwright/test from 1.55.0 to 1.56.1 - Updated @tailwindcss/postcss from 4.1.12 to 4.1.14 - Updated @tailwindcss/typography from 0.5.16 to 0.5.19 - Updated @testing-library/jest-dom from 6.8.0 to 6.9.1 - Updated @typescript-eslint/eslint-plugin from 8.42.0 to 8.46.1 - Updated @typescript-eslint/parser from 8.42.0 to 8.46.1 - Updated globals from 16.3.0 to 16.4.0 - Updated jest from 30.1.3 to 30.2.0 - Updated lint-staged from 16.1.6 to 16.2.4 - Updated tailwindcss from 4.1.12 to 4.1.14 - Updated glob from ^10 to ^11
Add allowedDevOrigins configuration to next.config.mjs to explicitly allow localhost and 127.0.0.1 cross-origin requests during development. This resolves the Next.js warning about cross-origin requests to /_next/* resources and ensures forward compatibility with future Next.js versions.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
💡 Enable Vercel Agent with $100 free credit for automated AI reviews |
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR addresses dev-time cross-origin warnings in Next.js and bumps package versions to recent releases.
- Add allowedDevOrigins to next.config.mjs to silence cross-origin warnings during local development
- Update Next.js, React, TypeScript, and various related dependencies/devDependencies
Reviewed Changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| package.json | Version bumps across dependencies and devDependencies, plus a glob override update |
| next.config.mjs | Introduces allowedDevOrigins to configure permitted dev origins |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
allowedDevOriginsin next.config.mjs to explicitly allow localhost and 127.0.0.1 cross-origin requests during developmentChanges
allowedDevOriginsconfiguration to suppress Next.js cross-origin warnings for/_next/*resources and ensure forward compatibility with future Next.js versions