build: remove next dependency for the Jest configuration
#2542
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Robbert
force-pushed
the
build/no-next-jest
branch
from
2af3dd3 to
a758849
Compare
Robbert
force-pushed
the
build/no-next-jest
branch
from
a758849 to
b8c9243
Compare
Robbert
force-pushed
the
build/no-next-jest
branch
from
b8c9243 to
d86a9f2
Compare
Robbert
force-pushed
the
build/no-next-jest
branch
from
d86a9f2 to
d5e4dfc
Compare
|
Yolijn
approved these changes
Feb 9, 2025
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.
Basically I started with the setup I got working in https://github.com/nl-design-system/themes/tree/main/packages/theme-toolkit and merged it with the existing configuration without
next.nextis still used for the Breadcrumb test though, so the dependency can't be removed from package.json yet.