| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
has nodejs/help#778 been fixed otherwise in the last 19 days? Can you explain why da1af3d is no longer required? |
Sorry, something went wrong.
There was a problem hiding this comment.
Requesting changes so I don't forget this
Sorry, something went wrong.
|
For question 1 please look at #15110 (it was only seemingly fixed but not really fixed). The initiation of global.console is not necessary anymore because that was originally done in the get of global.console and now it is done right away. That is why the test added by da1af3d continues to "work". |
Sorry, something went wrong.
There was a problem hiding this comment.
little unsure why some bits were changed?
Sorry, something went wrong.
| if (browserGlobals) { | ||
| setupGlobalTimeouts(); | ||
| setupGlobalConsole(); | ||
| } |
There was a problem hiding this comment.
It is desirable to load the console first for debugging reasons.
Sorry, something went wrong.
There was a problem hiding this comment.
Well that is a bit tricky if we want to instantiate it eagerly without the get call to do the Instantiation because internal/process/stdio has to be loaded first. Would it be fine to move the necessary part up that load stdio and keep the eager instantiation?
Sorry, something went wrong.
| const browserGlobals = !process._noBrowserGlobals; | ||
| if (browserGlobals) { | ||
| // Instantiate eagerly in case the first call is under stack overflow | ||
| // conditions where instantiation doesn't work. |
There was a problem hiding this comment.
The previous commit here still seems valid...?
Sorry, something went wrong.
There was a problem hiding this comment.
Somewhat yes, but it did not fully work as anticipated and therefore I think it is fine to remove the comment. I can add the comment back in if you like though.
Sorry, something went wrong.
| const originalConsole = global.console; | ||
| let console; | ||
| // Setup inspector command line API | ||
| const { addCommandLineAPI, consoleCall } = process.binding('inspector'); |
There was a problem hiding this comment.
needs if (!addCommandLineAPI) return;?
Sorry, something went wrong.
There was a problem hiding this comment.
Oh, you are right, this part should be moved below the if (!consoleCall) statement. That should be sufficient.
Sorry, something went wrong.
| const consoleAPIModule = new Module('<inspector console>'); | ||
| consoleAPIModule.paths = | ||
| Module._nodeModulePaths(cwd).concat(Module.globalPaths); | ||
| addCommandLineAPI('require', makeRequireFunction(consoleAPIModule)); |
There was a problem hiding this comment.
This is frankly unrelated to console instantiation. I'd prefer it to be moved out of console bootstrapping.
Sorry, something went wrong.
There was a problem hiding this comment.
I combined them because it was the only function calling the inspector. But I split them and the inspector part is now separated.
Sorry, something went wrong.
|
@nodejs/collaborators PTAL |
Sorry, something went wrong.
|
Since this should actually also fix a bug (see #15008 (comment)) it would be nice to get some reviews. |
Sorry, something went wrong.
|
LGTM if CI is happy |
Sorry, something went wrong.
Sorry, something went wrong.
PR-URL: #15111 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com>
PR-URL: #15111 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com>
PR-URL: nodejs/node#15111 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com>
PR-URL: nodejs/node#15111 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com>
Previously, console had to be compiled in case it was not available but this is no longer necessary - remove it. Refs: nodejs#15111
Previously, console had to be compiled in case it was not available but this is no longer necessary - remove it. PR-URL: nodejs#16212 Refs: nodejs#15111 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
Previously, console had to be compiled in case it was not available but this is no longer necessary - remove it. PR-URL: nodejs/node#16212 Refs: nodejs/node#15111 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
Previously, console had to be compiled in case it was not available but this is no longer necessary - remove it. PR-URL: nodejs/node#16212 Refs: nodejs/node#15111 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
|
I do not see much benefit to backport this, so I changed the label accordingly. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Console setup is currently more complicated then it has to be. I refactored it to be more straight forward.
Checklist
Affected core subsystem(s)
lib, test