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

@wfh/prebuild

v1.0.47-4

Published

Work with Plink, prebuild command line tool for monorepo based project

Downloads

2

Readme

Have trouble with wring bash shell ? quick read https://ryanstutorials.net/bash-scripting-tutorial/bash-if-statements.php

Design

Features

  1. Support monorepo, a repo contains multiple projects with different release schedule.
  2. For DevOps or admin developer
  3. Build out static resource (client side JS, CSS files) as zip for deploy
    • Also Store static resource together with Node server
  4. Build out Node server for image deployment service(e.g. for K8s)
  5. Build/deploy accepts 2 configuration parameters: environment, project name
  6. Can dynamically push static resource to Node.js file server
  7. Repo may provide customized static resource build scripts

Prebuild scripts

  1. Clean and build static resource and compile server side scripts, then deploy to the remote file server (maybe CDN) and push to git branch master, deploy-test or release
bash scripts/prebuild/prebuild.sh <environment> <product-config-name> <true|false>

<true|false> meaning whether the build only contains static resource and whether Node.js deployment is not required

  1. Only clean and build static resource and compile server side scripts, do not deploy to remote file server, do not push to any remote git branch
bash scripts/prebuild/prebuild-all.sh <environment> <product-config-name> <true|false>
  1. Deploying existing static resource which was built previously by prebuild-all.sh or a failed prebuild.sh to remote file server and push to the remote git branch.
bash scripts/prebuild/prebuild-post.sh <environment> <product-config-name> <true|false>
  1. Only deploying directory or zip file to the remote file server
bash scripts/prebuild/remote-deploy.sh <environment> <product-config-name> <zip-file or directory>