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

@heroku/update-node-build-script

v1.0.3

Published

A one-time migration tool to help you get your builds running on Heroku with a single command

Downloads

27

Readme

@heroku/update-node-build-script

oclif Version

Summary

You will need to make sure you are in your application's root directory, then run:

$ npx @heroku/update-node-build-script

Why?

To make getting started with Node.js on Heroku easier we will begin executing the build script by default if it is defined in your package.json. This change will go live on Monday, March 11, 2019. Read more about this change in our FAQ.

For users with an existing build script that they may not want run during the build, this will require some slight modifications to their package.json. The modifications are simple and mechanical, and this CLI tool will make updating as easy as possible.

screenshot of the CLI tool working

Usage

You will need to make sure you are in your application's root directory, then run:

$ npx @heroku/update-node-build-script

npx is a tool that comes with the modern verions of npm bundled with Node. If for some reason, npx is not available on your system, you can install it with the following command:

$ npm install -g npx

or download and run this package directly:

$ cd $APP_DIRECTORY
$ npm install -g @heroku/update-node-build-script
$ update-node-build-script

and then you can uninstall it when you are finished:

$ npm uninstall -g @heroku/update-node-build-script

What does this command do?

When it runs it will inspect the contents of your package.json file, note which scripts you have defined, and suggest a modification that will opt you in to the new build rules while maintaining your existing build behavior.

It will make no changes without your explicit approval.

screenshot of the CLI tool working

Feel free to inspect the source of this tool.

I don't want to run an npx command on my system

No problem! This tool is provided only as a convenience. The changes are documented in this FAQ and are simple to perform manually.