-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
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
Support compilerOptions in workspace members #24504
Comments
Any update on this? |
Any update? This feature is essential for many projects. For me, it's the only blocker for migrating to deno. |
i currently have the same problem. this is a crutial thing for most monorepos i think. most of my packages have a little different compileroptions |
Same, this is a blocker for me. |
FYI we are aware that this is highly requested and are working on a prototype for a solution. |
this feature will be much appreciated, glad to know the team is working on this 😄 |
Just ran into this as well. Everything was fine until I added a vite module to my workspace and discovered there was no way to make it work. I could, of course, use a separate repo, but then there would be no direct code sharing between back-end and front-end. |
+1 will be really nice to have this |
Currently the
compilerOptions
field is only supported in the workspace root. It should also be supported in workspace members.The text was updated successfully, but these errors were encountered: