Conversation
since now we have projects with jest and vitest the jest default configuration will be removed if you want to keep it please add it to your project
|
isn't jest still used in openmfp? Should we remove it, before we migrated? |
Collaborator
Author
|
It should be added separately since now it throws error in vitest projects |
Collaborator
Author
|
on a second thought, maybe we should just use eslint directly without this shared one |
auto-merge was automatically disabled
January 20, 2026 06:21
Pull request was closed
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
2 participants
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.
since now we have projects with jest and vitest
the jest default configuration will be removed
if you want to keep it please add it to your project