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

Umbrella: Evaluate all existing compiler options #58

Closed
37 tasks
jbrantly opened this issue Sep 25, 2015 · 3 comments
Closed
37 tasks

Umbrella: Evaluate all existing compiler options #58

jbrantly opened this issue Sep 25, 2015 · 3 comments
Labels

Comments

@jbrantly
Copy link
Member

There are a lot of TS compiler options. Some make sense with webpack, some don't. There have been pain points in the past where certain options cause issues (declaration, sourceMap, noLib, etc). So far these have been handled as reported on a case-by-case basis but I think it would be good to be proactive and evaluate all compiler options to make sure that the loader:

  1. Doesn't fail
  2. Possibly actively supports the option
  3. Possibly provides sane defaults

Here is an ongoing list of compiler options:

  • declaration
  • help
  • version
  • module
  • project
  • target
  • watch
  • charset
  • diagnostics
  • emitBOM
  • emitDecoratorMetadata
  • experimentalAsyncFunctions
  • inlineSourceMap
  • inlineSources
  • isolatedModules
  • jsx
  • listFiles
  • locale
  • mapRoot
  • moduleResolution
  • newLine
  • noEmit
  • noEmitOnError - Compiler Option: noEmitOnError #91
  • noEmitHelpers
  • noImplicitAny
  • noLib
  • noResolve
  • out
  • outDir
  • outFile
  • preserveConstEnums
  • removeComments
  • rootDir
  • sourceMap - Compiler Option: sourceMap #59
  • sourceRoot
  • stripInternal
  • suppressImplicitAnyIndexErrors
@stale
Copy link

stale bot commented Jan 19, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

1 similar comment
@stale
Copy link

stale bot commented Mar 20, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Mar 20, 2019
@stale
Copy link

stale bot commented Mar 27, 2019

Closing as stale. Please reopen if you'd like to work on this further.

@stale stale bot closed this as completed Mar 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant