Skip to content

Cannot disable warnings when node is launched via a shell script. #10802

Closed
Closed
Cannot disable warnings when node is launched via a shell script.#10802
Labels
feature requestIssues requesting new Node.js features.processIssues and PRs related to the process subsystem.

Description

@dzrw
dzrw
opened on Jan 14, 2017

As an end-user, I don't want to ever see warnings or deprecations. However, when node is invoked from a shell script via a shebang, there is no opportunity to pass the --no-warnings option to the process.

#!/usr/bin/env node --no-warnings
console.log("you will never get this far, so it doesn't matter if this compiles");

Is there an environment variable that can be set to toggle this option? If not, please add support for something like NODE_NO_WARNINGS=1.

Activity

  1. dzrw
    changed the title [-]Cannot disable warnings when scripts are launched from the shell.[/-] [+]Cannot disable warnings when node is launched via a shell script.[/+] on Jan 14, 2017
  2. mscdex
    added
    feature requestIssues requesting new Node.js features.
    processIssues and PRs related to the process subsystem.
    on Jan 14, 2017
  3. cjihrig
    added a commit that references this issue on Jan 19, 2017

    process: add NODE_NO_WARNINGS environment variable

    4990212
  4. cjihrig
    closed this as completedin #10842on Jan 19, 2017
  5. italoacasas
    added 2 commits that reference this issue on Jan 25, 2017

    process: add NODE_NO_WARNINGS environment variable

    7212a2b

    process: add NODE_NO_WARNINGS environment variable

    d24491c
  6. MylesBorins
    added 2 commits that reference this issue on May 16, 2017

    process: add NODE_NO_WARNINGS environment variable

    846270f

    process: add NODE_NO_WARNINGS environment variable

    637d9e3
  7. andrew749
    added a commit that references this issue on Jul 19, 2017

    process: add NODE_NO_WARNINGS environment variable

    621aaaf

  8. mnpenner commented on Feb 5, 2019

    @mnpenner
    mnpenner
    on Feb 5, 2019

    What's the solution?

    When I try putting this at the top of my file:

    #!/usr/bin/env NODE_NO_WARNINGS=1 node

    I just get:

    /usr/bin/env: ‘/path/to/my/script’: Text file busy

  9. bnoordhuis commented on Feb 5, 2019

    @bnoordhuis
    bnoordhuis
    on Feb 5, 2019
    Member

    @mnpenner https://unix.stackexchange.com/questions/399690/multiple-arguments-in-shebang

  10. Doragd commented on Mar 14, 2019

    @Doragd
    Doragd
    on Mar 14, 2019

    @mnpenner
    like this:

    #!/usr/bin/env
export NODE_NO_WARNINGS=1

    it works. :)

  11. mnpenner commented on Mar 14, 2019

    @mnpenner
    mnpenner
    on Mar 14, 2019

    @Doragd Huh? How would that work... the file contains JavaScript, it'll syntax error on export NODE_NO_WARNINGS=1

  12. 8 remaining items

  13. benjamingr commented on Sep 18, 2019

    @benjamingr
    benjamingr
    on Sep 18, 2019
    Member

    @jasnell one issue I just noticed is that that can't be set from within the program when it has already launched.

  14. SteveDeWald commented on Jan 12, 2020

    @SteveDeWald
    SteveDeWald
    on Jan 12, 2020

    @benjamingr, are you able to put it in the shebang? This worked for me:

    #!/usr/bin/env NODE_OPTIONS=--no-warnings node

  15. squallstar commented on Jan 15, 2020

    @squallstar
    squallstar
    on Jan 15, 2020

    This also worked for me:

    process.env.NODE_NO_WARNINGS = 1;

  16. hexrcs commented on Jan 16, 2020

    @hexrcs
    hexrcs
    on Jan 16, 2020

    @squallstar doesn't work for me.

    Which node version are you testing on? I'm testing fs.promises on node 10.16.0. The module doesn't emit a warning in v12.13.0 though because I believe it's no longer experimental.

  17. squallstar commented on Jan 16, 2020

    @squallstar
    squallstar
    on Jan 16, 2020

    @hexrcs the above works for me on Node 12. I have right before a process.env.NODE_TLS_REJECT_UNAUTHORIZED = '0'; and this doesn't trigger a warning (while it does when NODE_NO_WARNINGS is not defined).

  18. hexrcs commented on Jan 16, 2020

    @hexrcs
    hexrcs
    on Jan 16, 2020

    Is this documented anywhere? I couldn't find anything about this env variable but it would certainly be great if we finally get this feature. :)

  19. squallstar commented on Jan 16, 2020

    @squallstar
    squallstar
    on Jan 16, 2020

    @hexrcs https://nodejs.org/api/cli.html#cli_node_no_warnings_1 (or search for NODE_NO_WARNINGS on that page, the setting was added on Node 6).

  20. hexrcs commented on Jan 16, 2020

    @hexrcs
    hexrcs
    on Jan 16, 2020

    Weird, because setting it to either a string "1" or number 1 doesn't work on node v10 on my system (MacOS 10.14.6). (I was requiring the fs.promises module.)

    Just tested on node v12.13.0 using the example below, also doesn't seem to work. :(

    $ node

> process.env.NODE_NO_WARNINGS = 1
// 1
> process.emitWarning('something strange happened')
// (node:18941) Warning: something strange happened

> process.env.NODE_NO_WARNINGS = "1"
// "1"
> process.emitWarning('something strange happened')
// (node:18941) Warning: something strange happened

    If the node interpreter is spawned with node --no-warnings, then process.emitWarning will do nothing.

  21. squallstar commented on Jan 16, 2020

    @squallstar
    squallstar
    on Jan 16, 2020

    @hexrcs I just tested on Node v12.13.0 and I am using Mac OS 10.15.2 (19C57), works great from here.

  22. squallstar commented on Jan 16, 2020

    @squallstar
    squallstar
    on Jan 16, 2020

    @hexrcs something which you can try is to spawn a child process after the env variable has been updated. I remember doing that on previous versions of node when using commander to create a node-based CLI tool.

  23. hexrcs commented on Jan 16, 2020

    @hexrcs
    hexrcs
    on Jan 16, 2020

    @squallstar Thanks for the tip :) I've been doing similar things:

    #10802 (comment)

    OK, I just upgraded node to v12.14.1, also doesn't work... Way too weird.

    image

    Anyway, I'll keep using the child process approach for now.

  24. ErisDS commented on Apr 20, 2020

    @ErisDS
    ErisDS
    on Apr 20, 2020

    I raised this same issue here (oops): #32876 and @sam-github kindly took the time to explain there's a solution using process.removeAllListeners('warning').

  25. kevinwang5658
    added a commit that references this issue on May 4, 2024

    Updated to node 18.20. Removed warning messages from codify pkg using n…

    52a5b45
  26. enikao
    added a commit that references this issue on Jun 19, 2026

    made node runnable on linux

    acbcac6
  27. dslmeinte
    added a commit that references this issue on Jun 19, 2026

    Migrate TestLanguage generation from Deno to Node.js (#128)

    1f725a3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature requestIssues requesting new Node.js features.processIssues and PRs related to the process subsystem.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions