fix(typescript): Change noEmitOnError default to false#544
Merged
shellscape merged 1 commit intorollup:masterfrom Sep 8, 2020
Merged
fix(typescript): Change noEmitOnError default to false#544shellscape merged 1 commit intorollup:masterfrom
noEmitOnError default to false#544shellscape merged 1 commit intorollup:masterfrom
Conversation
Contributor
|
Don't wanna rush, but is there anything blocking you from merging this in? |
Member
Author
|
Waiting for review |
Contributor
|
Thank you for this!! It will make it so much easier for newcomers to get started |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
BREAKING CHANGE:
noEmitOnErrornow defaults to false instead of true. This means that Rollup will show a warning when type errors are encountered but will still compile. The previous behaviour is available by changing the setting totrue.Rollup Plugin Name:
typescriptThis PR contains:
Are tests included?
Breaking Changes?
If yes, then include "BREAKING CHANGES:" in the first commit message body, followed by a description of what is breaking.
List any relevant issue numbers:
Description
For watch mode to work, warnings must be used instead of errors. This behaviour better matches how Typescript works, since it only warns for type errors but compiles anyways. However, its different from how bundlers like Webpack work, as they usually fail.