Bad value in package.json

[tuxpoldo]

There is a bad value in the package.json file that causes the application to print an error message at every start:

(node:8) [DEP0128] DeprecationWarning: Invalid 'main' field in '/usr/local/lib/node_modules/@alo5/availability/node_modules/node-getopt/package.json' of './lib'. Please either fix that or report it to the module author
--
(Use `node --trace-deprecation ...` to show where the warning was created)

When used in a docker container, this error message is not printed on STDERR but redirected to STDOUT causing side effect when it is desired to redirect semantically relevant output to a file.

[DinoChiesa]

This PR fixes the issue for me. It's not been merged into jiangmiao/node-getopt at this point.

For any future searchers that arrive here before this PR is merged, if you want to avoid the warnings, you can replace the line that looks like this in your package.json:

  "node-getopt" : "0.3.2",

with this :

  "node-getopt": "git://github.com/tuxpoldo/node-getopt.git#05e498731c14b648fa332ca78d3a301c5e4be440",

That lone string refers to the commit in tuxpoldo's repo that fixes the warning.

[itskevp-del]

Still getting this error in 2026 in node v22.16.0. Seems the thing that is deprecated is now the "main" tag itself. I assume it's being kept around for backwards compatibility. The modern version is the tag "exports" which allows for multiple entrypoint definitions. Useless for this project so the warning doesn't affect anything, but it's a simple thing to fix

Replacing "main": "./lib", in package.json with the following gets rid of the warning and is how it should be done:

"exports" : { ".": "./lib/getopt.js" },

Would be great if this could actually get to NPM somehow because I love this package and it's the top result on google for the obvious search 'nodejs getopt', the first thing any C programmer will type into the searchbar. Using alternatives and extra arguments when installing (as suggested by the recent activity) just for one line in a configuration file seems like a shame. I don't know how the NPM process works though, is it just stuck like this forever if @jiangmiao isn't watching the repo anymore? Can it be forked into 'better-node-getopt' with this one change? lol