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

rocket-punch

v4.0.0

Published

![TEST](https://github.com/rocket-hangar/rocket-punch/workflows/TEST/badge.svg) ![E2E](https://github.com/rocket-hangar/rocket-punch/workflows/E2E/badge.svg) [![codecov](https://codecov.io/gh/rocket-hangar/rocket-punch/branch/master/graph/badge.svg)](http

Downloads

31

Readme

🚀 Rocket Punch! 🥊

TEST E2E codecov devDependencies Status

Rocket-Punch is a tool for creating and publishing directories in a project into NPM packages.

Usually, we use Monorepo to make and publish part of the project as a package, but the use of Monorepo is cumbersome. (Many Config files that occur per package, such as Watch with Transpilers such as TypeScript...)

Rocket-Punch packages and distributes some of the directories inside the project /src directory to NPM without cumbersome settings.

How does it work?

  1. If there are directories @myorg/package-a, @myorg/package-b, and package-c within the directory /src
  2. The rocket-punch build command creates packages in the out/packages directory.
  3. The rocket-punch publish command then publish packages from the out/pckages directory collectively to the NPM.

Basic usage

It's a simple setting.

cd your-project-root
npx rocket-punch-init

A .package.json, .packages.json files are created in the project.

build-packgaes and publish-packages would have been created in scripts in the package.json file.

  • The .package.json file is a common application to the package.json of all packages to be created.
  • The .packages.json file is a list of which files in the /src directory to package build and publish.

Please modify the setting files above to match the packages you will publish.

yarn run build-packages
yarn run publish-packages

Also, if you run the commands above, packages are built / published.

Restrictions

  • Please create directories with the same name as your package name within /src. If your package is @myorg/package1, you can create the directory /src/@myorg/package1.
  • Circular dependency will fail to build. If package1 and package2 refer to each other, the build will fail, so be careful.

Command-line

  • rocket-punch build
  • rocket-punch publish
  • rocket-punch doctor
  • rocket-punch view

Importable formats

Most Import Types available in Create-React-App are supported. Afterwards, Vite.js' basic import types will also be supported.

  • Plain Text
    • import string from './file.txt'
    • import string from './file.md'
  • YAML
    • import object from './file.yaml'
    • import object from './file.yml'
  • Images
    • import base64String from './file.jpg'
    • import base64String from './file.jpeg'
    • import base64String from './file.gif'
    • import base64String from './file.png'
    • import base64String from './file.webp'
  • SVG
    • import base64String, { ReactComponent } from './file.svg'