Be able to disable noEmit-true warning

[jasonkuhrt]

Perceived Problem

• Nexus warns when noEmit tsconfig option is used
• It usually represents user error Clear errors/warnings when noEmit is enabled #702
• Sometimes it doesn't Be usable with nextjs #648
• when it doesn't, the warning is at best, annoying

Ideas / Proposed Solution(s)

• When the user knows they definitely warn noEmit, then, some ideas:
  • be able to disable the warning
  • use new explicit command like nexus check (keep nexus build warning, telling user to use nexus check if that was there intent)
  • pass flag to build like --no-emit (the doubling up being like a confirmation step that makes the warning go away)

[jasonkuhrt]

We can rethink this now that #866 is landing.

Nexus should force noEmit to always be true.

The tool that will be outputting is no long TS, but Nexus.

While its true that even with #866 users will be able to do --no-bundle it is only incidental that this makes TS be the thing doing the final output.

Even with --no-bundle, in the future, with #854, a bundler will become a core part of the tool chain.

So the new proposal is:

• Nexus will always force-set the noEmit option in tsconfig to false. It will log a warning when it does this. The warning will have two forms:

  1. No value present before

  Example:

   We have set the property `compilerOptions.noEmit` in your tsconfig file to `true`. This helps you avoid emit unwanted files should you or some tool ever accidentally run `tsc` manually.
  

  1. false value present

  Example:

   We have set the property `compilerOptions.noEmit` in your tsconfig file to `true`. For some reason you had it explicitly set to `false`. You shouldn't need this. Nexus takes care of outputting your build. You should not be using `tsc` manually. If you disagree with this please open an issue (https://nxs.li/issues/create/feature) and let us know why!