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

angelscripts-stack-use

v0.1.4

Published

Manage current working project's stack

Downloads

24

Readme

angel-stack-use v0.1.4

Manage current working project's stack

usage

install

$ npm install angelscripts-stack-use

$ angel stack use

Applies stack upgrade within cwd.

$ angel stack use {remote} {updatePath} {branch}

arguments

  • remote - optional, git repo url or name of stack upgrade
  • updatePath - relative path to either remote or current working directory
  • branch - optional, used with git remote to specify remote's source code branch

logic behind

  1. read upgrade.json(upgrade) from stack upgrade root folder (stackRootFolder)
  • upgrade.main - pointer to relative directory containing the upgrade files, default ''
  • upgrade.name - name of the upgrade
  • upgrade.version - version of the upgrade
  • upgrade.dependencies - key value pairs of name: version
  • upgrade.peerUpgrades - key value pairs of name: relativePath
  1. upgrade.depencencies should be present as key in stack-upgrades within package.json
  2. apply stack upgrade - copy recursively all files from stackRootFolder + upgrade.main where:
  • .json files are deep merged
  • .gitignore files are rewritten only with the unique lines
  • any other file is overridden
  1. apply stack upgrade peers - use the same method as within step 3) for every upgrade.peerUpgrades match towards stack-upgrades hash from package.json
  2. store within package.json's stack-upgrades hash the applied upgrade {name: version}

$ angel stack list

List available stack upgrades within cwd.

$ angel stack list

$ angel stack configure

Prompt once for unique {{{placeholders}}} within files at cwd and replace them with provided values.

$ angel stack configure

how to create stack upgrade

  1. create a standard npm package as my-stack-upgrade
  2. place upgrade.json there
  3. have fun && $ mkdir ../my-upgraded-app && cd ../my-upgraded-app && angel stack use ../my-stack-upgrade