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

parcel-finder

v0.2.3

Published

recursively detect whether a directory with a package.json is parcel

Downloads

5

Readme

parcel-finder

recursively detect whether a directory with a package.json is a parcel

build status

parcels

A parcel is a convention for defining a front-end asset management structure.

A parcel MUST have:

  • a "view" field in package.json

A parcel MAY have:

  • a "main" field
  • static asset globs that may be read by parcel-map

example

Suppose we have 3 directories in views/: page1, page2, and page3.

views/page1 is a valid parcel because its package.json has a view field:

{
  "view": "view.html",
  "main": "main.js"
}

views/page2 is a also valid parcel because its package.json has a view field:

{
  "view": "render.jade"
}

views/page2/sub is a valid parcel that is nested inside of views/page2:

{
  "view": "beep.html"
}

views/page3 is not a valid parcel because it does not have a "view" field:

{
  "name": "not a parcel"
}

Running parcel-finder on this directory structure with this finder:

var detect = require('parcel-finder');
detect(__dirname + '/views', function (err, parcels) {
    console.log(JSON.stringify(parcels, null, 2));
});

gives this output:

{
  "/home/substack/projects/parcel-finder/example/views/page1/package.json": {
    "view": "view.html",
    "main": "main.js"
  },
  "/home/substack/projects/parcel-finder/example/views/page2/package.json": {
    "view": "render.jade"
  },
  "/home/substack/projects/parcel-finder/example/views/page2/sub/package.json": {
    "view": "beep.html"
  }
}

methods

var detect = require('parcel-finder')

detect(opts, cb)

Resolve the directory starting at opts.dir recursively to find parcels. cb(err, parcels) is called when the detection is complete with a map of package.json paths to package.json contents for package.jsons that are determined to be parcels.

If opts is a string, treat the string as the opts.dir.

install

With npm do:

npm install parcel-finder

license

MIT