-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any way to reload the built-in modules? #3087
Comments
There's some functionality that was added in nodejs/node#31321. You will need to rebuild Node.js once with the |
Thank you so much! Which of these two should I execute at the top of the
Both seem to produce the same output:
|
It looks like between those two choices it would be the first as (FWIW I've never used this build feature before) |
Thank you for the help. I'll try using it. 🙂 |
After building node with this mod I figured out that I should have used the absolute path to the node git repo instead. When using node from a different location, I get this error:
I was thinking about changing this functionality a bit. Instead of fixing the path in the configuration stage maybe we can enable this feature using a binary flag and during execution node will read in the builtin modules path from an environment variable. |
@RaisinTen if you give it an absolute path you won't have that issue. |
@RaisinTen did you ever get it working? I tried running this:
but the resulting
|
@bl-ue Yes, this works for me. :) |
Ohhh... I saw that message, but I didn't read it correctly. Makes perfect sense. Thank you 👍🏻 |
Is there any way to reload the built-in modules into the node executable generated by
make
without recompiling the C++ part entirely?The text was updated successfully, but these errors were encountered: