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 🙏

© 2025 – Pkg Stats / Ryan Hefner

loose-dependency-manager

v1.3.4

Published

Wire-up fragmented codes and files from various sources with a single command.

Readme

What is loose dependency manager?

Loose Dependency Manager (ldm) is a tool that helps you manage dependencies from various sources in a single file.

You can think of it as a sophisticated form of scp command that can be configured with a single specification file (ldm.yaml) and that supports versioning (if the remote source supports it) and locking mechanism.

Currently, it supports the following sources:

| Provider | Versioning Support | Can Download | URI Format | | --- | --- | --- | --- | | HTTP(S) | ❌ | only files | HTTP(S) URL | | GitHub | ✅ | files & directories | <github-source-id>:///path/to/file | | JSDelivr (npm) | ✅ | files & directories | <jsdelivr-npm-source-id>://default or <jsdelivr-npm-source-id>:///path/to/file | | JSDelivr (github) | ✅ | files & directories | <jsdelivr-github-source-id>:///path/to/file |

Installation

Before installing ldm, you need to have Node.js installed.

npm install -g loose-dependency-manager

Quick Start

Write a dependency specification file

You write a dependency specification file named ldm.yaml.

[!IMPORTANT] It is stronlgly recommended to set auth.token with personal access token when using GitHub as a source provider (even if you're using for public repositories). Github API imposes a harsh rate limit of 60 requests per hour for unauthenticated requests, so you may run into rate limit issues without a token.

version: "1"

dependencies:
  primitive.ts:
    uri: "@ts-essentials/ts-essentials:///lib/primitive/index.ts"
    version: latest
    destination: src/types/primitive.ts
  camel-case:
    uri: "@ts-essentials/ts-essentials:///lib/camel-case"
    version: latest
    destination: src/types/camel-case
  jquery:
    uri: jquery://default
    version: ^3.6.4
    destinations:
      - src/core.min.js
      - public/js/core.min.js
  reset.css:
    uri: https://meyerweb.com/eric/tools/css/reset/reset200802.css
    destination: public/css/reset.css
  pico.css:
    uri: "@picocss/pico:///css/pico.min.css"
    version: ^2.0.0
    destination: public/css/pico.min.css

sources:
  "@ts-essentials/ts-essentials":
    provider: github
    uri: ts-essentials/ts-essentials
    auth:
      token: ${GITHUB_TOKEN}
  jquery:
    provider: jsdelivr:npm
    uri: jquery
  "@picocss/pico":
    provider: jsdelivr:npm
    uri: "@picocss/pico"

config:
  envFile: .env
  deleteFilesOnRemove: true

YAML Validation for VSCode

For better editing experience, YAML validation is supported thanks to JSON schema and YAML VSCode Extension (by RedHat).

To enable YAML validation,

  • Install YAML VSCode Extension (by RedHat)
  • Add the following configuration to your .vscode/settings.json file.
    {
      "yaml.schemas": {
        "https://raw.githubusercontent.com/ldm-org/ldm/refs/heads/master/schema.json": "**/ldm.yaml"
      }
    }

Install dependencies

Then in terminal, run the following command.

ldm install

This will produce the following file sturcture, assuming that ldm.yaml is the only file in the directory.

|- ldm.yaml
|- ldm-lock.yaml
|--- src/
|----- core.min.js
|----- types/
|------- primitive.ts
|------- camel-case/
|--------- index.ts
|--------- README.md
|--- public/
|----- css/
|------- reset.css
|------- pico.min.css
|----- js/
|------- core.min.js

The example above can be summarized as following diagram.

example

Documentation

Documentation is not written yet. I'll try my best to write it as soon as possible.

Examples

You can find examples at e2e test scenarios.

Compare given and expected directory in each scenario to see what the execution of scenario.ts#scenario.command will produce.

Contribution

See Contributing Guide

License

MIT License © 2025-Present Joseph Hwang