Viewing profile — bartlomieju

Okay I traced it, the problem is in `node_modules/vite/dist/node/cli.js`: ``` function checkNodeVersion(nodeVersion) { const major = parseInt(nodeVersion.split(".")[0], 10); const …

Sure, we also managed to close ~30 outstanding issues with this rewrite and set us up to reach ~90% node:http compatibility, so overall I consider it a success.

We tried to build `node:http` on top of Rust libraries (like Hyper) but we failed for a couple years. So earlier this year we decided to make it compatible (by using llhttp to have…

> Seems like the core of these issues was a Claude-coauthored PR: https://github.com/denoland/deno/pull/33208 Disclaimer: I'm the author of the linked PR. Using AI here is not real…

Gee, sorry to hear that. It's Bartek from the Deno team here. This is really a whack-a-mole. We currently present the latest stable Node.js version (26.3.0) so the error is not cor…

Bartek from Deno team hear. I'll love to hear what you feel is missing so we could improve `deno desktop` for more users.

Yes, you can do all that. You get a fully-fledged Deno program that can do all of this, _plus_ you get a frontend GUI app.

Bartek from the Deno team here. No promises yet, but we're looking into feasibility of it.

Sorry to hear that, could I ask you to file an issue in our bug tracker?

Thanks, I'll update the docs. When we wrote them a couple weeks back, Electrobun was announcing Linux only support.

Bartek from the Deno here. Nope, we do support enums OOTB.

Bartek from the Deno team here. Thanks for the feedback, I understand your frustration. > The worst of the changes is "lib.node included by default", if I'm writing Deno or web cod…

Bartek from the Deno team here. Thanks for the feedback. I assure you this is not a short-sighted change. This has been a problem since before Deno 1.0. We resorted to hacks like d…

Thanks for feedback, I opened a PR to implement linking functionality that seems more familiar to npm's strategy: https://github.com/denoland/deno/pull/34359

Bartek from the Deno team here - we are actively working on improving experience running NextJS projects in Deno.

Hi, Bartek from the Deno team here. We are actively looking into improving this situation and from initial investigations we were able to shave off roughly 40% of the baseline size…

Bartek from the Deno team here. You can also use `package.json` and bare specifiers with Deno. We also recently added `--unstable-byonm` flag (Bring Your Own Node Modules) that all…

Bartek from the Deno team here. We are working on making this possible with a flag in the upcoming release.

A couple months back we added an ability for Deno to run projects authored for Node.js directly. Eg. if you have a Vite app (or any other app really) with "package.json" and some "…

Bartek from the Deno team here. Sorry to hear that - we made great progress in making Deno drop-in replacement this year, but we certainly are not yet there 100%. I'd love to hear …

Just to clarify - we do have support for node_modules/ resolution (with all of its quirks and gotchas), otherwise we wouldn't be able to load npm packages. However we made a hard s…

Bartek from the Deno team here, let me clarify a few things. > for one the security model is incompatible with node APIs. All Node.js APIs are polyfilled using Deno APIs and as suc…

These modules can be included but currently there's no way to use them - that's because they need to be present on disk to load them as dynamic libraries. We're debating how to bes…

It's another issue, but it's close

Bartek from the Deno team here. We're currently missing polyfills for IPC module to be able to use `next dev` command.