-
-
Notifications
You must be signed in to change notification settings - Fork 561
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
Watch mode cannot recover with typescript #258
Comments
Currently you have |
@danimoh yes, it has no effect. |
As stated on plugin readme, it ignores the
|
@Tylerian yeah, you're right Though I feel this should be enabled by default in watch mode, otherwise it's rather unintuitive. Anyway, thanks for the help - it was getting pretty annoying to always restart my watchers. |
Yeah, I agree with that too. Perhaps you can open a new Feature Request so the maintainers can discuss this with you and hopefully agree to add it to the plugin. |
For people who come across this because they want it on (/liked the default from before whenever #492 gets released) you can do this //tsopts
{
noEmitOnError : !process.env.ROLLUP_WATCH
} |
Running rollup in watch mode with typescript plugin if the typescript code is invalid the watcher breaks and exits with exit code 1. This make it impossible to re-build the code on code changes - you need to re-start the command every time.
(
noEmitOnError
ts compiler option doesn't help here)How Do We Reproduce?
https://github.com/karolis-sh/issue-rollup-typescript-1 (has a readme file)
Expected Behavior
Watch mode should work just like using js files.
Actual Behavior
Watch mode exits with exit code 1.
The text was updated successfully, but these errors were encountered: