</>PackageGraphPackageGraph

vlq

npmv2.0.4TypeScript

Generate, and decode, base64 VLQ mappings for source maps and other uses

Not recommended for new projects

No — vlq should not be adopted for new projects. Last published 1787 days ago.

  • AAdoption: grade A, Excellent.

    9.5M downloads per week and 2 known dependents.

  • FMaintenance: grade F, Failing.

    Last published 1787 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 7.3 KB installed.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding vlq to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

7.3 KB
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
No constraint declared
Module format
ESM + CommonJS
TypeScript
Types included
Install scripts
None

Quick start

A usage example from the vlq README.

jsFull README ↗
vlq.encode(123); // '2H';
vlq.encode([123, 456, 789]); // '2HwcqxB'

vlq vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
vlqthis page9.5M2MIT4 years ago
istanbul-lib-source-maps55.8M5BSD-3-Clause1 day ago
@vitest/istanbul-lib-source-maps25K2MIT1 day ago
@jridgewell/sourcemap-codec07MIT1 day ago
magic-string011MIT1 day ago
base64-js03MIT1 day ago

Dependencies

Declared by vlq v2.0.4. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (2)

rollup ^2.58.0typescript ^4.4.4

Used by

Popular packages that depend on vlq.

metro-source-mapnpm

🚇 Source map generator for Metro.

↓ 0/wk◈ 5 dependents⚖ MITTS
metro-symbolicatenpm

🚇 A tool to find the source location from JS bundles and stack traces.

↓ 0/wk◈ 3 dependents⚖ MITTS

Relationship graph

Dependencies (left) and dependents (right) of vlq.

metro-source-mapmetro-symbolicatevlq
vlq dependencies dependents

Frequently installed together

flow-enums-runtimenpm

Runtime to be use with the Flow Enums transform.

↓ 0/wk◈ 16 dependents⚖ MIT
invariantnpm

invariant

↓ 0/wk◈ 16 dependents⚖ MIT
source-mapnpm

Generates and consumes source maps

↓ 0/wk◈ 16 dependents⚖ BSD-3-ClauseTS
nullthrowsnpm

flow typed nullthrows

↓ 0/wk◈ 13 dependents⚖ MITTS
@babel/traversenpm

The Babel Traverse module maintains the overall tree state, and is responsible for replacing, removing, and adding nodes

↓ 0/wk◈ 27 dependents⚖ MIT
@babel/parsernpm

A JavaScript parser

↓ 0/wk◈ 23 dependents⚖ MIT
ob1npm

A small library for working with 0- and 1-based offsets in a type-checked way.

↓ 0/wk◈ 1 dependents⚖ MITTS
@babel/typesnpm

Babel Types is a Lodash-esque utility library for AST nodes

↓ 0/wk◈ 34 dependents⚖ MIT
metro-source-mapnpm

🚇 Source map generator for Metro.

↓ 0/wk◈ 5 dependents⚖ MITTS
metro-symbolicatenpm

🚇 A tool to find the source location from JS bundles and stack traces.

↓ 0/wk◈ 3 dependents⚖ MITTS

Release history

No releases in the last two years, typically about 99 days apart.

Recent versions of vlq
VersionPublishedSizeLicense
2.0.4latest4 years ago7.3 KBMIT
2.0.34 years ago9.4 KBMIT
2.0.24 years ago5.8 KBMIT
2.0.14 years ago5.8 KBMIT
2.0.04 years ago5.8 KBMIT
1.0.17 years ago8.1 KBMIT
1.0.08 years ago—MIT
0.2.39 years ago—MIT
0.2.29 years ago—MIT
0.2.111 years ago—MIT
0.2.011 years ago—MIT
0.1.012 years ago—MIT

Overview

vlq is an npm package that generate, and decode, base64 VLQ mappings for source maps and other uses. It is extremely widely used, with about 9.5M downloads per week and 2 known dependents in the graph. The latest version is 2.0.4, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need generate, and decode, base64 VLQ mappings for source maps and other uses and value a battle-tested, widely-adopted solution.

When not to use it

Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.

Pros

  • Large, well-established user base (9.5M weekly downloads).
  • Ships TypeScript type definitions.
  • Clear open-source license (MIT).
  • Lean dependency tree (2 direct dependencies).

Cons

  • No significant drawbacks detected from available metadata.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

rich_harris

Keywords

base64sourcemapsourcemapsvlq

Frequently asked questions

Should I use vlq?

No — vlq should not be adopted for new projects. Last published 1787 days ago.

How do I install vlq?

Run `npm install vlq` to add vlq to your npm project.

What license is vlq released under?

vlq is distributed under the MIT license.

How popular is vlq?

vlq has approximately 9,509,788 downloads per week and 2 known dependent packages.

Is vlq still maintained?

The most recent release of vlq (v2.0.4) was published 4 years ago.

Does vlq run install scripts?

No. vlq does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.