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

Ensure include is empty #18

Merged
merged 2 commits into from
Nov 19, 2021
Merged

Ensure include is empty #18

merged 2 commits into from
Nov 19, 2021

Conversation

IPWright83
Copy link
Contributor

Resolves #5

@gustavopch gustavopch merged commit 6996f84 into gustavopch:master Nov 19, 2021
@github-actions
Copy link

🎉 This PR is included in version 1.1.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

kylorhall added a commit to kylorhall/tsc-files that referenced this pull request Nov 30, 2021
This is an idea to fix gustavopch#20.

Instead of discarding all includes, which seems to discard required global `.d.ts` files, can we use the `typeRoots` a config may have setup instead?

I don't think this quite hits the mark however:
 - Does everyone use `typeRoots` in this manner?  I do not know.
 - Likely will not work for a monorepo with nested tsconfig as files are resolved to the root.
 - Often `typeRoots` will import a fair bit, this could still include a large % of your codebase.  My `typeRoots` includes `node_modules/@types`–this may defeat the purpose gustavopch#18 set out to resolve.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

set "include" tsc config option to empty string to prevent normal include settings from applying
2 participants