-
Notifications
You must be signed in to change notification settings - Fork 470
fix(pretty-dom): Ensure safe process.env access #431
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
refs testing-library#413 refs testing-library#161 Not all environments (particularly the browser, where testing via tools like Karma occurs) have access to the `process` variable. There is already checking to ensure that its member properties have fallbacks, and this ensures that if it is simply unavailable the same fallback occurs.
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 87df57a:
|
Codecov Report
@@ Coverage Diff @@
## master #431 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 22 22
Lines 374 374
Branches 87 87
=====================================
Hits 374 374
Continue to review full report at Codecov.
|
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 for the report and fix.
Looks good. Never touched this file so someone else should approve as well.
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.
Super duper. Thank you very much!
@all-contributors please add @Westbrook for code |
I've put up a pull request to add @Westbrook! 🎉 |
🎉 This PR is included in version 6.11.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
refs #413
refs #161
What:
Not all environments (particularly the browser, where testing via tools like Karma occurs) have access to the
process
variable. There is already checking to ensure that its member properties have fallbacks, and this ensures that if it is simply unavailable the same fallback occurs.Why:
I'd like to begin the work of supporting Karma and web components.
How:
Extra test for
process
.Checklist:
docs site
DefinitelyTyped