</>PackageGraphPackageGraph

slash

npmv5.1.0TypeScript

Convert Windows backslash paths to slash paths

Not recommended for new projects

No — slash should not be adopted for new projects. Last published 1219 days ago.

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

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 1219 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 3.2 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 slash 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.

3.2 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
node >=14.16
Module format
ESM only
TypeScript
Types included
Install scripts
None

Quick start

A usage example from the slash README.

import path from 'node:path';
import slash from 'slash';

const string = path.join('foo', 'bar');
// Unix    => foo/bar
// Windows => foo\\bar

slash(string);
// Unix    => foo/bar
// Windows => foo/bar

slash vs the alternatives

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

PackageWeekly downloadsDependentsLicenseLast release
slashthis page014MIT3 years ago
normalize-path72.6M1MIT1 day ago
path-key244.9M1MIT1 day ago
tildify01MIT1 day ago
color-convert299.6M1MIT1 day ago
@jridgewell/resolve-uri166.3M1MIT1 day ago

Dependencies

Declared by slash v5.1.0. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (3)

ava ^5.2.0tsd ^0.28.1xo ^0.54.2

Used by

Popular packages that depend on slash.

Relationship graph

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

Frequently installed together

Release history

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

Recent versions of slash
VersionPublishedSizeLicense
5.1.0latest3 years ago3.2 KBMIT
5.0.13 years ago3.2 KBMIT
5.0.04 years ago3.2 KBMIT
4.0.05 years ago3.7 KBMIT
3.0.07 years ago3.4 KBMIT
2.0.08 years ago2.8 KBMIT
1.0.012 years agoMIT
0.1.312 years agoMIT
0.1.113 years agoMIT
0.1.013 years agoMIT

Overview

slash is an npm package that convert Windows backslash paths to slash paths. It has 14 known dependents in the graph. The latest version is 5.1.0, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need convert Windows backslash paths to slash paths and value a focused 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

  • Ships TypeScript type definitions.
  • Clear open-source license (MIT).
  • Lean dependency tree (3 direct dependencies).

Cons

  • No significant drawbacks detected from available metadata.

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

Maintainers

Keywords

Funding

Frequently asked questions

Should I use slash?

No — slash should not be adopted for new projects. Last published 1219 days ago.

How do I install slash?

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

What license is slash released under?

slash is distributed under the MIT license.

How popular is slash?

npm does not publish download counts. Within PackageGraph's crawl, 14 known packages depend on slash.

Is slash still maintained?

The most recent release of slash (v5.1.0) was published 3 years ago.

Does slash run install scripts?

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