Uh oh!
There was an error while loading. Please reload this page.
module: Revert remove experimental status from JSON modules - #29754
module: Revert remove experimental status from JSON modules#29754guybedford wants to merge 4 commits into
Conversation
devsnek
left a comment
There was a problem hiding this comment.
the web's issue doesn't match our security model, I don't think we need to destabilise this
littledan
commented
Sep 29, 2019
I think it's possible that we will eventually want to use exactly this syntax for importing JSON modules in Node.js long term, for the reasons @devsnek says. However, the sad state is, we just don't know what the Web will do at this point--it is also possible that the Web may include some changes that we end up wanting to do in Node as well. So the conservative option would be to mark this as experimental again. |
devsnek
commented
Sep 29, 2019
we already do this differently than the web (with the current system you have to explicitly type in |
littledan
commented
Sep 29, 2019
Yes, I agree it's possible that it will never converge. But we haven't really done the design work on the web side so I can't personally draw a conclusion with confidence. |
nodejs-github-bot
commented
Oct 1, 2019
There was a problem hiding this comment.
It appears that this isn't valid C++ and will not compile.
EDIT: Well, this line is the start of a valid statement, but then the next few lines....you probably get what I mean. This:
20:46:37 ../src/node_options.cc: In constructor ‘node::options_parser::EnvironmentOptionsParser::EnvironmentOptionsParser()’:20:46:37 ../src/node_options.cc:321:35: error: expected ‘)’ before ‘;’ token20:46:37 kAllowedInEnvironment);20:46:37 Trott
commented
Oct 1, 2019
I'm in favor of making it experimental personally on "when in doubt, keep it experimental" grounds, but I would happily defer to Modules WG if there's consensus. Any chance this goes on the Modules WG agenda or something to come to a resolution? |
Trott
commented
Oct 1, 2019
Added the "work in progress" label. Feel free to remove once it compiles. |
39e2f6b to
683f429Compare683f429 to
67d6171Comparenodejs-github-bot
commented
Oct 1, 2019
nodejs-github-bot
commented
Oct 2, 2019
Trott
left a comment
There was a problem hiding this comment.
If a Collaborator wants to block this, I suggest making your opposition explicit with a "Request changes" review or a clear comment. As I said above, I'm generally inclined toward "leave it in experimental a bit longer" for anything where there's doubt, but there are certainly many people far more informed on this specific issue than I am....
Trott
commented
Oct 9, 2019
Landed in c0437d2 |
Trott
commented
Oct 9, 2019
@nodejs/tsc Because this restores a flag that was removed/made unnecessay in Node.js 12.4.0, is this semver-major and should not land except as part of 13.0.0? |
Trott
commented
Oct 9, 2019
Oh, wait, never mind, all of esm is experimental status so semver rules don't apply. |
Notable changes: * build: * Add `--force-context-aware` flag to prevent usage of native node addons that aren't context aware #29631 * deprecations: * Add documentation-only deprecation for `process._tickCallback()` #29781 * esm: * Using JSON modules is experimental again #29754 * fs: * Introduce `opendir()` and `fs.Dir` to iterate through directories #29349 * process: * Add source-map support to stack traces by using `--source-map-support` #29564 * tls: * Honor `pauseOnConnect` option #29635 * Add option for private keys for OpenSSL engines #28973 PR-URL: #29919
Notable changes: * build: * Add `--force-context-aware` flag to prevent usage of native node addons that aren't context aware #29631 * deprecations: * Add documentation-only deprecation for `process._tickCallback()` #29781 * esm: * Using JSON modules is experimental again #29754 * fs: * Introduce `opendir()` and `fs.Dir` to iterate through directories #29349 * process: * Add source-map support to stack traces by using `--source-map-support` #29564 * tls: * Honor `pauseOnConnect` option #29635 * Add option for private keys for OpenSSL engines #28973 PR-URL: #29919
Notable changes: * build: * Add `--force-context-aware` flag to prevent usage of native node addons that aren't context aware #29631 * deprecations: * Add documentation-only deprecation for `process._tickCallback()` #29781 * esm: * Using JSON modules is experimental again #29754 * fs: * Introduce `opendir()` and `fs.Dir` to iterate through directories #29349 * process: * Add source-map support to stack traces by using `--source-map-support` #29564 * tls: * Honor `pauseOnConnect` option #29635 * Add option for private keys for OpenSSL engines #28973 PR-URL: #29919
This reverts commit ec8776d from #27752, adding back the
--experimental-json-modulesflag to reflect the fact that JSON modules are being reverted for web (whatwg/html#4943) and should not be considered a stable feature.Tracking issue at nodejs/modules#391 with further information.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes