Package Exports

package-name-conflict

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (package-name-conflict) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

package-name-conflict

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 Dependencies

@bconnorwhite/bob: Bob is a toolkit for TypeScript projects

License

MIT

is-name-taken: Check if an NPM package name is taken
all-package-names: Get all NPM package names
npm-pd: A CLI dashboard for NPM publishers
npms-io-client: Isomorphic typed client for npms.io