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

grunt-deb

v0.2.5

Published

A grunt task that performs cross platform debian packaging

Downloads

21

Readme

grunt-deb

Performs cross platform debian packaging

NPM

Build Status

This task allows you to create your .deb without debhelper or Java. It's pure javascript. You only need tar and ar.

Getting started

This plugin requires Grunt ~0.4

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-deb --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-deb');

The deb_package task

###Overview In your Gruntfile (inside the initConfig object), add a section named deb_package.

A lot of options in this section are provided by the package.json file, but if you want to override them here's what to do:

grunt.initConfig({
    deb_package: {
        options: {
            maintainer: "Paul Varache <[email protected]>",
            uploaders: [ { "name": "Thomas Papiernik", "email": "[email protected]" } ]
            version: "1.0.0",
            name: "my-package",
            short_description: "short",
            long_description: "long",
            target_architecture: "all",
            category: "devel",
            build_number: "1",
            revision: "1",
            dependencies: [],           // List of the package dependencies
            extra_headers: [],          // List of extra headers to include
            tmp_dir: '.tmp',            // The task working dir
            output: './output/'         // Where your .deb should be created
        },
        build: {
            // Here you define what you want in your package
            files: [{
                cwd: './test_files/source',
                src: '**/*',
                dest: '/opt/my-package'
            }],
            // The task will create the links as src: dest
            links: {
                '/usr/bin/mp': '/opt/my-package/bin/mp'
            },
            // You can provide preinst, postinst, prerm and postrm script either by giving a file or what to put in it
            scripts: {
                preinst: {
                    src: './test_files/preinst.sh'
                },
                postinst: {
                    content: 'echo "postinst test"'
                }
            }
        }
    }
});

This will create a package with the name my-package_1.0.0-1_all.deb taht can be installed with sudo dpkg -i my-package_1.0.0-1_all.deb on all debian based architectures.

Options

options.maintainer

Type: String Default value: process.env.DEBFULLNAME <process.env.DEBEMAIL> or package.json author.name <author.email>

This value defines the maintainer of the package.

options.uploaders

Type: String Default value: package.json uploaders array { name, email }

This value defines the uploaders of the package. Take maintainers array from package.json

options.version

Type: String Default value: package.json version

This value defines the version of the package.

options.name

Type: String Default value: package.json name

This value defines the name of the package.

options.short_description

Type: String Default value: First line of package.json description

This value defines the short description of the package.

options.long_description

Type: String Default value: All line of package.json description except the first one

This value defines the long description of the package.

options.target_architecture

Type: String Default value: all

This value defines the architecture of the package.

options.revision

Type: String Default value: process.env.GIT_REVISION || process.env.SVN_REVISION || false

This value defines the revision of the package (use in name and package version).

options.build_number

Type: String Default value: process.env.BUILD_NUMBER || process.env.DRONE_BUILD_NUMBER || process.env.TRAVIS_BUILD_NUMBER || 1

This value defines the build number of the package.

options.category

Type: String Default value: misc

The software category. Used to fill the "section" field of the control file

options.extra_headers

Type: object Default value: {}

Extra headers to add to the package's control file, e.g. {"Foo": "1.2.3", "Bar": "abc"}


There is more to do:

  • Write tests
  • generation of the .changes and .dsc files

This task was developped with the help of Loïc Marie