Remix clone Hacker News

GraalJs, it would seem, would count.

It’s not “obscure” or “exotic;” at least, no more than Node was when it was released. Honestly this is such a lame take to those of us who are working in JS outside of Node and Deno.

And people do work at that intersection.

IMO Deno is the worst option of all new JS runtimes and taking on this fight kind of makes sense that way. If you can’t win mindshare, start a fight. I guess. (In my opinion they should have simply designed Deno to be NPM compatible, but here we are.)

▲

lucacasonato 6 hours ago | parent [-]

Deno is NPM compatible

▲

sgammon an hour ago | parent | next [-]

Only recently... and yes, to Deno's great credit. Deno has an amazing team and this isn't commentary about their hard work; just disagreement with one of the early decisions.

▲

ultrakorn2 3 hours ago | parent | prev [-]

`is:open is:issue label:bug label:"node compat"` -> 203 issues currently open.

▲

harrisi 3 hours ago | parent [-]

Neat. But for a relevant query, try searching for "npm" instead. 0 issues listed. Further, in the `deno_npm` repo for npm resolving by the deno cli, there are two open issues. One is a feature request, and the other is not clearly an important issue.

▲

sgammon an hour ago | parent [-]

> Neat. But for a relevant query, try searching for "npm" instead

`is:issue is:open npm` 467 open

https://github.com/denoland/deno/issues?q=is%3Aissue+is%3Aop...

`is:issue is:open label:bug npm` 199 open

https://github.com/denoland/deno/issues?q=is%3Aopen+is%3Aiss...

For the record, "NPM compat" probably does include many feature requests (legitimately), not just bugs.

	▲	harrisi 4 minutes ago \| parent [-]
		I did make a mistake. Thanks for pointing that out. However, the point that deno is npm compatible is still true, contrary to what you originally said.