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

packaholic

v1.3.15

Published

Node packaging tool.

Downloads

15

Readme

packaholic

packaholic-server, a simple implementation of packaging service based on packaholic.

Node packaging tool, support packing service.

Install

# on client
npm i packaholic -D

# on server
bun add packaholic

Usage

step 1:

define packaholic.config.ts under project root directory。

// packaholic.config.ts
import { defineConfig } from 'packaholic';

export default defineConfig({
  commands: [
    'npm run install',
    'npm run build',
  ],
  afterCommandsExec: () => {
    // upload dist dir to cdn
    // or other operations
  },
});

// also can export an function
export default (context) => {
  const { env } = context;

  return defineConfig({
    commands: [
      `npm run install -- --env=${env}`,
      'npm run build',
    ],
    afterCommandsExec: () => {
      // upload dist dir to cdn
      // or other operations
    },
  });
};

step 2:

On the packaging service, execute the runner method, which will automatically pull the project and execute the commands defined in packaholic.config.ts.

import { runner } from 'packaholic';

runner({
  source: 'local_path',
  context: {
    env: 'develop',
  },
});

try {
  await runner({
    source: 'git remote repository uri',
    repositoryRoot: './.cache_root',
    afterRepositoryCloned: () => {
    },
    onCommandExecError(err) {
      // return false to break
      return false;
    },
    afterConfigLoaded(config) {
      // config loaded
    },
    // define config filename, default is `packaholic.config.ts`
    // configFilename: 'packaholic.config.ts',
  });
} catch (err) {
  // fail
}

or run with customize bash:

import { runner } from 'packaholic';
import { spawn } from 'child_process';

runner({
  source: 'local_path',
  context: {
    env: 'develop',
  },
});

// or by Bun.spawn
const bash = spawn('bash', {
  shell: '/bin/bash',
  env: process.env,
});

try {
  await runner({
    source: 'git remote repository uri',
    repositoryRoot: './.cache_root',
    // If you need to customize some environments, such as using nvm to switch node, you can use this method.
    // packaholic will run the command in the bash object passed in.
    bash,
  });
} catch (err) {
  // fail
}

config

// packaholic.config.ts
import { defineConfig } from 'packaholic';

export default defineConfig({
  commands: [
    'npm run install',
    // start with @@ will ignore error
    '@@npm run install',
    // more configure
    {
      // replace env by `mappingEnvVariables`
      cmd: 'npm run build -- --ENV={{env}}',
      cwd: './',
      ignoreError: false,
      beforeExec: (opts) => {},
      afterExec: (opts) => {},
    },
  ],
  afterCommandsExec: (context) => {
    // upload dist dir to cdn
    // or other operations
  },
  mappingEnvVariables(context) {
    return {
      env: context.env,
    };
  },
  ignoreSpawnError: false,
});

why named packaholic

blend of "pack" and "-aholic" (from "workaholic").