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 🙏

© 2026 – Pkg Stats / Ryan Hefner

enduraweb

v0.1.0

Published

Deploy to EnduraWeb from the command line

Readme

enduraweb

Deploy to EnduraWeb from the command line.

Install

npm install -g enduraweb

(Before this is published, run it from the repo with npm run dev --workspace=enduraweb -- <command>, or npm run build:cli once and use node packages/cli/dist/index.js.)

Usage

# 1. Authenticate — paste a token created from Dashboard → Security → API tokens
enduraweb login

# 2. From your project's root:
enduraweb init          # create a new EnduraWeb project and link this folder to it
# — or, for an existing project —
enduraweb link          # link this folder to one of your existing projects

# 3. Ship a new version any time
enduraweb deploy        # aliases: enduraweb upload, enduraweb newbuild

Every deploy zips the current folder, uploads it, and runs it through the same sandboxed install/build pipeline as a dashboard upload — install scripts are blocked (--ignore-scripts) the same way, and each upload becomes its own numbered build automatically, exactly like a new commit.

Other commands:

enduraweb projects      # list your projects and their status
enduraweb whoami        # show which account you're logged in as
enduraweb logout        # forget the stored token

What gets uploaded

enduraweb deploy reads .gitignore if present (so what deploys matches what's version-controlled) plus an optional .endurawebignore for anything that should be excluded from a deploy specifically — e.g. a committed dist/ you don't want re-uploaded on top of a fresh server-side build. node_modules, .git, and .enduraweb are always excluded regardless of either file, since dependencies are reinstalled server-side.

.endurawebignore uses the same syntax as .gitignore:

# .endurawebignore
*.local.json
tmp/

Config

  • enduraweb login writes ~/.enduraweb/config.json (token + API URL), created with 0600 permissions.
  • enduraweb init / enduraweb link write .enduraweb/project.json in the current folder (which project it deploys to) and add .enduraweb/ to that folder's .gitignore if it's a git repo.
  • Self-hosting EnduraWeb elsewhere? Point the CLI at it with enduraweb login --api-url https://your-api-host, or set ENDURAWEB_API_URL in the environment.