chore: Update build to add bundled licenses of internalized modules #175
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.
Summary
As discussed, we currently internalize modules but should include a refrence to them in the bundled license text.
In general, internalizing modules is done because
gql.tada
installs the CLI (and in the future; other dependencies) automatically and should remain compact without making what it pulls in or itself too heavy.We aim to only do this for dependencies that are replaceable for custom purposes or are there as stand-ins temporary (e.g. duplicates of what
typescript
could already do, but what we haven't implemented viatypescript
yet)We can review this before reaching a
1.0.0
milestone on@gql.tada/internal
and@gql.tada/cli-utils
, at which point we're able to identify more options to not internalize modules to keep their statistics onnpm
intact.Set of changes
rollup