-
-
Notifications
You must be signed in to change notification settings - Fork 9.1k
test: more case about cjs bundle to esm lib #19787
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
CodSpeed Performance ReportMerging #19787 will degrade performances by 63.1%Comparing Summary
Benchmarks breakdown
|
@@ -0,0 +1,3 @@ | |||
console.log(exports) | |||
console.log(module) | |||
console.log(this) |
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 we avoid using console.log
, it outputs a lot of span into CI output, ideally we should remove console.log
and debugger
from all tests (except where we need it)
|
||
module.exports = { | ||
name: "overrides-exports-cjs" | ||
}; |
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.
let's add a test case:
module.exports = {
name: "adding-exports-cjs"
};
module.exports.foo = "foo";
expect(lib3.name).toBe("overrides-exports-cjs"); | ||
expect(lib3.foo).toBe(undefined); | ||
expect(lib4).toMatchObject({}); | ||
expect(lib5).toMatchObject({}); |
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.
Is it expected, because I think we should have adding-exports-cjs
and foo
What kind of change does this PR introduce?
Add more test case.
Did you add tests for your changes?
Yes, feel free to more requirement
Does this PR introduce a breaking change?
No
What needs to be documented once your changes are merged?
No