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
Never remove cached node_modules or binary modules #1230
Conversation
Can we get this one merged into SLS offline? |
I can confirm that we've been using this fork for months, works like a charm 💯 |
Yep, problem is it's now behind master ... Be great if someone from the SLS team can approve this! @dherault ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @dl748 - could you please rebase your changes on top of current master
branch and push again?
Well rebasing didn't work, now I lost those changes. |
a6ee025
to
52d1efd
Compare
Hey @dl748 - it looks good but it's marked as draft - is it ready for a re-review? |
Thanks, @dl748, welcome to the club! |
Published in v8.6.0 (in a few hours) |
Description
Adding node_modules check to orphan unloading.
Motivation and Context
if the module in question included a binary plugin, this can cause problems when reloading. We should probably never unload a node_modules package and require the developer to restart if they update or change them. This will force any code outside of node_modules to reload which I think is acceptable, however, if the developer has their OWN binary plugin, this could still be an issue.
How Has This Been Tested?
Included a binary module into the handler that is only used there and called the handler more than once
Screenshots (if appropriate):