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
👷 Attempt to switch to pnp linker #4368
Conversation
Target being a faster CI!
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 ce97804:
|
Up-to-now we have been importing buffer while it's a known native package in node. So in order to avoid node from pulling its own, we were relying on path import. We switched to a way safer approach: we alias the buffer package with another name and we import it via its other name. It avoid path related hazards and let the package manager and node responsible to tell the code where to find the relevant package. Satellite PR for #4368
Up-to-now when changing the test runner used internally by Jest, we were passing it the full path to the runner and its entry point. This approach proved fragile when we attempted to switch to Yarn in PnP mode. This PR change the way we declare the runner: we stop passing the path to the entry point and just pass its name. Satellite PR for #4368
Codecov Report
@@ Coverage Diff @@
## main #4368 +/- ##
=======================================
Coverage 93.57% 93.57%
=======================================
Files 207 207
Lines 5013 5013
Branches 1368 1368
=======================================
Hits 4691 4691
Misses 322 322
Flags with carried forward coverage won't be shown. Click here to find out more. |
Up-to-now when changing the test runner used internally by Jest, we were passing it the full path to the runner and its entry point. This approach proved fragile when we attempted to switch to Yarn in PnP mode. This PR change the way we declare the runner: we stop passing the path to the entry point and just pass its name. Satellite PR for #4368
Up-to-now we have been importing buffer while it's a known native package in node. So in order to avoid node from pulling its own, we were relying on path import. We switched to a way safer approach: we alias the buffer package with another name and we import it via its other name. It avoid path related hazards and let the package manager and node responsible to tell the code where to find the relevant package. Satellite PR for #4368
Target being a faster CI!
Category:
Potential impacts: