-
Notifications
You must be signed in to change notification settings - Fork 6
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
Getting process exit code 1 when changing files #45
Comments
This is the output using DEBUG mode. |
Hm, it looks like you're running on WSL right? We have no formal support for windows or WSL but I will look into adding it. PRs also welcome! Also, that message is expected when the script you're actually running quits -- any chance you can share the contents of that script, or report that it works under other runners? |
Sure, this is the script. If I change anything inside of it, I get the exit code 1. import koa from "koa";
import { ServiceConfig } from "./service_config";
import { middleware_health_check, middleware_ignore_favicon } from "./middleware/AppBasicMiddleware";
import logger from "koa-logger";
const { port } = ServiceConfig.getConfig();
const app = new koa({
keys: ["xxx_secret_abc_123"]
});
app.use(logger());
app.use(middleware_ignore_favicon);
app.use(middleware_health_check);
app.use(async (ctx) => {
ctx.body = "Hiiiii!";
});
app.listen(port, () => {
console.log(`Service listening on port: ${port}`);
}); I'm not running WSL- just regular Windows. I'm not sure what other runtimes I could compare it with. I can confirm that using nodemon to watch an output "dev-build" directory, which itself is watched and rebuilt by esbuild, runs and restarts without issue. |
@lostpebble we just fixed a couple bugs with the |
Hi there, just started using this project today- but noticed the "hot reload" doesn't work for me. This includes simple updates like just changing the text inside a
console.log()
. I know it has nothing to do with the--inspect=9230
as I tried without it and it still threw the error.The text was updated successfully, but these errors were encountered: