Deno+vite crashes on node dependency
Earlier today I was happy because everything worked on my m1 macbook.
When I've returned home (arch) I got errors from latest deno...
(I am running deno on the metal, but I will provide a way to reproduce it with docker:)
9 Replies
Am I doing something in unintended way?
(metal, interactive shell)
import { join } from "node:path"
join works like expected
(rollup native.js uses const { platform, arch, report } = require('node:process');
so in interactive shell I did import { report } from "node:report"
report is undefined@Danielduel Can you file an issue for that? That sounds like a bug in Deno https://github.com/denoland/deno/issues/new
Went ahead and pasted the messages into an issue. https://github.com/denoland/deno/issues/21355
GitHub
node:
process.report
is missing · Issue #21355 · denoland/denoReported on discord: Earlier today I was happy because everything worked on my m1 macbook. When I've returned home (arch) I got errors from latest deno... (I am running deno on the metal, but I...
Thank you @marvinh., do I have to do anything now?
no, someone of the cli team will take a look at that issue. There is enough information in there to debug it
Thank you ^^
@bartlomieju thanks for the quick response, I suggest doing it in 2 parts - first just to make vite run with most of stuff stubbed in the polyfill and 2nd part to make actual implementation of the report object
Yup, that's a good approach!
I miss a detail here - despite I've built deno with an implementation of report in process... importing "node:process" still fetches it from the remote
GitHub
fix(ext/node): add stubbed process.report by Danielduel · Pull Requ...
targets #21355, #21304
Issues with vite are caused by the missing node's process report object.
I've stubbed most of it for starter and replaced trivial spots with stubs.
I am not sure how ...