Right now you need to run TypeScript in watch mode with vitest to see changes updated across packages. This PR uses the publishConfig in 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.
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.