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 there anything that prevents vercel dev from bundling the contents?
Every time I run a lambda, I have no issues. But when I try to manually bundle it, or run vercel dev I get this.
error: Uncaught AssertionError: Assertion failed.
at Object.assert ($deno$/util.ts:33:11)
at compile ($deno$/compiler.ts:1355:5)
at async tsCompilerOnMessage ($deno$/compiler.ts:1548:22)
at async workerMessageRecvCallback ($deno$/runtime_worker.ts:74:9)
So now I am not sure of the issue. If I remove mustache, it works. I had issues with multiple things that I am importing. I am not saying the vanilla code is an issue. I am trying to understand why it's so fragile, and what these libraries are using that can be bundled outside of now-deno, but in combination with now-deno just fail.
Closing this issue, because I feel like Deno was not available in my path. It was not until recently when i tried to install a script that I realized it was missing, even though I had the command.
Is there anything that prevents
vercel dev
from bundling the contents?Every time I run a lambda, I have no issues. But when I try to manually bundle it, or run
vercel dev
I get this.So now I am not sure of the issue. If I remove mustache, it works. I had issues with multiple things that I am importing. I am not saying the vanilla code is an issue. I am trying to understand why it's so fragile, and what these libraries are using that can be bundled outside of
now-deno
, but in combination withnow-deno
just fail.vercel.dev
api/test/index.ts
api/test/template.html
The text was updated successfully, but these errors were encountered: