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

Deno 1.16 Release Notes

deno.com

Post reply on HN
Print view View original

11–14 of 14 posts

Re: Deno 1.16 Release Notes

#11

Post by Hamcha »

chaorace wrote: post #9

Personal anecdote: I've fallen in love with Deno as a scripting solution for my desktop machine. It is way more powerful than shell scripting while also being way more portable and clean than a Python or Node script ( assuming you end up using at least one dependency, a very common situation in Node ). I know someone's going to ask about permissions making the invocation process a pain, so here's my advice for that:…

Oh the shebang line is a really nice tip I didn't think about!

Something worth noting is that Deno also has permission APIs that let you query the current permission status and interactively ask for more: https://deno.land/manual/runtime/permission_apis#request-per...

Re: Deno 1.16 Release Notes

#12

Post by tpoacher »

chaorace wrote: post #9

Personal anecdote: I've fallen in love with Deno as a scripting solution for my desktop machine. It is way more powerful than shell scripting while also being way more portable and clean than a Python or Node script ( assuming you end up using at least one dependency, a very common situation in Node ). I know someone's going to ask about permissions making the invocation process a pain, so here's my advice for that:…

not sure what you mean by that. would you mind giving an example shebang line that does this?

Re: Deno 1.16 Release Notes

#13

Post by chaorace »

tpoacher wrote: post #12
chaorace wrote: post #9

Personal anecdote: I've fallen in love with Deno as a scripting solution for my desktop machine. It is way more powerful than shell scripting while also being way more portable and clean than a Python or Node script ( assuming you end up using at least one dependency, a very common situation in Node ). I know someone's going to ask about permissions making the invocation process a pain, so here's my advice for that:…

not sure what you mean by that. would you mind giving an example shebang line that does this?

Here you go! One example Deno script with permissions embedded in the shebang line:

  #!/usr/bin/env -S /usr/bin/deno run --allow-net=api.github.com
  const jsonResponse = await fetch("https://api.github.com/users/denoland");
  const jsonData = await jsonResponse.json();
  console.log(jsonData);

Re: Deno 1.16 Release Notes

#14

Post by tpoacher »

chaorace wrote: post #13
tpoacher wrote: post #12

Earlier quoted context omitted.

not sure what you mean by that. would you mind giving an example shebang line that does this?

Here you go! One example Deno script with permissions embedded in the shebang line: #!/usr/bin/env -S /usr/bin/deno run --allow-net=api.github.com const jsonResponse = await fetch("https://api.github.com/users/denoland"); const jsonData = await jsonResponse.json(); console.log(jsonData);

Ah, I thought you were referring to filesystem permissions, which confused me!

This makes sense. Thanks!

Post reply on HN