You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Whenever deno/the build encounters a syntax error, packup serve crashes and needs to be restarted.
Describe the solution you'd like
On exceptions, packup should render the error or exception but keep watching the file tree for changes and then re-try a build on change.
Describe alternatives you've considered
Alternative would be to run packup build in a loop or through an inotify callback, and have another devserver serve the built assets when they change.
Additional context
Just add a syntax error to a .ts file, save it, and the packup process shows the error. E.g.
[ERROR] [plugin deno] The module's source code could not be parsed: Unexpected token `slideControls`. Expected * for generator, private key, identifier or async at file:///xxx/main.ts:116:9
const slideControls = document.getElementById('slideshow-controls') as HTMLElement;
~~~~~~~~~~~~~
Error: Build failed with 1 error:
error: The module's source code could not be parsed: Unexpected token `slideControls`. Expected * for generator, private key, identifier or async at file:///xxx/main.ts:116:9
....
It won't pick up new saves to that file and just hangs. So when fixing this syntax error, the packup process has to be re-started.
Is your feature request related to a problem? Please describe.
Whenever deno/the build encounters a syntax error,
packup serve
crashes and needs to be restarted.Describe the solution you'd like
On exceptions, packup should render the error or exception but keep watching the file tree for changes and then re-try a build on change.
Describe alternatives you've considered
Alternative would be to run packup build in a loop or through an inotify callback, and have another devserver serve the built assets when they change.
Additional context
Just add a syntax error to a .ts file, save it, and the packup process shows the error. E.g.
It won't pick up new saves to that file and just hangs. So when fixing this syntax error, the packup process has to be re-started.
The text was updated successfully, but these errors were encountered: