Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Deno 2.9

deno.com

Post reply on HN
Print view View original

41–50 of 63 posts

Re: Deno 2.9

#41

Post by bartlomieju »

catapart wrote: post #35
nwhit wrote: post #32

Earlier quoted context omitted.

What node version do you have installed? I cannot reproduce the issue on that repo, I've tried with node versions all the way back to node 12.

here's a dump of the console: ``` catapart@snake:~/Development/magnitce-code-example$ deno install Warning The following packages are deprecated: ┖─ npm:boolean@3.2.0 (Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.) catapart@snake:~/Development/magnitce-code-example$ deno task dev Task dev vite You are using Node.js 20.11.1. Vite requires Node.js version 20.19+ or 22.12+.…

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 minor = parseInt(nodeVersion.split(".")[1], 10); return (major === 20 && minor >= 19) || (major === 22 && minor >= 12) || major > 22; } if (!checkNodeVersion(process.versions.node)) console.warn(`You are using Node.js ${process.versions.node}. Vite requires Node.js version 20.19+ or 22.12+. Please upgrade your Node.js version.`); ```

And that error should be thrown only in Deno Are you 100% sure this is not running some old version of Deno on your system?

Re: Deno 2.9

#42

Post by catapart »

bartlomieju wrote: post #41
catapart wrote: post #35

Earlier quoted context omitted.

here's a dump of the console: ``` catapart@snake:~/Development/magnitce-code-example$ deno install Warning The following packages are deprecated: ┖─ npm:boolean@3.2.0 (Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.) catapart@snake:~/Development/magnitce-code-example$ deno task dev Task dev vite You are using Node.js 20.11.1. Vite requires Node.js version 20.19+ or 22.12+.…

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 minor = parseInt(nodeVersion.split(".")[1], 10); return (major === 20 && minor >= 19) || (major === 22 && minor >= 12) || major > 22; } if (!checkNodeVersion(process.versions.node)) console.warn(`You are using Node.js ${process.versions.nod…

you nailed it! I tried it on a different machine, just to be sure, and it worked without a problem. So then I did a full restart on the mint machine and I got a whole new error that was talking about missing files. So I uninstalled deno and reinstalled it, and it worked exactly like it did on the other machine.

I actually started this after another user said they couldn't reproduce the issue, but you figured it out before I finished reporting back.

Thanks for straightening me out on this! As I said a few days ago on the Deno Desktop HN Topic, I'm looking forward to this newest version!

Re: Deno 2.9

#43

Post by conartist6 »

undefined_void wrote: post #40
conartist6 wrote: post #29

Earlier quoted context omitted.

AI lets people be reaaaaaaally "productive" when leaning into entirely the wrong work. Deno has no future if all it wants to be is a clone of node, so it just seems to me like your work is to speed the collapse

> A "node:http" regression caused by a PR fixing many of outstanding issue. Author explains and apologizes. > "Deno has no future" I think there may be other things bothering you? These comments aren't really productive and discourage maintainers to even continue replying. Disclaimer: I am a maintainer.

Oh, you bet that my goal is not to give the AI users a pat on the back. I want them to know my unfiltered contempt for their unfiltered contempt for me (and anyone like me who still works with their hands).

Re: Deno 2.9

#44

Post by timw4mail »

someguyiguess wrote: post #23
MoonWalk wrote: post #5

Earlier quoted context omitted.

Well if Node compatibility is your big deal then yeah, why not just use it? I started a new project on Deno to avoid the NPM mess. Node compatibility was a distraction for the product. I'm tired of everything depending on Node. Assuming that everybody uses it is lazy.

To be fair, you can't blame a person for thinking that a runtime created by the same guy who created Node would work with Node.

But the point of Deno was to try to avoid pitfalls that became apparent in NodeJS, so some over-correction was bound to happen.

Re: Deno 2.9

#45

Post by conartist6 »

conartist6 wrote: post #43
undefined_void wrote: post #40

Earlier quoted context omitted.

> A "node:http" regression caused by a PR fixing many of outstanding issue. Author explains and apologizes. > "Deno has no future" I think there may be other things bothering you? These comments aren't really productive and discourage maintainers to even continue replying. Disclaimer: I am a maintainer.

Oh, you bet that my goal is not to give the AI users a pat on the back. I want them to know my unfiltered contempt for their unfiltered contempt for me (and anyone like me who still works with their hands).

for the record the fact that I'm radically anti-AI also doesn't mean that I'm wrong that over the long term average it is a force that creates compounding debt and unmakes communities

Re: Deno 2.9

#46

Post by undefined_void »

conartist6 wrote: post #43
undefined_void wrote: post #40

Earlier quoted context omitted.

> A "node:http" regression caused by a PR fixing many of outstanding issue. Author explains and apologizes. > "Deno has no future" I think there may be other things bothering you? These comments aren't really productive and discourage maintainers to even continue replying. Disclaimer: I am a maintainer.

Oh, you bet that my goal is not to give the AI users a pat on the back. I want them to know my unfiltered contempt for their unfiltered contempt for me (and anyone like me who still works with their hands).

> unfiltered contempt for me

bro what

Re: Deno 2.9

#47

Post by conartist6 »

undefined_void wrote: post #46
conartist6 wrote: post #43

Earlier quoted context omitted.

Oh, you bet that my goal is not to give the AI users a pat on the back. I want them to know my unfiltered contempt for their unfiltered contempt for me (and anyone like me who still works with their hands).

> unfiltered contempt for me bro what

I totally understand that you wouldn't get it if you'd never seen the kinds of things people say about non-AI users (writ large) and thought "they mean me".

I've been told I'm insane, retarded, a megalomaniac, or simply extinct. People I once respected are trying to convince the next generation not to learn, not to gain skill, not to build community. People with as much logic as a heap of bat feces tell me confidently that code is "over". Now if I was an AI I'd be very polite about this, but I'm a human so I say they can go fuck themselves.

Re: Deno 2.9

#48

Post by bobajeff »

phaser wrote: post #36

I am the freaky outlier that's actually excited about this. My city builder game, Microlandia[1], runs on Deno. The game's graphics and UI is a Three.js/React app, but the guts of the game are in a "sidecar" process that is a `deno compile` typescript executable. On Mac, there's a Tauri shell that runs both client and server, and for Linux and Windows we use Electron, (Tauri proved to be quite problematic except when…

Congrats on your game it reminds me both of SimCity on the SNES and SimCity 2000 (pc).

I'm also using a cursed stack (deno + pyodide) and it's awesome! Everything works surprisingly well and I can do my Python experiments in a notebook while hot reloading via vite in a browser + quickly try things in the dev console.

Re: Deno 2.9

#49

Post by MoonWalk »

pier25 wrote: post #34
MoonWalk wrote: post #5

Earlier quoted context omitted.

Well if Node compatibility is your big deal then yeah, why not just use it? I started a new project on Deno to avoid the NPM mess. Node compatibility was a distraction for the product. I'm tired of everything depending on Node. Assuming that everybody uses it is lazy.

> Node compatibility was a distraction for the product I've gone back and forth on this point over the years. Yeah, Node compat has probably affected the rest of the product. I imagine at some point they (or their investors) freaked out because adoption wasn't happening. And the reality is it really doesn't matter if your product is better when nobody is using it. In retrospect I think it would have been a better dec…

Yep, it's hard to say what the right move was.

Re: Deno 2.9

#50

Post by MoonWalk »

Tiberium wrote: post #6
MoonWalk wrote: post #5

Earlier quoted context omitted.

Well if Node compatibility is your big deal then yeah, why not just use it? I started a new project on Deno to avoid the NPM mess. Node compatibility was a distraction for the product. I'm tired of everything depending on Node. Assuming that everybody uses it is lazy.

Because I wanted native TypeScript support which Node only gained relatively recently and only partially, plus the issues I showed are regressions - they worked fine in earlier Deno versions.

Makes sense.
Post reply on HN