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

atom-pathspec

v0.0.0

Published

Translates pseudo-drives into absolute paths for Atom.

Downloads

484

Readme

atom-pathspec

A utility library for Atom for resolving relative links into special folders such as the installation directory or the user's home directory. This uses a special "pseudo drive" prefix on the directory to translate into an absolute path.

Prefix | Location -------------- | ------------------------------------------------ application: | The directory the application is installed into. home: | The current user's home directory. ~ | Same as home:. config: | The configuration folder. desktop: | The user's desktop. documents: | The user's documents (My Documents) folder. downloads: | The user's download folder. project: | Only used with getProjectPath(), gets the project root relative to the given buffer.

The above prefixes are case-insensitive and strip out dashes so APPDATA:, appdata: and app-data: all resolve to the application data directory. This is to make it more tolerant toward non-technical users entering data.

Any leading slashes (/) after the colon (or ~) will be stripped off and the remaining path will be treated as a file relative to that location. For example, on Unix, home:etc/dictionaries would resolve to $HOME/etc/dictionaries. home:/etc/dictionaries and home://etc/dictionaries resolve to the same path.

Absolute paths are passed in. If a relative path is given, either by prefixing with a ./ or not having a leading slash or drive, then relatively to the current working drive will be used.

API

getPath(spec) ⇒ string

Returns an absolute path from the given spec.

Param | Type | Description ----- | -------- | ------------ spec | string | A path specifier which may be an absolute, pseudo-drive, or relative path. |