</>PackageGraphPackageGraph

convert-source-map

npmv2.0.0

Converts a source-map from/to different formats and allows adding/changing properties.

Not recommended for new projects

No — convert-source-map should not be adopted for new projects. Last published 1423 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 1423 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 15 KB installed.

  • ASupply chain: grade A, Excellent.

    No install scripts, 2 maintainers, and a contained dependency surface.

  • 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 convert-source-map 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.

15 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
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the convert-source-map README.

var convert = require('convert-source-map');

var json = convert
  .fromComment('//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiYnVpbGQvZm9vLm1pbi5qcyIsInNvdXJjZXMiOlsic3JjL2Zvby5qcyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiQUFBQSIsInNvdXJjZVJvb3QiOiIvIn0=')
  .toJSON();

var modified = convert
  .fromComment('//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiYnVpbGQvZm9vLm1pbi5qcyIsInNvdXJjZXMiOlsic3JjL2Zvby5qcyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiQUFBQSIsInNvdXJjZVJvb3QiOiIvIn0=')
  .setProperty('sources', [ 'SRC/FOO.JS' ])
  .toJSON();

console.log(json);
console.log(modified);

convert-source-map vs the alternatives

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

PackageWeekly downloadsDependentsLicenseLast release
convert-source-mapthis page07MIT3 years ago
@jridgewell/gen-mapping163.4M4MIT1 day ago
istanbul-lib-source-maps55.8M5BSD-3-Clause1 day ago
@vitest/istanbul-lib-source-maps25K2MIT1 day ago
@jridgewell/remapping04MIT1 day ago
@jridgewell/trace-mapping020MIT1 day ago

Dependencies

Declared by convert-source-map v2.0.0. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (2)

inline-source-map ~0.6.2tap ~9.0.0

Used by

Popular packages that depend on convert-source-map.

Relationship graph

Dependencies (left) and dependents (right) of convert-source-map.

Frequently installed together

Release history

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

Recent versions of convert-source-map
VersionPublishedSizeLicense
2.0.0latest3 years ago15 KBMIT
1.9.03 years ago11 KBMIT
1.8.05 years ago10 KBMIT
1.7.06 years ago10 KBMIT
1.6.08 years ago10 KBMIT
1.5.18 years agoMIT
1.5.09 years agoMIT
1.4.09 years agoMIT
1.3.010 years agoMIT
1.2.010 years agoMIT
1.1.310 years agoMIT
1.1.210 years agoMIT
1.1.111 years agoMIT
1.1.011 years agoMIT
1.0.011 years agoMIT

Overview

convert-source-map is an npm package that converts a source-map from/to different formats and allows adding/changing properties. It has 7 known dependents in the graph. The latest version is 2.0.0, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need converts a source-map from/to different formats and allows adding/changing properties and value a focused solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Clear open-source license (MIT).
  • Lean dependency tree (2 direct dependencies).

Cons

  • No bundled TypeScript types (may require a separate @types package).

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

Maintainers

Keywords

Frequently asked questions

Should I use convert-source-map?

No — convert-source-map should not be adopted for new projects. Last published 1423 days ago.

How do I install convert-source-map?

Run `npm install convert-source-map` to add convert-source-map to your npm project.

What license is convert-source-map released under?

convert-source-map is distributed under the MIT license.

How popular is convert-source-map?

npm does not publish download counts. Within PackageGraph's crawl, 7 known packages depend on convert-source-map.

Is convert-source-map still maintained?

The most recent release of convert-source-map (v2.0.0) was published 3 years ago.

Does convert-source-map run install scripts?

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