FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

(v8.x backport) src: allow CLI args in env with NODE_OPTIONS by sam-github · Pull Request #12647 · nodejs/node · GitHub

/ node Public

(v8.x backport) src: allow CLI args in env with NODE_OPTIONS - #12647

Closed
sam-github wants to merge 1 commit into
nodejs:v8.x-stagingfrom
sam-github:backport-12028-to-v8.x
Closed

(v8.x backport) src: allow CLI args in env with NODE_OPTIONS#12647
sam-github wants to merge 1 commit into
nodejs:v8.x-stagingfrom
sam-github:backport-12028-to-v8.x

Conversation

Copy link
Copy Markdown
Contributor

Backport of #12028. Conflict in doc/api/cli.md was trivial, caused by docs added adjacent to those introduced in #11968.

@jasnell not sure what status of 8.x is, but I request this feature be part of 8.x, and backported to non-maintenance versions (i.e 7.x and 6.x). Its a very useful feature for production, so I'd like it to be available in production Node.js releases.

Not all CLI options are supported, those that are problematic from a
security or implementation point of view are disallowed, as are ones
that are inappropriate (for example, -e, -p, --i), or that only make
sense when changed with code changes (such as options that change the
javascript syntax or add new APIs).

PR-URL: #12028
Reviewed-By: James M Snell jasnell@gmail.com
Reviewed-By: Michael Dawson michael_dawson@ca.ibm.com
Reviewed-By: Refael Ackermann refack@gmail.com
Reviewed-By: Gibson Fahnestock gibfahn@gmail.com
Reviewed-By: Bradley Farias bradley.meck@gmail.com

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

Not all CLI options are supported, those that are problematic from a
security or implementation point of view are disallowed, as are ones
that are inappropriate (for example, -e, -p, --i), or that only make
sense when changed with code changes (such as options that change the
javascript syntax or add new APIs).

PR-URL: nodejs#12028
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Bradley Farias <bradley.meck@gmail.com>
nodejs-github-bot added build Issues and PRs related to build files or the CI. c++ Issues and PRs that require attention from people who are familiar with C++. windows Issues and PRs related to the Windows platform. labels Apr 25, 2017
sam-github changed the base branch from master to v8.x-staging April 25, 2017 18:30

jasnell commented Apr 25, 2017

Copy link
Copy Markdown
Member

A backport PR for 8.x is not necessary. Now that this has landed in master, it will be picked up automatically the next time I sync the 8.x and 8.x-staging branches. This can be closed.

sam-github closed this Apr 26, 2017
sam-github deleted the backport-12028-to-v8.x branch October 16, 2018 17:06
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Issues and PRs related to build files or the CI. c++ Issues and PRs that require attention from people who are familiar with C++. windows Issues and PRs related to the Windows platform.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants


Back | FazBrowse Home | New Git URL