package-name-conflict
Check if NPM package names conflict
Last updated 4 years ago by bconnorwhite .
MIT · Repository · Original npm · Tarball · package.json
$ gnpm install package-name-conflict 
SYNC missed versions from official npm registry.

package-name-conflict

npm typescript Coverage Status GitHub stars Twitter Follow

Check if NPM package names conflict.

To prevent typosquatting, NPM no longer allows names that differ from existing packages in punctuation only.

This package checks if package names conflict.

Note:
Package names are not validated. To validate package names, use validate-package-name.

Installation

yarn add package-name-conflict
npm install package-name-conflict

API

import { conflicts, conflictsAny, transform } from "package-name-conflict";

// Check if two package names conflict:

conflicts("abc.123", "Abc-123"); // true

// Return first conflicting package name in an array:

conflictsAny("abc123", ["test", "test2", "Abc-123"]); // "Abc-123"

conflictsAny("abc123", ["test", "test2"]); // false

// Transform a package name to its simplified form:

transform("Abc-123"); // "abc123"

Types:

function transform(name: string): string;

function conflicts(nameA: string, nameB: string): boolean;

function conflictsAny(name: string, names: string[]): string | false;


Dev DependenciesDavid


License license

MIT


Related Packages

Current Tags

  • 1.0.3                                ...           latest (4 years ago)

3 Versions

  • 1.0.3                                ...           4 years ago
  • 1.0.1                                ...           4 years ago
  • 1.0.0                                ...           4 years ago
Maintainers (1)
Downloads
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 0
Dependencies (0)
None
Dev Dependencies (2)
Dependents (1)

Copyright 2013 - present © cnpmjs.org | Home |