-
Notifications
You must be signed in to change notification settings - Fork 20
build(next): Add test setup #111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
thien-remote
left a comment
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.
Thanks @dragidavid this is excellent! Not an approval yet because I want to try simplifying the test build a bit. Will keep you updated
* Fix * Update jest.config.js * Update babel.config.js * chore: add default node version --------- Co-authored-by: David Dragovacz <[email protected]>
|
Approving as my comments are not blockers |
f3e3b79
| const config = { | ||
| roots, | ||
| moduleNameMapper, | ||
| testPathIgnorePatterns, |
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.
praise: This entire PR is very smart, TIL about this for moduleNameMapper 💡 💡 💡
To follow up on #108 and #110, this PR adds the test script to
next. It belongs to the same internal ticket of DEVXP-2530.moduleNameMapperin thejest.config.mjsfile to map the imports to the files in thenextfolder. This only happens when we run thetestscript from within thenextfolder. Otherwise everything is unaffected.nvmrcandenginesso we can make sure everyone uses the correct node version (LTS)