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 🙏

© 2026 – Pkg Stats / Ryan Hefner

lud

v0.1.2

Published

The Luddites CLI Client To Manage Free And Paid Versions Of Packages For Publishing.

Downloads

4

Readme

Lud

by Art Deco™Professional Software Development Company In London.

npm version

PLEASE REFER TO THE FULL DOCUMENTATION ON THE LUD HOMEPAGE! Information provided in this README has illustrative purpose only, is limited and doesn't describe API of this library in details.

lud is: a library to manage free and paid versions of the same package within its repo. The package.json source of truth for publishing is abandoned, and is only used to store dependencies' information for development purposes. In its place, the package folder is added in which a JS file index.js is kept from which metadata is exported. Different versions for publishing are stored as individual folders in the package folder, and lud generates package.json files to put in each of the versions (free/paid) and copies necessary files across.

The packages are published individually from within each of the folders with standard yarn/npm publish commands, however the future version will allow to publish packages on the luddites.io registry for paid packages.

Below is an example of the package folder:

package
├── EULA
├── LICENSE
├── free
│   ├── CHANGELOG.md
│   ├── LICENSE
│   ├── README.md
│   ├── bin
│   │   └── lud.js
│   └── package.json
└── index.js
# lud is meant to be a dev dependency
yarn add -D lud
npm i --save-dev lud

Example

The following is an example of package/index.js of the Erte package, that allows to use ANSI codes to format and colour strings for CLI output:

import { dependencies } from '../package.json'

export let name = '@artdeco/erte'
export let description = 'String difference with colour and CLI ANSI formatting.'

let keywords = [
  'erte', 'art deco', 'artdeco',
  'string', 'diff', 'ansi',
  'color', 'colour',
  'difference', 'cli',
]
export let author = 'Art Deco™'
export let bugs = {
  url: 'https://github.com/art-deco/Issues',
  email: '[email protected]',
}
export let homepage = 'https://www.artd.eco'

const EULA = 'package/EULA'
const LICENSE = 'package/LICENSE'

let compile = ['compile/index.js']
export const FREE = {
  description: `${description} [FREE]`,
  addFiles: ['README.md', 'CHANGELOG.md', LICENSE, ...compile],
  license: 'AGPL-3.0',
  keywords,
}
export const PUBLIC = {
  ...FREE,
  name: 'erte',
  description: `${description} [PUBLIC]`,
  copy: {
    'package/free/erte.js': 'erte.js',
  },
}
export const PAID = {
  description: `${description} [PAID]`,
  addFiles: ['README.md', 'CHANGELOG.md', EULA, ...compile],
  license: 'SEE LICENSE IN EULA',
  private: true,
  paid: true,
  keywords,
}
export const LIB = {
  dependencies,
  description: `${description} [LIB]`,
  addFiles: [EULA, ...compile, 'types', 'src'],
  module: 'src/index.js',
  externs: 'types/externs.js',
  license: 'SEE LICENSE IN EULA',
  private: true,
  paid: true,
  lib: true,
  copy: {
    'package/paid/erte.js': 'erte.js',
  },
}

The example includes different versions, including free (published on npm as erte) and its analogue but with namespace, public (published on npm as @artdeco/erte), as well as paid and library (w/ source code) versions published on the private registry. Since the source code is kept in a single repo, it would be a chore to switch between branches for different package versions, and maintaining different package.json files is too cumbersome, therefore Lud solves this problem by allowing to generate and maintain multiple versions within the package directory.

There are additional APIs that can be used within the index.js file:

  • addFiles: an array of files that need to be added to the target package, preserving their paths structure.
  • copy: copies these files into the given location relative to the target package's folder.

Dependencies can be required from the package.json and exported via entry as well. However, in the example for Erte, they are only exported with the LIB version that is meant for development and provides the source code for the package, since all other versions compile the source code and its dependencies into a single JS file with a compiler.

CLI

The package is used from the CLI. Please refer to the documentation for all available commands. Standard usage:

# generate free version into package/free
lud@luddites:~$ lud -t package/free -e FREE

Copyright & License

The public free version of the package is provided under the GNU Affero General Public License v3.0 so that you can use it in AGPL-compatible projects. The full version requires purchasing of a license key and is distributed under an EULA terms. Please contact Art Deco on Keybase chat to purchase the key.