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

chore: use @tsconfig/node14 and stricter TS config #1242

Merged
merged 2 commits into from Sep 10, 2022
Merged

Conversation

SimenB
Copy link
Member

@SimenB SimenB commented Sep 10, 2022

#1226 fails CI due to "missing" flatMap - instead of manually defining lib etc., extending @tsconfig/node14 seems cleaner

@SimenB SimenB changed the title chore: use @tsconfig/node14 and stricter TS config chore: use @tsconfig/node14 and stricter TS config Sep 10, 2022
@SimenB SimenB merged commit 7f3cc12 into main Sep 10, 2022
@SimenB SimenB deleted the @tsconfig/node14 branch September 10, 2022 11:46
@github-actions
Copy link

🎉 This PR is included in version 27.0.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

"noEmit": true,
"importsNotUsedAsValues": "error",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curious why this? I can live with it, but my understanding is that its "maybe" needed in some rare cases (e.g. using something that isn't smart enough to automatically figure it out like tsc and Babel can), and it means extra noise in diffs when you need to switch between imports.

I'm pretty sure it doesn't help us as I've looked at our compiled outside in the past and feel this is the sort of thing I'd have done already if I found it was adding unneeded imports

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants