Fix (bug from jsx in vitest config)#293
Open
CoderOMaster wants to merge 4 commits into
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Next.js app’s Vitest configuration to avoid a JSX-related configuration issue by removing the explicit esbuild.jsx setting, relying on the project’s TypeScript/React JSX settings instead.
Changes:
- Removed
esbuild: { jsx: 'automatic' }fromapps/next-js/vitest.config.ts. - Kept the existing Vitest
jsdomenvironment, globals, and setup file configuration unchanged.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| @@ -1,12 +1,9 @@ | |||
| import { defineConfig } from 'vitest/config' | |||
|
|
|||
| export default defineConfig({ | |||
…to fix vitest TypeError
…st/PyTuple iterators (GHSA)
…ng binary integrity verification (GHSA)
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
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.
Pull Request Checklist
Please ensure that your PR meets the following requirements:
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes # (issue number)
Type of Change