Expose ts-invariant/process entry point for optional global.process polyfill.
#139
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Though ts-invariant stopped polyfilling global.process in #94, there's a chance existing applications were accidentally depending on that API, so we can make it easy to install (and then remove!) the global.process polyfill if you still need it: import { install, remove } from "ts-invariant/process" install(); ... remove(); By default, the polyfill will be installed upon importing ts-invariant/process for the first time, so you may not need to call install() in most cases (though it doesn't hurt). Calling remove() cleans up the global namespace, removing the stub global.process object (if ts-invariant/process defined one). This allows you to import other packages that depend on process.env before removing the polyfill, without permanently polluting the global namespace.
benjamn
changed the title
ts-invariant/process entry point for optional global.process polyfill.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Though
ts-invariantstopped polyfillingglobal.processin #94, there's a chance existing applications were accidentally depending on that API, so we can make it easy to install (and then remove!) theglobal.processpolyfill if they still need it:By default, the polyfill will be installed upon importing
ts-invariant/processfor the first time, so you may not need to callinstall()in most cases (though it doesn't hurt).Calling
remove()cleans up the global namespace, removing the stubglobal.processobject (ifts-invariant/processdefined one). This allows you to import other packages that depend onprocess.envbefore removing the polyfill, without permanently polluting the global namespace.