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

path-resolver

v0.0.2

Published

returns a valid filesystem path.

Downloads

3,992

Readme

path-resolver

returns a valid filesystem path.

What?

this is a really insanely simple module to do path normalization, and existence checking. How simple? <30 lines of coffeescript.

How?

npm install path-resolver and then require('path-resolver').<method> where method is guess,sync, or async.

Examples

sync check (existential checking is done, in sync)

if ((path = require('path-resolver').sync("/path/to/file.ext")) != false)
  console.log("valid path given: "+path);

async check (existential checking is done, async [needs callback])

require('path-resolver').async("/path/to/file.ext",function(path){
  if (path != false)
    console.log("valid path given: "+path);
  else
    console.log("bad path!");
});

and guess check (no existential checks done)

if ((path = require('path-resolver').guess("/path/to/file.ext")) != false)
  console.log("probably valid path given (syntax is correct): "+path);

A bit more info...

so a sync check uses fs.existsSync whereas async uses fs.exists. guess does check at all, just syntax verifies the path. if any of these methods return false, the path syntax was invalid, or (if using sync or async) the path doesn't exist in the filesystem.