npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

win-path

v0.2.0

Published

Manipulate a Windows machine's PATH from Node.js.

Downloads

5

Readme

win-path

Manipulate a Windows machine's PATH from Node.js.

Installation

npm install win-path

Quickstart


const path = require('win-path')

// get the machine's PATH variable
path.get()
    .then(console.log)
    // => C:\rainbow;C:\unicorn

const dir = 'C:\\kittens'

// check whether dir is already in PATH
path.has(dir)
    .then(console.log)
    // => false

// add dir to the PATH
path.add(dir)
    .then(console.log)
    // => C:\rainbow;C:\unicorn;C:\kittens

// remove dir from the PATH
path.remove(dir)
    .then(console.log)
    // => C:\rainbow;C:\unicorn

API

  • dir should be a non-empty string with the path.sep being \\. The dir parameter is optional; the default value is process.cwd().

  • target must be one of ['process', 'machine', 'user']. If it is not, the returned Promise will reject with INVALID_TARGET. The target parameter is optional; the default value is process.

path.get([target])

  • Resolves with the machine's current PATH variable.

path.has([dir, target])

  • Resolves with true or false depending on whether the specified directory is in the PATH or not.

path.add([dir, target])

  • Adds the specified directory to the PATH variable and returns the new PATH.
  • Resolves with WARN_DIR_ALREADY_IN_PATH if the directory is already in the PATH.
  • Resolves with ERR_SECURITY_EXCEPTION if adding the directory to the PATH failed due to security reasons (e.g. non-elevated process).

path.remove([dir, target])

  • Removes the specified directory from the PATH variable and returns the new PATH.
  • Resolves with WARN_DIR_NOT_IN_PATH if the directory is not present in the PATH.
  • Resolves with ERR_SECURITY_EXCEPTION if removing the directory from the PATH failed due to security reasons (e.g. non-elevated process).

Notes

  • This module is based on the Powershell scripts in the /scripts directory. Therefore, to be able to use it in the first place, Powershell must be in the PATH (which it is by default on a new Windows machine).
  • Internally, the Powershell scripts use [System.Environment]::GetEnvironmentVariable('path', target).

License

WTFPL – Do What the F*ck You Want to Public License.

Made with :heart: by @MarkTiedemann.