
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
cross-dirname
Advanced tools
[Node.js](https://nodejs.org) + [Gjs](https://gjs.guide/) + [Deno](https://deno.land/) module that returns the current script dirname and filename. Similar to `__dirname` and `__filename` but also works in CommonJs and ES modules.
Node.js + Gjs + Deno module that returns the current script dirname and filename. Similar to __dirname
and __filename
but also works in CommonJs and ES modules.
On Node.js and GJS you can install the package as with NPM:
npm install cross-dirname --save
On Deno you just need to import this package:
import { getDirname, getFilename } from 'https://deno.land/x/cross_dirname/mod.ts';
Please do not use getDirname
and getFilename
in nested other methods, instead always use them in the root of your file, otherwise it may return wrong results.
// /path/to/the/script.mjs
import { getDirname, getFilename } from 'cross-dirname'
console.log(getDirname()) // outputs "/path/to/the"
console.log(getFilename()) // outputs "/path/to/the/script.mjs"
// /path/to/the/script.cjs
const { getDirname, getFilename } = require('cross-dirname');
console.log(getDirname() === __dirname) // true
console.log(getFilename() === __filename) // true
// /path/to/the/script.ts
import { getDirname, getFilename } from 'https://deno.land/x/cross_dirname@v0.0.4/mod.ts';
console.log(getDirname()); // outputs "/path/to/the"
console.log(getFilename()); // outputs "/path/to/the/script.ts"
You can use NPM packages in GJS with a bundler like esbuild.
Take a look at the examples for an GJS + esbuild example, you can start the example like this:
# Install dev dependencies
npm install
# Go to the example
cd examples/gjs
# Bundle src/index.js
node esbuild.mjs
# Run the bundled index.js
gjs -m index.js
You can run the examples with
npm install
npm run build
deno run ./examples/deno/index.ts
# -> /.../examples/deno
node ./examples/node/index.cjs
# -> /.../examples/node
node ./examples/node/index.mjs
# -> /.../examples/node
node ./examples/gjs/esbuild.mjs
gjs -m ./examples/gjs/index.js
# -> /.../examples/gjs
Contributions for more platforms are welcome :)
This module has been tested on the following platforms:
Runtime | Type | Platform | State |
---|---|---|---|
Node.js | CJS | Linux | ✔ |
Node.js | CJS | MacOS | ✔ |
Node.js | CJS | Windows | ✔ |
Node.js | ESM | Linux | ✔ |
Node.js | ESM | MacOS | ✔ |
Node.js | ESM | Windows | ✔ |
Deno | ESM | Linux | ✔ |
Deno | ESM | MacOS | ✔ |
Deno | ESM | Windows | ✔ |
Gjs | ESM | Linux | ✔ |
Gjs | ESM | MacOS | UNTESTED |
Gjs | ESM | Windows | UNTESTED |
Chrome | ESM | Browser | ✔ |
Chrome | CJS | Browser | ✔ |
You can run all tests with:
npm run test
Or the tests for a special runtime:
npm run test:node
npm run test:deno
npm run test:gjs
npm run test:browser´
FAQs
[Node.js](https://nodejs.org) + [Gjs](https://gjs.guide/) + [Deno](https://deno.land/) module that returns the current script dirname and filename. Similar to `__dirname` and `__filename` but also works in CommonJs and ES modules.
We found that cross-dirname demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.