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

build-message

v1.0.0

Published

Build message banner, intended for information messages during multi stage builds.

Downloads

5

Readme

build-message

Build message banner for information messages during multi stage builds.

Table of Contents

Description

Use build-message when you have a multistep build and want to be able to quickly identify the current build step or some other important information in long logs. The message that you log using build-message is formatted with a 4 character prefix spacing and a dashed line 8 characters longer than the message. Like this:

If the message is really long, the terminal width will be the max width, or 80 characters if the terminal width isn't discoverable. The build message will be split (if possible on spaces) at a relevant position. If possible build-message tries to insert 4 spaces before the text, but will accomodate to the available space.

Example with 16 character width terminal:

Installation

Intended to install in the root package of a monorepo.

npm install build-message --save-dev

or

yarn add -D build-message

Usage

The standard usage is to use in a "pre" or "post" npm script. see: https://docs.npmjs.com/cli/v8/using-npm/scripts#pre--post-scripts

Here's some standard package.json examples:

yarn+CRA

"prebuild": "yarn build-message building client",
"build": "react-scripts build",

npm+rollup

"prebuild": "npm build-message building library x",
"build": "rollup",

CLI

The build-message tool can be used from the cli for testing it's functionality.

CLI Useage

$ build-message <message> | [options]

$ scopy --help
$ scopy -v
  • message The message that you want logged in a banner format.
  • [options]
    • -v , --version Print version and quit.
    • -h , --help Print help and quit

CLI Examples

Examples :

$ build-message building main
---------------------
    building main
---------------------

$ build-message debug build
-------------------
    debug build
-------------------