Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad value in package.json #20

Open
tuxpoldo opened this issue Jul 27, 2021 · 1 comment · May be fixed by #21
Open

Bad value in package.json #20

tuxpoldo opened this issue Jul 27, 2021 · 1 comment · May be fixed by #21

Comments

@tuxpoldo
Copy link

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
Copy link

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.

jmattsson added a commit to DiUS/chariotd that referenced this issue Mar 26, 2024
...and deprecation warning from node-getopt. See
  jiangmiao/node-getopt#20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants