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

feat(vite): allow passing path to custom tsconfig file when skipTypeCheck is false #19784

Merged
merged 1 commit into from
Jan 30, 2024

Conversation

vneogi199
Copy link
Contributor

When skipTypeCheck is false and no tsconfig file exists in projectRoot, it returns undefined which causes join(opts.workspaceRoot, opts.tsconfig) in validateTypes to fail with The "path" argument must be of type string. Received undefined.
Allow user to pass custom tsconfig file location which can be in parent/child directory of projectRoot

Current Behavior

If tsconfig does not exist is projectRoot it fails with The "path" argument must be of type string. Received undefined

Expected Behavior

Allow user to pass custom tsconfig file, so that vite build does not fail and type checking works.

Related Issue(s)

@vercel
Copy link

vercel bot commented Oct 22, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
nx-dev ✅ Ready (Inspect) Visit Preview Jan 29, 2024 3:02pm

…heck is false

When skipTypeCheck is false and no tsconfig file exists in projectRoot, it returns undefined which
causes `join(opts.workspaceRoot, opts.tsconfig)` to fail with `The "path" argument must be of type
string. Received undefined`.
Allow user to pass custom tsconfig file location which can be in parent/child directory of
projectRoot
@mandarini mandarini merged commit d147604 into nrwl:master Jan 30, 2024
6 checks passed
FrozenPandaz pushed a commit that referenced this pull request Jan 31, 2024
Copy link

github-actions bot commented Feb 5, 2024

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants