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

@abernier/create-sandbox

v1.0.5

Published

[![NPM version](https://img.shields.io/npm/v/@abernier/create-sandbox.svg?style=flat)](https://www.npmjs.com/package/@abernier/create-sandbox)

Downloads

20

Readme

NPM version

It's codesandox but as a local command-line!

Command to create a standard CRA, but:

  • with a random project-name (if no-one given)
  • launch VScode automatically on src/App.js
  • choose a random port between [3000..4000] to launch the localhost hot-reload server

Usage

The following command will create a new random-name-2345 project into .

$ npm init @abernier/sandbox

or

$ yarn create @abernier/sandbox

Alternative usage

Specify a existing folder

$ npm init @abernier/sandbox ~/tmp

A random-name-2345 will be created inside ~/tmp and your CRA created into.

Specify a non-existing folder

$ npm init @abernier/sandbox ~/code/rosie

A rosie folder will be created and your CRA created into.

NB: no random name here as you specify a non-existing folder name

npx

Alternatively to you could just:

$ npx @abernier/create-sandbox

but this is less cool

Publish to NPM

Ready to publish a new version to NPM registry?

Manually

  1. bump the package.json version
  2. npm login if not already
  3. npm publish

If successful, you should want to tag the version:

$ git add package.json
$ git commit -m "bump version"
$ git tag v1.0.1
$ git push --tags

Using CI workflow

Pre-requisite:

  1. Generate a new NPM access token on npmjs.com (you need a NPM account and be logged-in)
  2. Set it as NPM_TOKEN secret (in Settings > Secrets and as referenced into ci.yml file)

Then, to release a new version on npm:

  1. bump the package.json version
  2. then, create a new realese and wait for the ci publish it :)