Adding `noEmit: true` is a breaking change and should be a major release version about tsconfig HOT 6 CLOSED

@sodatea can I get your thoughts on this?

from tsconfig.

Technically this library is still zerover, so any minor version bump could be breaking.

from tsconfig.

It's been 0.x for 3 years now, so I'd assume it would be considered stable; regardless of whether the version was actually ever bumped to 1.x

from tsconfig.

In practice, 0.4.0 -> 0.5.0 is considered a major release that can contain breaking changes.
https://github.com/npm/node-semver#caret-ranges-123-025-004

from tsconfig.

Agree that it is opinionated.

we have our own settings for exporting/generating types,

IMO that's the point of the defaults.
Those who are able to write their own settings would know how to deal with that option.
But many users don't care or don't know what each options do, and we need to provide a good-enough default for them.

from tsconfig.

This wasn't flagged as a major release, based on the commit message:

feat: turn on noEmit by default and add tsconfig.lib.json

I think the issue is that this change makes the assumption that the developer's use-case is a "non-library project."

This change makes it confusing for any developer that is new to Vue, using the standard configuration provided, to create a Vue component library without having to understand why their package isn't emitting the proper type declarations.

We can close the issue (and I really appreciate you taking a look).

Can I suggest the README be updated to explain the default noEmit option and the scenario in which a developer would want to override it?

from tsconfig.