Repository navigation
Watching and compiling stops when having an error in Typescript file #492
Description
- Rollup Plugin Name: @rollup/plugin-typescript
- Rollup Plugin Version: 5.0.1
- Rollup Version: 2.20.0
How Do We Reproduce?
clone this repo: https://github.com/simonvanbennekom/rollup
npm install
npm run watchnamespace Account {
export function onLoad(){
var number = 1;
privateFunction(number);
}
function privateFunction(input : number) {
console.log(input)
}
}Change value of number variable in Account.ts, to "" and Save the file
Expected Behavior
Terminal should show this kind of message: Argument of type 'string' is not assignable to parameter of type 'number'.Actual Behavior
rollup v2.20.0
bundles ./Scripts/Account.ts → Scripts...
created Scripts in 1.1s
[2020-07-08 13:33:02] waiting for changes...
rollup v2.20.0
bundles ./Scripts/Account.ts → Scripts...
Terminal will be reused by tasks, press any key to close it.
Activity
shellscape commentedon Jul 8, 2020
Thanks for opening an issue. Citing the issue template:
Please add a reproduction and we'll be happy to triage further.
simonvanbennekom commentedon Jul 8, 2020
@shellscape Hi updated the post, added a repository and steps to reproduce. Hope this is enough so you can help me with my issue. Thanks. Can u reopen this issue?
shellscape commentedon Jul 8, 2020
Please add the sections of the issue template that you removed.
simonvanbennekom commentedon Jul 8, 2020
@shellscape sorry, missed that. fixed it now.
shellscape commentedon Jul 9, 2020
You have no
rollup.config.jsfile in your reproduction repo. You'll need one and you'll need to configure thetypescriptplugin in order to use TS. Following your instructions I receive:I'm sorry but the issues here are not a forum for support. I searched our issues here and I found #255 and #258 which might be related. I encourage you to check out and discuss on the issues which address the same problem.
simonvanbennekom commentedon Jul 9, 2020
noEmitOnError fixes the problem. sorry for the inconvenience.
shellscape commentedon Jul 9, 2020
No worries. Glad you found the fix.