Identifiers

npm Package Name

Validate npm package names including scoped packages (@org/package), per the npm naming spec.

Try it in RegexPro →

Available in

JSSupported

JavaScript / ECMAScript

Browser-native RegExp. Default if you don't pick.

PYSupported

Python (re)

CPython stdlib `re`. Unicode-aware `\w` and `\d` by default.

GOSupported

Go (RE2)

Linear-time matching. No backreferences or lookarounds.

Pattern

regexengine-agnostic
^(?:@[a-z0-9\-*~][a-z0-9\-*._~]*\/)?[a-z0-9\-~][a-z0-9\-._~]*$

Raw source: ^(?:@[a-z0-9\-*~][a-z0-9\-*._~]*\/)?[a-z0-9\-~][a-z0-9\-._~]*$

How it works

The optional group (?:@[a-z0-9\-*~][a-z0-9\-*._~]*\/)? matches a @scope/ prefix for scoped packages. The main name [a-z0-9\-~][a-z0-9\-._~]* matches lowercase letters, digits, hyphens, dots, and tildes. Uppercase is not allowed per npm rules.

Examples

Input

react

Matches

  • react

Input

@types/node

Matches

  • @types/node

Input

MyPackage

No match

—

Common use cases

  • •package.json validation in monorepo tooling
  • •Custom registry name enforcement
  • •Automated dependency auditing scripts
  • •CLI tools that accept package names as arguments
←PreviousLogfmt Key-Value Pair
All patterns
NextEmoji (Unicode)→