Closed scarf005 closed 2 months ago
@scarf005 It was removed here https://github.com/lumeland/lume/commit/bff5800be2414b80f6288e27bc8d8e0be832117a#diff-019b7b01afa861216d127d59201e36bc7b5ccbb44be90f521af6f044808b09a1
I don't remember exactly the reason, but I got some errors importing stop
so I though it wasn't needed anymore (stop
only is required in Deno, in Node it works automatically).
As a workaround, adding this to _config.ts
works:
import { stop } from "lume/deps/esbuild.ts"
const isWatch = Deno.args.some((arg) => ["-s", "--serve", "-w", "--watch"].includes(arg))
if (!isWatch) addEventListener("lume:afterBuild", stop)
great.
Could you try if this happens with splitting: false
?
The plugins works differently depending on this option in the esbuild settings.
changing the value of splitting
doesn't change the result, probably due to both code path not running esbuild.stop()
as mentioned in https://esbuild.github.io/getting-started/#deno
@scarf005 I just restored the stop()
call. Can you confirm it works fine now?
You can use the latest development version with deno task lume upgrade --dev
.
fixed in v2.1.4
Version
2.1.3
Platform
ubuntu
What steps will reproduce the bug?
deno.json
,_config.ts
,main.tsx
deno.json
_config.ts
main.tsx
deno task build
.How often does it reproduce? Is there a required condition?
it always happens.
What is the expected behavior?
after building the project must stop immediately.
What do you see instead?
The plugin hangs and gets killed after 10 seconds.
Additional information
it might be that
esbuild.stop()
isn't called?