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

@lbatchelor/netlify-cli

v1.2.2-patched.9

Published

Netlify builds, deploys and hosts your front-end straight from Github.

Downloads

4

Readme

Netlify CLI

The Netlify CLI tools lets you create, deploy, and delete new sites straight from your terminal.


Why does this fork exist?

This fork exists due to errors we are getting when using the normal client. Some times the permalink we get back doesn't actually work. This fork simply fetches that url a second time to ensure that we are logging the correct one.

It also adds the ability to set a WRITE_PERMALINK_TO_FILE environment variable to write the url to a file as well.

WRITE_PERMALINK_TO_FILE="permalink.txt" yarn netlify-patched -t $NETLIFY_TOKEN deploy --site-id $NETLIFY_SITE_ID_STAGING -p dist.zip

Installation

To install the CLI tools:

npm install netlify-cli -g

Usage

Deploy a front-end project that lives in my-project and builds to dist directory:

cd my-project/
netlify deploy dist

Configuration and Authentication

The first time you use the netlify cli command you'll be asked to authenticate.

Your access token is stored in ~/.netlify/config.

Netlify also stores a local .netlify file in the folder where you run netlify deploy from where the site_id is stored.

Environments

You can easily setup different environments like staging or production. Just use the -e flag:

netlify deploy dist -e production

Netlify creates different sites with each their own URL for each of your environments and keeps track of them in the .netlify config file.

Caveats

  • netlify-cli is known to hang with an "ECONNRESET" error (parsed as JSON, it will look odd) when used from many CI environments. This is a known issue that is only fixed in our alternate and current CLI: https://github.com/netlify/netlifyctl

  • netlify-cli is known to hang when used with Node.js version 8.1.0. Version 8.1.2 works well