Uh oh!
There was an error while loading. Please reload this page.
src: add fetch to bootstrap/browser.js - #41958
Conversation
Fixes: nodejs#41816 Signed-off-by: Darshan Sen <raisinten@gmail.com>
nodejs-github-bot
commented
Feb 13, 2022
Review requested:
|
RaisinTen
commented
Feb 13, 2022
Hmm, seems to fail during the node:internal/options:20({options: optionsMap}=getCLIOptions());^
Error: ShouldnotqueryoptionsbeforebootstrappingisdoneatgetCLIOptionsFromBinding(node:internal/options:20:32)atgetOptionValue(node:internal/options:40:19)
at node:internal/bootstrap/browser:79:5
#
# Fatalerrorinv8::ToLocalChecked
# EmptyMaybeLocal.
#and the exception is coming from Line 942 in ceaa299 The bootstrap script is run during compilation but the CLI option is passed at runtime. @joyeecheung is this something we should even be doing? If so, how? |
devsnek
commented
Feb 13, 2022
options are set at runtime. bootstrapping happens at build time. if something needs to check options it should not be part of bootstrapping. |
aduh95
commented
Feb 13, 2022
I don't think this can land until we make |
RaisinTen
commented
Feb 14, 2022
Ah, yes indeed. I'm closing this because re-exposing fetch when it becomes stable should be much easier to do than fixing git conflicts in this pr. |
joyeecheung
commented
Feb 15, 2022
A trick that you can do is to add it during bootstrap unconditionally and then removing it during pre-execution when the option is not on - but yeah it’s probably still too early to do this for fetch. |
RaisinTen
commented
Feb 15, 2022
@joyeecheung yes, I did something similar in #41969. |
Fixes: #41816
Signed-off-by: Darshan Sen raisinten@gmail.com