-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
fix(profiling): Don't put require, __filename and __dirname on global object
#14470
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
fc0e866 to
531e99b
Compare
531e99b to
7b07ab9
Compare
f2ef50c to
5f6dba9
Compare
5f6dba9 to
98e4eec
Compare
a45f224 to
32633bf
Compare
32633bf to
de1a11f
Compare
1eefeac to
5aa22a2
Compare
require, __filename and __dirname on global object
5f9438b to
4d46401
Compare
4d46401 to
31653f3
Compare
❌ 1 Tests Failed:
View the full list of 1 ❄️ flaky tests
To view more test analytics, go to the Test Analytics Dashboard |
|
I am gonna skip the test for now. I am not even sure what exactly we are testing here. |
|
@lforst I think it's fine to skip the test. The intention was to run a mjs script that uses profiling and check that globalThis.require was not available. |
mydea
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.
I guess if tests pass, should be all good! Changes generally seem OK to me but I am not an expert on this matter ^^
Fixes our CJS detection by no longer storing a reference to require on globalThis.
Ref #14525, #13662