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

glitch-static-build-cache

v1.0.0

Published

Cache your static builds on Glitch to avoid longer startup times

Downloads

4

Readme

Glitch-Static-Build-Cache

NodeJS CI Passing Status Badge Code Coverage Badge GitHub tag (latest SemVer) NPM Badge

Easy to use CLI command to get Glitch to re-use past builds if nothing has changed, for projects that build a static site output.

This is really just a wrapper around my other package, static-build-cache.

Installation

Install how you would normally install packages. If you are on Glitch, see these instructions.

Usage

Usage pretty much mirrors static-build-cache. The only extra options are currently:

Option (CLI) | Option (JS) | Default | Description --- | --- | --- | --- --skipDetection | skipDetection | false | Skip is "is on glitch" detection, and always treat as if it is. --bailOnNonGlitch | bailOnNonGlitch | false | If this is run outside of Glitch, would you like the program to bail with an error? If so, it will prevent chained commands from running.

Usage Example

Package.json before using:

{
	"scripts": {
		"start": "react-scripts start",
		"build": "react-scripts build",
		"test": "react-scripts test",
		"eject": "react-scripts eject"
	}
}

After:

{
	"scripts": {
		"start": "glitch-cache && react-scripts start",
		"build": "react-scripts build",
		"test": "react-scripts test",
		"eject": "react-scripts eject"
	}
}

With the above config, the same project on Glitch can be executed locally as well; on Glitch it will build and serve, but locally it will just run the next command react-scripts start.

Development

Change Notes

Version | Date | Notes --- | --- | --- v1.0.0 | 09/16/2020 | Initial Release 🚀

Known Issues

Uptime, package re-installs, and container resets are a bit of a grey area with Glitch; there are some known issues and undocumented behaviors. In the case that your container experiences a reset, where packages are re-installed, you might find that using this tool barely reduces your startup time.

Unfortunately, in those instances, there is not much I can do to improve things, besides suggesting that you pay to upgrade to a boosted Glitch plan.

About Me

  • 🔗joshuatz.com
  • 💬@1joshuatz
  • 💾github.com/joshuatz