-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
ci: Split node & browser unit tests #6535
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
0c8046b
to
9ee6705
Compare
size-limit report 📦
|
package.json
Outdated
"test-ci-browser": "TESTS_SKIP=node ts-node ./scripts/test.ts", | ||
"test-ci-node": "TESTS_SKIP=browser ts-node ./scripts/test.ts", |
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.
Can't remember: Does this work on windows?
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.
good point, I guess we can use cross-env
!
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.
noice
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.
Generally, I think it's good to split up this huge unit test job. I'm just wondering if there's a downside to not testing browser packages with different node versions... Maybe we'd miss some bugs appearing in SSR scenarios? But I guess overall that's an edge case and we're testing NextJS and Remix anyway in the node jobs. So I'd say let's do it 👍
bbe3f1e
to
076b133
Compare
This PR does two main things: