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

@pie-cli-libs/installer

v1.5.4

Published

installer for pie elements

Downloads

102

Readme

installer

For installing dependencies of a pie item.

build

npm run build

test

npm test # unit tests
npm run integration-test # this is disabled for now. instead run: 
./node_modules/.bin/jest --config jest.config.int.js

publish

See the main readme.

Item Configuration

A pie item will have the following configuration:

{
  /** 
    * elements is a mapping between a custom element name and it's package.
    * on the left side is the name of the custom element that'll be used.
    * on the right side is the npm style dependency look up.
    * > NOTE: The npm package name does not need to match the element name, they'll be associated with each other.
    */

  elements: {
    'el-one': '../..', //where ../.. is an npm package called located 2 directories above
    'el-two': '^1.0.0', //looks for an npm package called 'el-two'
    'el-three': '@scope/name@^2.0.1' //looks for an npm package '@scope/name@^2.0.1`
    'el-four': 'user/repo#v2.0.0' // github repo
  },
  models: [
    { id: '1', element: 'el-one', ...}
  ]
}

Using the above pie item definition, install will install the dependencies needed and will return information on the installation.

The installation directory will look like so:

root
├── .configure   
│   ├── node_modules # configure dependencies in here
│   └── package.json
├── .controllers
│   ├── node_modules # controller dependencies in here
│   └── package.json
├── node_modules # player dependencies in here
└── package.json

It'll return an array of objects similar to:

{
  "element": "text-entry",
  "isLocal": true,
  "isPackage": true,
  "main": {
    "dir": "/Users/edeustace/dev/github/PieElements/pie-elements/packages/text-entry/docs/demo/.pie",
    "moduleId": "@pie-elements/text-entry",
    "tag": "text-entry"
  },
  "src": "../..",
  "controller": {
    "dir": "/Users/edeustace/dev/github/PieElements/pie-elements/packages/text-entry/docs/demo/.pie/.controller",
    "moduleId": "@pie-elements/text-entry-controller"
  },
  "configure": {
    "dir": "/Users/edeustace/dev/github/PieElements/pie-elements/packages/text-entry/docs/demo/.pie/.configurue",
    "moduleId": "@pie-elements/text-entry-configure",
    "tag": "text-entry-configure"
  }
}