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-deb

v1.1.2

Published

Create a Debian package for a binary

Downloads

200

Readme

pkg-deb

Create a Debian package from an executable binary.

Usage

pkg-deb 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 DEBIAN/control with the following fields:

  • name
  • author - Debian only accepts a single author as part of its maintainer field
  • description
  • homepage

Before packaging the provided binary is written to /usr/bin for it to be able to be executed globally once installed on a user's system.

const pkgDeb = require('pkg-deb')
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: 'x64',
  logger: console.log
}

await pkgDeb(opts)

API

await pkgDeb(opts)

Creates a Debian package in your dest directory. Under the hood pkgDeb creates a DEBIAN/control file before creating a new 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.deb 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, amd64, all.
  • opts.logger: Logger to help you debug. Defaults to debug.

Contributors

License

Copyright (c) 2016 Daniel Perez Alvarez (unindented.org). This is free software, and may be redistributed under the terms specified in the LICENSE file.