Use deno_std path module?

Open
#30 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
deno, javascript
Domain
web-dev

Research direction

Start by comparing the current module entry point with the proposed mod.ts exports, then review package.json and the deno bundle command. Confirm the deno_std path API works for the package's existing consumers and that the generated ES module and package metadata preserve the current interface.

Written by the indexing model from the issue text.

Description

Would you mind switch to use deno_std's path module? API is compatible with Node.js, simply use deno bundle to output es module, make bundlers do tree shaking better

// mod.ts
import { win32, posix } from 'https://deno.land/std@0.163.0/path/mod.ts'

export { win32, posix }

export const {
  basename,
  delimiter,
  dirname,
  extname,
  format,
  fromFileUrl,
  isAbsolute,
  join,
  normalize,
  parse,
  relative,
  resolve,
  sep,
  toFileUrl,
  toNamespacedPath
} = posix

deno bundle mod.ts index.js

// package.json
{
  "module": "./index.js",
  "main": "./index.js",
  "type": "module"
}
Dominant language
JavaScript
Stars
192
Forks
54
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from browserify/path-browserify

All issues in browserify/path-browserify

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.