We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I was researching turborepo and found this great example repo :-)
While looking through it I found that tsconfig.base.json had paths specified like this:
tsconfig.base.json
paths
"baseUrl": ".", "paths": { "@my-monorepo/*": ["./packages/*"] }
However this seems redundant since the repo is also using yarn workspaces in the root package.json like this:
yarn workspaces
package.json
"workspaces": [ "packages/*" ],
This will create symlinks in node_modules/@my-monorepo/XXX so module resolution would work without using paths in tsconfig.base.json.
node_modules/@my-monorepo/XXX
So my question is why both tsconfig paths and yarn worspaces are used?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I was researching turborepo and found this great example repo :-)
While looking through it I found that
tsconfig.base.json
hadpaths
specified like this:However this seems redundant since the repo is also using
yarn workspaces
in the rootpackage.json
like this:This will create symlinks in
node_modules/@my-monorepo/XXX
so module resolution would work without usingpaths
intsconfig.base.json
.So my question is why both tsconfig paths and yarn worspaces are used?
The text was updated successfully, but these errors were encountered: