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

@foresightyj/lazy-git

v1.0.4

Published

This command helps in case where you do not want to run a time-consuming command (e.g. a webpack build which takes a few minutes) if git repository does not have new commits.

Downloads

1

Readme

This command helps in case where you do not want to run a time-consuming command (e.g. a webpack build which takes a few minutes) if git repository does not have new commits.

Usage is pretty similar to cross-env, simply prefix your actual command with lazy-git, e.g.

cross-env NODE_ENV=production lazy-git webpack --config webpack.prod.js

The first time it runs

$ npm run build:prod
> cross-env NODE_ENV=production lazy-git webpack --config webpack.prod.js

.lazy-git does not exist. It will be made after a successful run.
...
...
webpack 5.37.1 compiled with 2 warnings in 38225 ms
Successfully ran: `webpack --config webpack.prod.js`. Save the corresponding commit hash: 23240f7 style change to .lazy-git

The second time it runs (assuming no new commits):

$ npm run build:prod
> cross-env NODE_ENV=production lazy-git webpack --config webpack.prod.js

Command: `webpack --config webpack.prod.js` is SKIPPED because .lazy-git already has last commit: `23240f7 style change`
To re-run the command, simply delete the file: `D:\Working\FHT.CMS.Web\fht-cms-web-client\.lazy-git` and then retry.

Later, if new commits detected:

/d/Working/FHT.CMS.Web/fht-cms-web-client $ npm run build:prod

cross-env NODE_ENV=production lazy-git webpack --config webpack.prod.js

New commit detected: d2d2506 applied lazy-git ... ... webpack 5.37.1 compiled with 2 warnings in 38496 ms Successfully ran: webpack --config webpack.prod.js. Save the corresponding commit hash: d2d2506 applied lazy-git to .lazy-git ...