feat: simplify monorepo with package.json publishConfig overrides
#101
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
manzt
changed the title
publishConfig overrides
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.
Right now you need to run TypeScript in watch mode with vitest to see changes updated across packages. This PR uses the
publishConfigin the package.json to link TypeScript (and vitest) to the TypeScript subpackage source within the monorepo. This means that we don't need to recompile TypeScript for vitest to work, and instead vitest will be tracking changes across all files in the repo. However, when we publish to NPM we update the package.json package exports to point to the build typescript code.