| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
I dunno how to get around some of this dependancy injection for now... Maybe add these to process and then remove them after boot?
Sorry, something went wrong.
|
(fixed linting) |
Sorry, something went wrong.
There was a problem hiding this comment.
Why do you need NativeModule? I think you can just use require at this point
Sorry, something went wrong.
There was a problem hiding this comment.
@vkurchatkin We don't want this in the regular module cache.
Sorry, something went wrong.
There was a problem hiding this comment.
what do you mean? require and NativeModule.require are literally the same thing in built-in modules: https://github.com/nodejs/node/blob/master/src/node.js#L1004
Sorry, something went wrong.
There was a problem hiding this comment.
Ooooh good catch
Sorry, something went wrong.
|
Very interesting! This should go a long way towards clearing things up. It might be worthwhile to CC folks from NW.js and electron to make sure this is compatible with their projects, but if so I'm generally in favor of this. |
Sorry, something went wrong.
There was a problem hiding this comment.
(Looks like my previous comment got squashed)
I dunno how to get around some of this dependancy injection for now... Maybe add these to process and then remove them after boot?
Sorry, something went wrong.
|
Thanks for CCing @chrisdickinson @Fishrock123 . It's fine for NW.js. |
Sorry, something went wrong.
|
Rebased on master. I have work that will be sitting ontop of this since it's easier to tell what needs modification, and as such I'd sorta like to get this merged. cc @trevnorris |
Sorry, something went wrong.
There was a problem hiding this comment.
could be made const.
EDIT: nope. sorry.
Sorry, something went wrong.
|
going to add the ctc meeting tag. only b/c it relocates so much code, would like a decisive ok from everyone. |
Sorry, something went wrong.
|
sigh I should have added it today. Already CC'd everyone though with almost no response? |
Sorry, something went wrong.
|
Sorry, saw the ctc mention just hadn't had any time to review. Will look
|
Sorry, something went wrong.
|
And before anyone asks, yes this is totally just moving some code around, that's the point haha. :P |
Sorry, something went wrong.
|
At a high level this LGTM if CI is green. |
Sorry, something went wrong.
|
Could you point to where you think it could be semver-major? Do addons need the file location? I've already heard from two embedders (nw.js and N|Solid) that this doesn't cause significant issues either. |
Sorry, something went wrong.
|
As I said, I'm just being conservative. It shouldn't break anything but it's worth being cautious. One impact this will have is changing the stack trace on certain errors, e.g: bash-3.2$ node ~/tmp/test.js
events.js:154
throw er; // Unhandled 'error' event
^
Error: foo
at Object.<anonymous> (/Users/james/tmp/test.js:5:17)
at Module._compile (module.js:413:34)
at Object.Module._extensions..js (module.js:422:10)
at Module.load (module.js:357:32)
at Function.Module._load (module.js:314:12)
at Function.Module.runMain (module.js:447:10)
at startup (node.js:139:18)
at node.js:999:3
bash-3.2$
While that shouldn't have an impact, I think it's at least worth being cautious. I've kicked off a CITGM run here: https://ci.nodejs.org/job/thealphanerd-smoker/66/ |
Sorry, something went wrong.
This is not so terribly uncommon and I definitely do not think we guarantee stacktraces. That's like guaranteeing lib/internal APIs. See: https://github.com/nodejs/node/commits/master/test/message -- 8830797 modifies the same traces but is scheduled for LTS. |
Sorry, something went wrong.
|
Grrr... CITGM smoke testing is currently broken due to the npm/graceful-fs issue on master. |
Sorry, something went wrong.
|
Also see @rvagg's comment here: #5092 (comment) ... so I'm not alone in my caution on this. |
Sorry, something went wrong.
|
The one failure appears to be unrelated. Land it! |
Sorry, something went wrong.
PR-URL: nodejs#5103 Reviewed-By: Trevor Norris <trev.norris@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: nodejs#5103 Reviewed-By: Trevor Norris <trev.norris@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: nodejs#5103 Reviewed-By: Trevor Norris <trev.norris@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
|
landed, thanks everyone! |
Sorry, something went wrong.
Clarify comments re invoking bootstrap_node.js. Fix filename to bootstrap_node.js per nodejs#5103. Fix tests `node.js` -> `bootstrap_node.js` Fix comment on why we check the loop again before exiting. `context-inl.h` -> `env-inl.h`
PR-URL: nodejs#5103 Reviewed-By: Trevor Norris <trev.norris@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Conflicts: node.gyp src/node.js
PR-URL: nodejs#5103 Reviewed-By: Trevor Norris <trev.norris@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: nodejs#5103 Reviewed-By: Trevor Norris <trev.norris@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #5103 Reviewed-By: Trevor Norris <trev.norris@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #5103 Reviewed-By: Trevor Norris <trev.norris@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #5103 Reviewed-By: Trevor Norris <trev.norris@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #5103 Reviewed-By: Trevor Norris <trev.norris@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #5103 Reviewed-By: Trevor Norris <trev.norris@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #5103 Reviewed-By: Trevor Norris <trev.norris@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
| Back | FazBrowse Home | New Git URL |
Ok so, this is definitely a bit nuts. Just a bit. Well, the second commit that is.
I figure what this costs us in the short term will be made up for by ease of contribution in the future.
This PR is mostly about the first set of changes. Although I'd also like to do the second. src/node.js is very big and it's fairly hard to figure out what you all might need to change for any specific patch.
CI: https://ci.nodejs.org/job/node-test-pull-request/1562/
R=@nodejs/ctc