Right now, every time npx runs, it removes all binaries from a single,
shared binary directory. This works fine in isolation, but if there's a long-running pipeline, it can cause odd errors. For example, in npx foo | npx bar | npx baz, each successive npx call would blow away the bin directory before executing the next command. If everything a command from that bin dir is already loaded into memory on execution, that's fine -- but some required binaries for later stuff might end up getting removed.
npx should have a better model for this, and, ideally, it'll also facilitate faster re-runs.
Right now, every time npx runs, it removes all binaries from a single, shared binary directory. This works fine in isolation, but if there's a long-running pipeline, it can cause odd errors. For example, in
npx foo | npx bar | npx baz, each successivenpxcall would blow away thebindirectory before executing the next command. If everything a command from that bin dir is already loaded into memory on execution, that's fine -- but some required binaries for later stuff might end up getting removed.npx should have a better model for this, and, ideally, it'll also facilitate faster re-runs.