cli-cwd
Advanced tools
Readme
Runs specified command with modified CWD, redirecting all stdio in the correct way (i.e. you can pipe or redirect stdin/stdout/stderr).
The package installs cwd command with the following signature:
cwd <directory> -- <command> [arg]...
$ cwd /usr/bin -- pwd
/usr/bin
$ cwd /usr/bin -- ls |ack '^zip'
zip
zipcloak
zipgrep
zipinfo
zipnote
zipsplit
More realistic example — universally operate on directories no-matter-what-flag-tool-authors-have-chosen-to-use.
$ cwd ./dir -- tar cvaf ../dir.tbz2 .
$ cwd ./dir -- zip -r ../dir .
$ cwd ./dir -- 7z a ../dir . -tzip
In all of these cases files are saved with file names relative to ./dir.
Usage: cwd <directory> -- <command> [arg]...
Well, there is an API, but you should definitely use Node's own child_process.exec instead. Take a look at index.js if you are not convinced.
npm install -g cli-cwd
MIT
FAQs
Run command with modified CWD (current working directory)
The npm package cli-cwd receives a total of 1 weekly downloads. As such, cli-cwd popularity was classified as not popular.
We found that cli-cwd demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The US Justice Department has penalized two consulting firms $11.3 million for failing to meet cybersecurity requirements on federally funded projects, emphasizing strict enforcement to protect sensitive government data.
Security News
ua-parser-js is set to drop the MIT license and adopt a controversial dual AGPLv3 + PRO licensing model in its upcoming v2.0 release, raising significant concerns among developers and enterprise users.
Security News
Researchers recently demonstrated that the npm Registry is vulnerable to cache poisoning combined with DoS, posing significant risks for package availability.