Skip to content
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

Open
Tracked by #10
dsherret opened this issue Jul 10, 2024 · 8 comments · May be fixed by #27009
Open
Tracked by #10

Support compilerOptions in workspace members #24504

dsherret opened this issue Jul 10, 2024 · 8 comments · May be fixed by #27009
Assignees
Labels
feat new feature (which has been agreed to/accepted) workspaces
Milestone

Comments

@dsherret
Copy link
Member

Currently the compilerOptions field is only supported in the workspace root. It should also be supported in workspace members.

@albnnc
Copy link
Contributor

albnnc commented Aug 27, 2024

Any update on this?

@AdityaBorkar
Copy link

Any update? This feature is essential for many projects. For me, it's the only blocker for migrating to deno.

@3flippa
Copy link

3flippa commented Oct 20, 2024

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

@Andonvr
Copy link

Andonvr commented Oct 29, 2024

Same, this is a blocker for me.

@bartlomieju
Copy link
Member

FYI we are aware that this is highly requested and are working on a prototype for a solution.

@marsian83
Copy link

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 😄

@bartlomieju bartlomieju added this to the 2.1.0 milestone Nov 5, 2024
@UBy
Copy link

UBy commented Nov 8, 2024

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.

@juanbercoff
Copy link

+1 will be really nice to have this

@bartlomieju bartlomieju modified the milestones: 2.1.0, 2.2.0 Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat new feature (which has been agreed to/accepted) workspaces
Projects
None yet
Development

Successfully merging a pull request may close this issue.