Add subpath exports #214
Merged
Add subpath exports #214
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
Subpath exports have been added for the three "main" modules in this package. These allow consumers to easily omit the parts of the package they aren't using, without risking accidentally relying upon internal APIs. The three main "feature" modules have been exposed as subpath exports. The "util" module is the only one not exported, and that's because its API includes methods that we don't want to include in the public API of the package. We can separate the internal and external "util" methods later on if there is any demand for this.
Gudahtt
force-pushed
the
add-subpath-exports
branch
from
cc19b62
to
031c59b
Compare
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.
Subpath exports have been added for the three "main" modules in this package. These allow consumers to easily omit the parts of the package they aren't using, without risking accidentally relying upon internal APIs.
The three main "feature" modules have been exposed as subpath exports. The "util" module is the only one not exported, and that's because its API includes methods that we don't want to include in the public API of the package. We can separate the internal and external "util" methods later on if there is any demand for this.