fix: set compilerOptions.noEmit to avoid tsconfig.json warning

[danielroe]

🔗 Linked issue

nuxt/eslint#414

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This sets noEmit which is correct for a tsconfig.json meant primarily for IDE type hinting.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[pi0]

How this affects nitro behavior?

[danielroe]

It won’t affect any behaviour outside of ide type hints (without this PR, you’ll get an IDE warning when you use JS files in a nitro project)

[pi0]

Sorry if my message seems stupid, but how i can see such a warning in a nitro project?

[danielroe]

I’ll provide a screenshare later as I’m just having dinner. But it’s definitely the right thing to do. See https://www.totaltypescript.com/tsconfig-cheat-sheet - there are likely more things we should bring in from that article too…

[pi0]

It is a harmless config but i won't merge a PR without a nitro minimal reproduction or at least enough merits. Currently only linked reason is a closed issue in eslint module.

[danielroe]

Here you go.

Hope this helps explain.

CleanShot.2024-04-29.at.19.32.04.mp4

[pi0]

Thanks!

[danielroe]

You are very welcome 😊