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

gh-pages-auto-release

v1.1.369

Published

This node module will help you to publish your package to dist folder as a github page.

Downloads

412

Readme

gh-pages-auto-release

This node module will help you to publish your package to dist folder as a github page.

All you have to do is run gh-pages-auto-release in your release script

{
  "name": "package-name",
  "version": "1.0.0",
  "scripts": {
    "build": ":", 
    "test": ":",
    "release": "gh-pages-auto-release",
  },
  "devDependencies": {
    "gh-pages-auto-release": "*"
  }
}

The --git-repo option

By default pages output of your project is pushed to a branch on its own repository (designated by the GIT_REMOTE_URL environment variable). You can change this by pointing to a different repository using the --git-repo option.

For example: gh-pages-auto-release --git-repo [email protected]:wix/my-library-gh-pages

This option is typically used on monorepos that have multiple projects with gh pages. Since github design dictates one-to-one relationship between published pages and the git repository, you should create a separate repository for publishing and pass it using this option.

Your page is automatically re-published every CI build

Once you're build is complete in CI, your page can be accessed at:

https://wix.github.io/package-name/

where package-name is the name you gave your git repository

obvious note: This url will work only if you have dist/index.html file generated by your build.