Update tsconfig.json #146
Merged
Update tsconfig.json #146
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MinixBF
approved these changes
Oct 15, 2023
|
|
I trust you on this. So let's go 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update the
tsconfig.jsonfollowing the video of Matt Pocock.New additions
"moduleDetection": "force": Every file is treated as a module instead of a global script (is it good for thescripts/folder?)"noEmit": true: Ensures that no JS file will be produced during type-check"verbatimModuleSyntax": true: Ensures the use of the correctcjs/mjsinside modulesWarning
I'm not sure all these additions are suited for the project/Svelte(Kit)/do not already exist in the base
.svelte-kit/tsconfig.json, so it's not 100% safe to merge before a double check.Note
PR 90% made from the GitHub Mobile app! Would've been 100% if we had the option to rename the branch we are creating :)