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

@futagoza/publish-package

v1.6.0

Published

A 'npm/yarn publish' wrapper with my preferred defaults.

Downloads

704

Readme

A 'npm/yarn publish' API wrapper with my preferred defaults that returns a promise.

  • api based, so you can call from your scripts, but spawns the actual commands
  • run either Yarn (option.yarn = true) or NPM (default)
  • perfect for embedding into your build scripts (Gulp anyone?)
  • --access public by default (publishing scoped packages is simpler)
  • optionally checks if package version is already on NPM

example

const publish = require( "@futagoza/publish-package" );

publish( __dirname, { checkVersion: true } )
    .catch( details => {

        console.error( details.stderr );
        process.exit( 1 );

    } )
    .then( () => console.log( "Yahoo!" ) );

options

function publish( path?: string, options: {} ): Promise;

| api option | npm/yarn cli option | description | | ---------- | ------------------- | ---------------- | | access | --access scope | See https://docs.npmjs.com/cli/publish | | checkVersion | | Will check on NPM before publishing | | dir | | Alternative to the path argument1 | | dry-run | --dry-run | See https://docs.npmjs.com/cli/publish | | dry | --dry-run | Alias for dry-run | | dryRun | --dry-run | Alias for dry-run | | folder | | Alternative to the path argument1 | | log | | An optional logging function2 | | new-version | --new-version value | See https://yarnpkg.com/lang/en/docs/cli/publish/ | | newVersion | --new-version value | Alias for new-version | | otp | --otp value | See https://docs.npmjs.com/cli/publish | | otpcode | --otp value | Alias for otp | | path | | Alternative to the path argument1 | | private | --access restricted | If true, uses --access restricted | | public | --access public | If true, uses --access public (default) | | scoped | --access public | If true, uses --access public | | registry | --registry url | See https://docs.npmjs.com/misc/registry | | reg | --registry url | Alias for registry | | restricted | --access restricted | If true, uses --access restricted | | runOpts | | Option's to send to @futagoza/node-run | | tag | --tag name | See https://docs.npmjs.com/cli/publish | | version | --new-version value | Alias for new-version | | yarn | | Will use yarn publish instead of npm publish |

  1. Can be used in place of path (e.g. publish( { dir: ... } ))
  2. Check defaultLogger in @futagoza/gulp-publish-package/index.js for an example

NOTE: To circumvent an issue with running npm publish from a yarn run ... command, the registry option is set to https://registry.npmjs.org/ by default when running npm publish only, otherwise it is only included when specified.


History license

@futagoza/publish-package is Copyright (c) 2018+ Futago-za Ryuu