feat: add external package importer-exporter #1214
Draft
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
3 tasks
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.
This PR adds a package called
@smithy/external, which re-exports external dependencies.Why:
package.json->"exports"introduced in Node.js 12, this package provides Node.js runtimes a bundled re-export ofuuidand potentially other external dependencies in the future. This reduces the file count, since otherwise direct import ofuuidadds a dozen or so files.uuidpackage, avoiding redundant bundling in web.This doesn't actually require Node.js 16 as the minimum, but TypeScript won't understand the sub-export otherwise.