npmpackage.info

Gathering detailed insights and metrics for nodemjs

Other packages similar to nodemjs

esbrowserify-pmb

0.1.2

Easily browserify ES modules. Think esmod-pmb/nodemjs but for browserify.

Gathering detailed insights and metrics for nodemjs

nodemjs - 0.1.16 | npmpackage.info

nodemjs

Run .mjs files from your command line, with all the tweaks from esmod-pmb.

0.1.16

JavaScript

16.60 kB

3.1

Installations

npm install nodemjs

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

8.17.0

NPM Version

6.14.17 Pull Requests

Open

0

Total

0

Closed

0

Issues

Open

2

Total

3

Closed

1

Releases

Unable to fetch releases

Languages

JavaScript

Shell

JavaScript (65.14%)

Shell (34.86%)

Developer

mk-pmb

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

2 Stars

25 Commits

2 Watchers

5 Branches

1 Contributors

Updated on Apr 07, 2025

Maintainers

View All 1 Contributors

Package Meta Information

Latest Version

0.1.16

Package Id

nodemjs@0.1.16

Unpacked Size

16.60 kB

Size

7.08 kB

File Count

NPM Version

6.14.17

Node Version

8.17.0

Published on

May 13, 2025

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

esmod-pmb p-each-series-cjs p-eval

Dev Dependencies

lodash.upperfirst p-fatal rot-13

nodemjs

Run .mjs files from your command line, with all the tweaks from esmod-pmb.

Added features:

Legacy-resolves module names passed with -r if they would otherwise yield the ERR_MODULE_RESOLUTION_LEGACY error.
Pre-imports all modules listed in env var NODEMJS_PRELOAD and npm setting nodemjs-preload (see caveats below). Multiple module specs can be separated with spaces. They will be loaded even before the -r pre-imports.

⚠ Incompatible with node.js v20+! ⚠

… because the upstream esm module is no longer maintained. See issue #2.

API

No.

CLI

1$ nodemjs test/uc1st.mjs
2uc1st: [ 'Using dummy input', 'Because there were', 'No CLI args' ]
3
4$ ./test/uc1st.mjs foo bar qux
5uc1st: [ 'Foo', 'Bar', 'Qux' ]

Setup

npm install --global nodemjs
Make sure you have a node.js (compatible) binary available as the nodejs command. If you use sane package sources, you probably do. If you don't, just make a symlink nodejs to node or whatever it's called on your system.
(If you'd like to argue the supremacy of the more generic node command name, file an issue, ideally after you've renamed the Node.js foundation to Node foundation.)
As of 0.1.7, you can configure your favorite nodejs replacement via the NODEJS_CMD env var.

Known issues

Currently no support for setting process.mainModule, see the upstream bug ticket.
npm config caveat: The nodemjs-preload npm setting is currently ignored if its value as a string is literally undefined. If you want to pre-load a module with that name and nothing else, put it in twice, with a space between. See also: Duplicate pre-imports.
Duplicate pre-imports: nodemjs currently does not check whether a module you're trying to pre-import had already been imported before. Usually node's module cache voids all non-first import attempts per module, so this won't matter — unless you use cache-busting modules, in which case you're on your own.
REPL: The REPL isn't upgraded to ESM because esm currently cannot expose its REPL in a clean and easy way.
The invokedAs context property for nodemjsCliMain doesn't work.
Needs more/better tests and docs.

License

ISC

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Maintained

Determines if the project is "actively maintained".

0

SAST

Determines if the project uses static code analysis.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

License

Determines if the project has defined a license.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

Score

3.1

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More