If you are not using jpm, you can place the file path.janet from the repository in your current directory, and Janet will be able to import it as well.
Since the path repository has been archived, may be it's worth choosing another one for the example.
May be spork isn't a bad choice? Though I guess that's more than one file, so since the text near the end of what's quoted refers to a single file, updating it as well might be worth considering. However, doing that might lead to losing this valuable tip:
If you are not using jpm, you can place the file path.janet from the repository in your current directory, and Janet will be able to import it as well.
I looked around for a suitable single-file replacement that lived under janet-lang at github but came up empty-handed...
Currently in the Installing a module portion of the docs, there is the following:
...
Since the path repository has been archived, may be it's worth choosing another one for the example.
May be spork isn't a bad choice? Though I guess that's more than one file, so since the text near the end of what's quoted refers to a single file, updating it as well might be worth considering. However, doing that might lead to losing this valuable tip:
I looked around for a suitable single-file replacement that lived under janet-lang at github but came up empty-handed...