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

pkg-rpm

v1.0.3

Published

Create a RedHat-RPM package for a Node.js executable.

Downloads

170

Readme

pkg-rpm

Create a Debian package from an executable binary.

Usage

pkg-rpm requires a specific structure for your binary directory. For example:

.
└── project 
    ├── LICENSE
    ├── README.md
    ├── package.json
    └── dist 
        └── executable 

Your source directory must have a package.json for a properly generated SPECS/packageName.spec with the following fields:

  • name
  • description
  • license
  • homepage
const pkgRhel = require('pkg-rpm')
const path = require('path')

const opts = {
  version: '0.0.1',
  name: 'executable',
  dest: path.join(__dirname, 'project', 'dist'),
  src: path.join(__dirname, 'project'), 
  input: path.join(__dirname, 'project', 'dist', 'executable'),
  arch: 'amd64',
  logger: console.log
}

await pkgRhel(opts)

API

await pkgRhel(opts)

Creates a RedHat package in your dest directory. Under the hood pkgRhel generates an applicable SPECS/packageName.spec file and runs rpmbuild to create the package.

Options:

  • opts.version: Version number of the package.
  • opts.name: Name of the package.
  • opts.dest: Destination where to write the final package. It will be saved as name-version-arch.rpm in the provided dest.
  • opts.src: Path to source directory. Must have a package.json.
  • opts.input: Binary to be packaged.
  • opts.arch: Architecture. You can specify: x64 or amd64.
  • opts.logger: Logger to help you debug. Defaults to debug.

The full directory structure that pkgRhel creates is as follows:

.
└── pkg-rpm-tmpdirectory (created by pkgRhel.createStagingDir())
    ├── BUILD
    │   └── provided_binary (copied over with pkgRhel.copyApplication())
    ├── BUILDROOT
    ├── RPMS (this will contain the built RPM)
    │   └── amd64 (current architecture directory)
    │       └── packageName-version-arch.rpm (created by pkgRhel.createPackage())
    ├── SOURCES
    ├── SPECS
    │   └── module.spec (will be created with pkgRhel.createSpec())
    └── SRPMS

See Also:

License

Apache-2.0