Hacker News: bartlomieju

New comment by bartlomieju in "Deno Desktop"

bartlomieju — Mon, 22 Jun 2026 10:49:52 +0000

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

New comment by bartlomieju in "Deno Desktop"

bartlomieju — Mon, 22 Jun 2026 10:48:51 +0000

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.

New comment by bartlomieju in "Deno Desktop"

bartlomieju — Mon, 22 Jun 2026 10:48:13 +0000

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

New comment by bartlomieju in "Deno Desktop"

bartlomieju — Mon, 22 Jun 2026 10:47:42 +0000

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

New comment by bartlomieju in "Deno Desktop"

bartlomieju — Mon, 22 Jun 2026 10:46:28 +0000

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

New comment by bartlomieju in "Deno Desktop"

bartlomieju — Mon, 22 Jun 2026 10:45:37 +0000

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

New comment by bartlomieju in "Deno 2.8"

bartlomieju — Mon, 25 May 2026 15:34:02 +0000

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 code I absolutely don't want node types included by default.

Since a few versions ago, Deno now has some of Node.js APIs included by default (eg. process or Buffer). It's really more of a bug fix to make type-checking work properly.

While it's not ideal, you can still decide which types you want included by default with `compilerOptions.types`. `["deno.ns", "web"]` should give you what you're looking for.

New comment by bartlomieju in "Deno 2.8"

bartlomieju — Mon, 25 May 2026 15:32:16 +0000

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 different set of globals for user code and different for code inside node_modules/ directory. It was a maintenance headache, made global lookups super slow and was really hard to explain to users. While Web "setTimeout" might have been nice in the beginning the fact that it required additional APIs like "Deno.unrefTimer" made it worse than Node's setTimeout.

New comment by bartlomieju in "Deno 2.8"

bartlomieju — Mon, 25 May 2026 15:29:43 +0000

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

New comment by bartlomieju in "Deno in 2023"

bartlomieju — Mon, 05 Feb 2024 13:50:02 +0000

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

New comment by bartlomieju in "Deno in 2023"

bartlomieju — Mon, 05 Feb 2024 13:47:46 +0000

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, with more improvements possible in the future. Stay tuned for upcoming releases.

New comment by bartlomieju in "A Node, TypeScript, TS-Node and ESM experience that works"

bartlomieju — Tue, 21 Nov 2023 18:13:04 +0000

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 allows you to manage `node_modules/` be the package manager of your choice. In other words, you should be able to drop Deno into an existing Node project.

New comment by bartlomieju in "A Node, TypeScript, TS-Node and ESM experience that works"

bartlomieju — Tue, 21 Nov 2023 18:10:27 +0000

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

New comment by bartlomieju in "Deno 1.35: A fast and convenient way to build web servers"

bartlomieju — Wed, 05 Jul 2023 22:10:19 +0000

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 "scripts" defined there, just try running "deno task ". Deno will automatically pick up "package.json" and try its best to run the that script.

It's not fully done, but in our testing we got a lot of non-trivial projects running that way. If something doesn't work in your case, I would greatly appreciate a bug report to help us fix this.

As for the written guide - there's not a single one at the moment - it's something we'll be looking into in the coming months.

New comment by bartlomieju in "Deno 1.35: A fast and convenient way to build web servers"

bartlomieju — Wed, 05 Jul 2023 20:32:15 +0000

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 what problems did you hit and look into solving them.

New comment by bartlomieju in "Node.js built-ins on Deno Deploy"

bartlomieju — Fri, 26 May 2023 16:11:34 +0000

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 stance that CommonJS is only supported in npm dependencies and cannot be used in user code (ie. you must use ESM in your application code).

New comment by bartlomieju in "Node.js built-ins on Deno Deploy"

bartlomieju — Fri, 26 May 2023 16:05:15 +0000

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 such these Node.js API are subject to the same permission model as regular Deno programs.

> however if deno were to support all npm packages, it would necessarily basically have to implement the entire node api, including support for pre async/await (aka callbacks)

We're not aiming for 100% compatibility, though we managed to polyfill a hefty amount of built-in Node modules, including ones that are callback based.

> consider just the c++ embedder apis. how exactly would deno deal with that with respect to permissions?

This is the same situation as with Deno's FFI API. You need to pass `--allow-ffi` flag to enable usage of `Deno.dlopen` (or `require("./foo.node")` for N-API extensions). That said when you load dynamic libraries all bets are off - we can't control what the dynamic library can do and you effectively open up your whole system. Still, you can't load such libraries unless `--allow-ffi` flag is passed.

Hope this clears up some things.

New comment by bartlomieju in "Deno 1.34: Deno compile supports NPM packages"

bartlomieju — Thu, 25 May 2023 12:58:38 +0000

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 best tackle that. If you have a specific use case in mind I would appreciate opening a feature request in our issue tracker.

New comment by bartlomieju in "Deno 1.34: Deno compile supports NPM packages"

bartlomieju — Thu, 25 May 2023 12:56:23 +0000

It's another issue, but it's close

New comment by bartlomieju in "Deno 1.34: Deno compile supports NPM packages"

bartlomieju — Thu, 25 May 2023 12:56:01 +0000

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