Unstable byonm breaks Deno Fresh
When I try to run the boilerplate Deno Fresh project with the byonm unstable flag, it seems to start but does not turn interactive. I know unstable flags are there to protect us from breaking changes, but maybe someone already solved this or knows how to solve it.
To get it to where I am, I
- created a new project with tailwindcss.
- set the byonm unstable flag in deno.json
- added the following package.json and installed through npm
In the console, it shows the following error
Error: Build failed with 5 errors: error: Cannot convert undefined or null to object error: Cannot convert undefined or null to object error: Cannot convert undefined or null to object error: Cannot convert undefined or null to object error: Cannot convert undefined or null to object at failureErrorWithLog (https://deno.land/x/esbuild@v0.20.2/mod.js:1626:15) at https://deno.land/x/esbuild@v0.20.2/mod.js:1034:25 at runOnEndCallbacks (https://deno.land/x/esbuild@v0.20.2/mod.js:1461:45) at buildResponseToResult (https://deno.land/x/esbuild@v0.20.2/mod.js:1032:7) at https://deno.land/x/esbuild@v0.20.2/mod.js:1061:16 at responseCallbacks.<computed> (https://deno.land/x/esbuild@v0.20.2/mod.js:679:9) at handleIncomingPacket (https://deno.land/x/esbuild@v0.20.2/mod.js:739:9) at readFromStdout (https://deno.land/x/esbuild@v0.20.2/mod.js:655:7) at https://deno.land/x/esbuild@v0.20.2/mod.js:1974:11 at eventLoopTick (ext:core/01_core.js:175:7) { errors: [Getter/Setter], warnings: [Getter/Setter] }For those interested, I'm invested in this setup to work because I want a Deno Fresh web client to work in my existing pnpm workspace (monorepo). Deno will live in the 'apps/web' subdirectory and will use packages installed from 'packages/*' through pnpm.
6 Replies
From what I can puzzle out, some esbuild plugin doesnβt get imported correctly. Resulting in a nullish value instead of the expected plugin object
Cc @marvinh.
I'm not able to reproduce that. The dev server starts, I can visit the page in the browser and the islands are interactive.
Weird, Iβll give it another try
Latest deno stable?
yes, also tried with the latest rc release
Thanks
Tried it in docker, just to be sure it wasn't MacOS fooling around. Same results
Deno
deno 1.46.3 (stable, release, aarch64-unknown-linux-gnu)
v8 12.9.202.5-rusty
typescript 5.5.2
Fresh
1.7.1
npm
10.8.3
To be sure, I removed the node_modules and byonm flag, which makes it work as expected. It's not a Deno/Fresh fluke
I was unable to figure out why this doesn't work for me with v1. But the v2 rc runs perfectly. Seeing the projected timeline, v2 is acceptable to use and my problem is solved.
Thank you for taking some time to check with me.