Hacker GitHub

← All repos

denoland/deno

View on GitHub ↗ ★ 108,792 Rust

A modern runtime for JavaScript and TypeScript.

202 mentions on Hacker News by 161 people: 34 stories, 168 comments · first 2018-08-23 · latest 2026-10-16

Mentions per year 202 mentions · busiest year 2020 (45)
20082026
  1. …the content of a redirect, like in a browser. [0] https://github.com/nodejs/undici/issues/1072 [1] https://github.com/denoland/deno/pull/8353 [2] https://github.com/denoland/deno/issues/4389
    comment by zebracanevra · 2022-02-01 · in Fetch API has landed into Node.js
  2. …local HTTPS/HTTP2 setups in node these days. [1] https://github.com/nodejs/node/issues/3159 [2] https://github.com/denoland/deno/pull/11491
    comment by lewisl9029 · 2022-01-17 · in Some ways DNS can break
  3. …on it. Deno developers consistently ignore security issues, high priority bugs take months to fix. https://github.com/denoland/deno/issues/11964 https://github.com/denoland/deno/issues/9750 API-based access control can’t possibly work…
    comment by goldsteinq · 2022-01-10 · in State of the Web: Deno
  4. I'm pretty sure Deno just uses the open source TypeScript compiler: https://github.com/denoland/deno/tree/main/cli/tsc
  5. ▲ 2
    Deno 1.16 Released
    story by mattlondon · 2021-11-09 · 1 comment
  6. …API & basically laughed it out of the room as infeasible & worthless, on a number of dimensions. https://github.com/denoland/deno/issues/11018 So the web is in the worst possible spot. We have one API where we can do nothing for our users:…
  7. OP should have tested Deno ( https://github.com/denoland/deno ) too along side Node. Alas...
    comment by ignoramous · 2021-10-12 · in AWS Lambda Cold Start Times
  8. > V8 requires glibc I don't _think_ this is true. https://github.com/denoland/deno/issues/3711#issuecomment-62...
  9. …this work has never been brought into main (a couple of attempts have been made subsequently). https://github.com/denoland/deno/issues/3711#issuecomment-62...
  10. ▲ 2
    Deno v1.14.3
    story by 0xedb · 2021-10-05 · 0 comments
  11. …mode [^1] all of a sudden. Truck loads of eggs, or chickens depending on your view. [^1]: https://github.com/denoland/deno/issues/12295
    comment by justshowpost · 2021-10-03 · in Chicken and Egg Problem (2000)
  12. …wouldn't happen if it were written in something like Rust with a big focus on performance. [0] https://github.com/denoland/deno/issues/5432 [1] https://github.com/swc-project/swc/issues/571
    comment by fabiospampinato · 2021-09-21 · in Rome will be written in Rust
  13. …just paste into a file and run that file… Otherwise you might want to check out piping support https://github.com/denoland/deno/pull/6130 Something like `echo "yourcodehere" | deno run -`
    comment by justshowpost · 2021-09-17 · in Deno 1.14
  14. https://github.com/denoland/deno/discussions/11771 > NodeJS compatibility, what is our high-level strategy, goals, next steps? > Do we see Node and Deno co-existing, or do we want to think of Node as "legacy"? (Note, there was no clear…
    comment by up6w6 · 2021-09-16 · in Deno 1.14
  15. …on this thread how they eventually arrived at relying on Rust for most steps in the tsc toolchain: https://github.com/denoland/deno/issues/5432 The conclusion reached there is as you have stated: Rust is simply an order of magnitude faster…
    comment by SOLAR_FIELDS · 2021-09-02 · in Deno Deploy Beta 2
  16. Here's a gotcha for you: https://github.com/denoland/deno/issues/4568
    comment by ypcx · 2021-09-01 · in Deno Deploy Beta 2
  17. There's a few: https://github.com/denoland/deno/issues?q=is%3Aissue+is%3Aop...
    comment by ypcx · 2021-09-01 · in Deno Deploy Beta 2
  18. /tmp$ mkdir test /tmp$ cd test /tmp/test$ curl -sOL https://github.com/denoland/deno/releases/download/v1.13.1/deno-x86_64-unknown-linux-gnu.zip /tmp/test$ unzip deno-x86_64-unknown-linux-gnu.zip Archive: deno-x86_64-unknown-linux-gnu.zip…
    comment by skywal_l · 2021-08-23 · in Deno on MDN
  19. Yes, it seems like a very similar mistake to me: https://github.com/denoland/deno/issues/4574#issuecomment-62...
    comment by silasdavis · 2021-08-23 · in Deno on MDN
  20. …about Deno the more that I'm liking it. [1] https://deno.land/manual/linking_to_external_code [2] https://github.com/denoland/deno/discussions/11809#discussio...
    comment by andrew_ · 2021-08-23 · in Deno on MDN
  21. I think you might be interested in this open issue about public API for compiler. https://github.com/denoland/deno/issues/1739
    comment by searchableguy · 2021-08-10 · in Deno 1.13 Release
  22. …actually compiles the source code into V8 bytecode and bundles that with the Node binary [1]. [0] https://github.com/denoland/deno/issues/10507 [1] https://github.com/vercel/pkg
    comment by ksbrooksjr · 2021-08-10 · in Deno 1.13 Release
  23. ▲ 3
    Skip Type Checking by Default
    story by danpeddle · 2021-07-11 · 0 comments
  24. …out of the fetch spec and thus would to be implemented. It's also not clear from this issue either. https://github.com/denoland/deno/issues/3326
    comment by ledgerdev · 2021-05-12 · in Deno 1.10 Release Notes
  25. For context, this 11-month old github release < https://github.com/denoland/deno/releases/tag/v1.1.0 > is the Deno 1.1 release notes, not the linked post here which is for the 1.10 release notes.
    comment by Macha · 2021-05-12 · in Deno 1.10 Release Notes
  26. I gave it a whirl: > git clone https://github.com/denoland/deno.git denoland/deno > git clone https://github.com/denoland/rusty_v8.git denoland/rusty_v8 > cd denoland/deno > vi Cargo.toml ... [patch.crates-io] rusty_v8 = { path =…
    comment by CraigJPerry · 2021-05-12 · in Deno 1.10 Release Notes
  27. They're talking about deno, which _is_ written in Rust. https://github.com/denoland/deno
    comment by thegeekpirate · 2021-05-12 · in Deno 1.10 Release Notes
  28. …interactive permission prompt is still easily bypassed by nicely asking terminal to confirm it: https://github.com/denoland/deno/issues/9750#issuecomment-79... Direct link to asciinema: https://asciinema.org/a/9rvK8ANJK0WnQc9nsrFKdC7ir
    comment by goldsteinq · 2021-04-14 · in Deno 1.9
  29. …there's still a nasty bug with path mismatches between the LSP server and the VSCode extension ( https://github.com/denoland/deno/issues/9744 ) which requires reloading the window to fix spurious errors, but I'm sure it'll be fixed soon…
    comment by elisee · 2021-03-29 · in The Deno Company
  30. …Two random Rust projects: https://github.com/tokio-rs/tokio : $ grep -irn 'unwrap' | wc -l 1398 https://github.com/denoland/deno : $ grep -irn 'unwrap' | wc -l 2050 I dunno, but all Rust projects I have encountered had unwraps everywhere.
    comment by johnisgood · 2021-03-22 · in How Safe Is Zig?
  31. ▲ 1
    Release v1.8.2 · Denoland/Deno
    story by chovybizzass · 2021-03-22 · 0 comments
  32. Issue: https://github.com/denoland/deno/issues/9666
  33. As someone who's not a fan of JS in the browser, https://github.com/denoland/deno is _shockingly_ nice for "script-sized" tasks that need more performance than bash+jq makes easy.
  34. For anyone else curious, I believe Deno is a reference to https://github.com/denoland/deno please correct me though if that’s wrong
  35. ▲ 2
    Deno 1.6 lets you compile TypeScript to a single executable
    story by feross · 2020-12-10 · 0 comments
  36. …probably get away with wasm build of a C/C++ or Rust library if you don't mind getting dirty. 1. https://github.com/denoland/deno/issues/1891 edit: partial webcrypto/wasm option already available https://deno.land/x/god_crypto@v1.4.1
  37. ▲ 657
    Deno 1.6 supports compiling TypeScript to a single executable
    story by andyfleming · 2020-12-09 · 280 comments
  38. …I'm concluding that only by this very old thread; I'm not up-to-date with deno + could be wrong https://github.com/denoland/deno/issues/171
  39. …So for example this: (1000).toLocaleString(); will get you "1,000" with Node, but "1000" with Deno: https://github.com/denoland/deno/issues/1968
    comment by svnpenn · 2020-09-13 · in Deno 1.4
  40. The ticket for TLS support was closed in December ( https://github.com/denoland/deno/issues/1568 ) and there seems to be a lot of TLS support including esoteric use cases now.
    comment by fulafel · 2020-09-13 · in Deno 1.4
  41. …to go back from TypeScript to plain JavaScript. This is a very specific case, but it can happen: https://github.com/denoland/deno/pull/6793
    comment by anonova · 2020-08-20 · in TypeScript 4.0
  42. …the issues mentioned is that they ended up with duplicate independent Body classes in two locations https://github.com/denoland/deno/issues/4748 Then consolidate the two classes...? How is the the language's fault? > The internal code and…
    comment by underdeserver · 2020-06-21 · in Deno will stop using TypeScript
  43. ▲ 6
    Deno 1.1 Released
    story by anw · 2020-06-18 · 0 comments
  44. …compiler written in Rust[0][1], and `deno fmt` subcommand already uses it internally. [0] https://github.com/denoland/deno/issues/5432 [1] https://github.com/swc-project/swc
  45. …sub processes. They are also working on fine-grained permissions for these workers [1]. [1] https://github.com/denoland/deno/issues/4867
    comment by Pozzuh · 2020-06-04 · in What the Hell Is a Deno?
  46. Packaging to standalone executable is being worked on https://github.com/denoland/deno/issues/986
    comment by rahulete · 2020-06-04 · in What the Hell Is a Deno?
  47. https://github.com/denoland/deno/blob/9090023c33de7b64ae4142... Deno runs js in v8 and all syscalls go through the rust runtime. The limitations are pretty coarse (but i'd say a great start).
    comment by maxmcd · 2020-05-29 · in Deno Is a Browser for Code
  48. …lower memory footprints.." --- ¹ https://deno.land/manual/contributing/architecture#schematic... ² https://github.com/denoland/deno/blob/2610ceac20bc644c0b58bd... ³ Fine-Grained Sandboxing with V8 Isolates -…
    comment by lioeters · 2020-05-29 · in Deno Is a Browser for Code
  49. ▲ 1
    Deno v1.0.1 released with bug fixes and improvements
    story by vignesh_warar · 2020-05-20 · 0 comments
  50. The file system module's permissions are however still vulnerable to symlinks for example: https://github.com/denoland/deno/issues/2318
    comment by LunaSea · 2020-05-17 · in From Node to Deno