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

@staticdeploy/cli

v0.15.5

Published

CLI tool for StaticDeploy

Downloads

997

Readme

@staticdeploy/cli

CLI tool to create and deploy bundles.

Install

npm i -g @staticdeploy/cli

Use

  • staticdeploy bundle: creates a bundle and uploads it to the StaticDeploy server. Options:

    • --config (optional): specify the file from which to load options. Defaults to staticdeploy.config.js
    • --apiUrl: URL of the StaticDeploy management API
    • --apiToken: authentication token for the management API
    • --from: path of the directory to create the bundle from
    • --name: name of the bundle
    • --tag: tag of the bundle
    • --description: description of the bundle
    • --fallbackAssetPath (optional): absolute path (relative to the from directory) of the asset to use as fallback when requests don't match any other asset. Defaults to /index.html, but the asset MUST exist
    • --fallbackStatusCode (optional): status code to use when serving the fallback asset. Defaults to 200
    • --headers (optional): (asset matcher, headers) map specifying which headers to assign to which assets
  • staticdeploy deploy: deploys a bundle to an entrypoint. Options (all required):

    • --config (optional): specify the file from which to load options. Defaults to staticdeploy.config.js
    • --apiUrl: URL of the StaticDeploy API
    • --apiToken: authentication token for the API
    • --bundle: name:tag combination of the bundle to deploy
    • --entrypoint: urlMatcher of the entrypoint to deploy to
    • --app: name of the app the entrypoint links to

A valid config file has the following structure:

module.exports = {
  // Optional
  bundle: {
    // Options for the bundle command as specified above
  },
  // Optional
  deploy: {
    // Options for the deploy command as specified above
  }
};

Options can also be passed as upper-cased, snake-cased, environment variables prefixed by STATICDEPLOY_. Eg:

export STATICDEPLOY_API_URL=...
export STATICDEPLOY_API_TOKEN=...

Option sources have the following priority:

  1. command line flags
  2. environment variables
  3. configuration defined in the config file

Meaning for example that when an option is provided both as a command line flag and as an environment variable, the value provided with the command line flag is used.