✅ Import buffer via aliased name #4381
Merged
+6
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Category:
Potential impacts: