rsp/deno-dirname

Node-style __dirname and __filename polyfill for Deno

Programming since I was 6, professionally since I was 16.

I got obsessed with programming when I was a kid and hasn't recovered since then.

Currently building custom backend APIs using TypeScript/Node.js for the insurtech industry at Beesafe, Vienna Insurance Group.

💖❤️‍🔥

🤝

✍️

🗣

🏢

💖

deno-dirname's Issues

Slash too much

import { __ } from 'https://deno.land/x/dirname/mod.ts';


const { __filename, __dirname } = __(import.meta);

console.log(`${__dirname}/w.ts`.substr(1));

I get /C:/worka/example-deno/w.ts
instead of C:/worka/example-deno/w.ts

temporary solution is to use

console.log(`${__dirname}/w.ts`.substr(1));

Upload to deno.land/x/dirname

The page one lands on when accessing deno.land/x/dirname is currently a message saying the name has been reserved, but no releases have been uploaded yet. Is it the same module? In any case, thanks for the package mate!

suggestion about the name of the main function

could you contemplate the possibility of changing the function name to get a better understanding what do function do, when importing it into the code. Term "__" don't say much.
could to be similar to this:

export function fileData({ url = import.meta.url }: { url: string }) {
const u: URL = new URL(url);
const f: string = u.protocol === 'file:' ? u.pathname : url;
const d: string = f.replace(/[/][^/]*$/, '');
return {
  d,
    f,
    dirname: d,
        filename: f,
     __dirname: d,
     __filename: f,
  };
}

export function dirname(meta: { url: string }) {
  return fileData(meta).__dirname;

export function filename(meta: { url: string }) {
  return fileData(meta).__filename;
}