Currently /foo means exactly that. The file called "foo" in the root of the filesystem. This is different to how the npm files array works, which "re-roots" absolute paths on-top of the current package (in other words, it ignores the leading slash). We should work the same way, since it's currently a big footgun.
One special case is that for input files, we do want to support selecting files outside of the current package. So we should still support ../.
Output files can't currently support ../ because of the way we copy output to the .wireit/<script>/cache folder. We could support it by representing local cache differently (e.g. with a tarball).
Currently
/foomeans exactly that. The file called "foo" in the root of the filesystem. This is different to how the npmfilesarray works, which "re-roots" absolute paths on-top of the current package (in other words, it ignores the leading slash). We should work the same way, since it's currently a big footgun.One special case is that for input files, we do want to support selecting files outside of the current package. So we should still support
../.Output files can't currently support
../because of the way we copy output to the.wireit/<script>/cachefolder. We could support it by representing local cache differently (e.g. with a tarball).