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

make tsconfig.json configurable #1258

Open
1 task done
munxar opened this issue Aug 30, 2024 · 1 comment
Open
1 task done

make tsconfig.json configurable #1258

munxar opened this issue Aug 30, 2024 · 1 comment
Labels
status: under review Further discussion is needed to determine this issue's scope and/or implementation type: feature Introduction of new functionality to the application

Comments

@munxar
Copy link

munxar commented Aug 30, 2024

Prerequisites

  • This feature already exists in shadcn/ui - if not, it won't be considered here so don't continue with your issue.

Describe the feature

I know that this has been discussed here #214.

My issue is that I have a Svelte / Inertia / AdonisJS project that uses multiple tsconfig.json files (frontend / backend).
Other shadcn ports like shadcn-vue make this configurable in the cli (https://github.com/radix-vue/shadcn-vue/blob/85b10641c22a7ce0275219bee78a4a9e8e586b46/packages/cli/src/commands/init.ts#L142) and store the tsconfig.json in the components.json.
Could this be an option?
If you don't like the additional setup step, an option to overwrite in components.json would help in this edge cases.

p.s. sorry for the "hacking" the prerequisitites.
p.p.s. As a workaround I currently just add the path aliases to my root tsconfig.json when running the cli.

@munxar munxar added the type: feature Introduction of new functionality to the application label Aug 30, 2024
@huntabyte huntabyte added the status: under review Further discussion is needed to determine this issue's scope and/or implementation label Sep 19, 2024
@huntabyte
Copy link
Owner

Do you have any thoughts on the feasibility of this @AdrianGonz97 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: under review Further discussion is needed to determine this issue's scope and/or implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants