Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Wanted: installer #471
a program which installs itself into your $PATH. It will walk your $PATH, find a writable directory, writing a new shell script into it called
The shell script will look like this:
#!/bin/sh deno run -A https://deno.land/std/installer/bin.ts $@
So now people can run this:
This will create a new executable shell script called
#!/bin/sh deno run --allow-write --allow-net https://deno.land/std/http/file_server.ts $@
Should we select first writeable dir? How about keeping it all in one place and using
Also we should take a moment to figure out how to go about updating and/or reloading of installed scripts
Usage of denoget:
This command creates files below:
If you add ~/.deno/denoget/bin into $PATH, you can execute file_server directly.
The reason why denoget uses wget is to read shebang of target script.
#!/usr/bin/env deno --allow-all
deno's fetch doesn't support redirect, so I couldn't read shebang from script using redirect server like
I'm okay to remove this feature if I would add denoget into std.
In Go's way,
These behaviors may be helpful to decide command name ;)
I think 1) can be skipped and included directly in 2)
We can automate it
Can you elaborate? Won't
@syumai let's get PR going and iterate in there, I'll help out
Yes, this can be
Maybe what I should try is to implement feature of this TODO comment.
Thanks! I'm going to start doing it this week ;)
What I'm going to do:
Is this ok? If it is, I start doing it. @bartlomieju