path-browserify

path-browserify is a browser-compatible reimplementation of Node.js’s built-in path module, providing the same join, resolve, relative, dirname, basename, extname, and parse/format functions for environments — namely web browsers — that don’t have Node’s module available natively. It matches the Node.js 10.3 path API and implements only the POSIX-style functions, not the Windows (win32) variants.

The package exists almost entirely as bundler infrastructure: Browserify and webpack automatically substitute path-browserify whenever bundled code calls require('path') in a browser target, so most consumers never install or import it directly — it’s a dependency of the bundling pipeline rather than application code.

What You Get

• Browser-safe implementations of path.join, path.resolve, path.relative, path.normalize
• path.dirname, path.basename, and path.extname matching Node.js semantics
• path.parse and path.format for splitting and reassembling path components
• POSIX-only path handling (no win32 path separator support)
• Automatic use as the default path polyfill in Browserify and webpack bundler configurations

Common Use Cases

• Running Node.js-authored libraries that call require('path') inside a webpack or Browserify browser bundle
• Building isomorphic JavaScript utilities that need consistent path-joining behavior in both Node and browser environments
• Polyfilling path for code shared between a Node backend and a bundled frontend without maintaining two implementations
• Satisfying transitive dependencies of npm packages that assume a Node-like path module is always available

Under The Hood

Architecture The entire implementation lives in a single 529-line index.js file structured around internal POSIX path-parsing helpers (segment normalization, ../. resolution) that back the public join, resolve, normalize, relative, dirname, basename, extname, parse, and format exports — mirroring the internal structure of Node.js’s own path.js source closely enough to track upstream Node behavior function-for-function. Tech Stack Zero runtime dependencies; it is deliberately dependency-free vanilla JavaScript so it can be safely bundled into any browser build without pulling in further transitive code. Code Quality The test/ directory is comprehensive and mirrors Node.js’s own path test suite naming convention (test-path-join.js, test-path-resolve.js, test-path-relative.js, test-path-parse-format.js, test-path-zero-length-strings.js, etc.), covering each exported function plus edge cases like zero-length string arguments — a pattern consistent with the package being adapted directly from Node.js’s own internal path tests. API Design The API is an intentional 1:1 mirror of Node’s built-in path module, so there is effectively no learning curve for anyone already familiar with Node — the tradeoff is that the package has been stable at the Node 10.3 API surface with no further updates, so newer path additions in later Node versions are not reflected.