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

3.7.5 => 3.8.3 introduces breaking change(and shouldn't) #37416

Closed
rmainwork opened this issue Mar 16, 2020 · 4 comments
Closed

3.7.5 => 3.8.3 introduces breaking change(and shouldn't) #37416

rmainwork opened this issue Mar 16, 2020 · 4 comments

Comments

@rmainwork
Copy link

TypeScript Version: 3.8.3

Search Terms:

  1. Option 'noEmit' cannot be specified with option 'incremental'.
  2. typescript incremental noEmit
  3. tsc noEmit incremental

Code

{
  "incremental": true
}
tsc --noEmit

Expected behavior:

The typescript project should compile successfully (it does under 3.7.5) since 3.7.5 to 3.8.3 is not a semver breaking change the two should be backwards compatible, but aren't. https://semver.org/spec/v2.0.0.html#summary

Actual behavior:

tsconfig.json:15:5 - error TS5053: Option 'noEmit' cannot be specified with option 'incremental'.

15     "incremental": true,
       ~~~~~~~~~~~~~


Found 1 error.

Playground Link:

n/a (typescript playground doesn't have the option to configure the tsc command or set the incremental option in tsconfig.json

Related Issues:
n/a

@MartinJohns
Copy link
Contributor

since 3.7.5 to 3.8.3 is not a semver breaking change

TypeScript does not follow SemVer: #14116 (comment)

@rmainwork
Copy link
Author

rmainwork commented Mar 16, 2020

...oh.

...Well that's "fun".

Thanks for the heads up I guess.

Duplicate of #36917

@MartinJohns
Copy link
Contributor

There are good reasons to not follow SemVer. :-) You can read about them in #14116.

Also you can check out #36917, which mentions why noEmit and incremental is not allowed/supported together.

@rmainwork
Copy link
Author

rmainwork commented Mar 16, 2020

Yeah, thanks. I'm reading the thread just now...the only problem is that I'm pinned to 3.5.2 and getting 3.8.x.

If typescript doesn't follow semver...is there an explanation somewhere of what the version numbers actually mean? Do they mean anything at all?

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

No branches or pull requests

2 participants