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

bower-path-data

v0.1.0

Published

Get information on bower related paths and directory names.

Downloads

3

Readme

bower-path-data

Get information on bower related paths and directory names.

Installation

npm install bower-path-data

Usage

path/to/app/.bowerrc

{
  "directory": "../../../.tmp/assets/bower_stuff"
}

path/to/app/assets/bower.json

{
  // ...
  // JSON file contents don't matter, they are not checked. The existance of the
  // file is all that matters for the purposes of path data.
  // ...
}
const bowerPathData = require('bower-path-data');

var pathInfo =  bowerPathData.sync('path/to/app/assets');
// pathInfo => {
//   componentsDir: '.tmp/assets/bower_stuff',
//   componentsDirName: 'bower_stuff',
//   jsonDir: 'path/to/app/assets',
//   rcDir: 'path/to/app'
// }

API

bowerPathData()

Does nothing / placeholder for an async method.

bowerPathData.sync(startPath)

Returns an object containing bower path and directory name information, if available. Any values that could not be found will be returned with a value of null.

startPath

Type: String

A path to the directory to start looking for bower.json in.

If not found, ancestor directories will be searched until a match is found (using find-up) or the volume root is reached. From bower.json's location, .bowerrc will be searched for in the same way.

If .bowerrc is found, then bower-config will be used to read the configuration.

  • If the directory property is a string, then the component directory path will be the result of running the rc file's path and the directory property through node's path.join method.
  • Otherwise, the component directory path will be the result of running json file's path and the string bower_components through path.join().

The component directory name will then be retrieved from the component directory path.