-
-
Notifications
You must be signed in to change notification settings - Fork 742
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
Fixing problem with NCC #268
Conversation
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.
This offers better consistency, both packages were being used previously (one occurences of merge-deep
and two of deepmerge
). Luckily, there is a test for the change you've done.
Please take a look at my question(s) addressed and clean up - if neccessary.
@@ -64,7 +64,7 @@ | |||
}, | |||
"dependencies": { | |||
"debug": "^4.1.1", | |||
"merge-deep": "^3.0.2", | |||
"deepmerge": "^4.2.2", |
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.
Is this dependency needed at all for the recaptcha plugin? I don't see any reference to it.
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.
It's being used on line 77 to merge the passed opts with the defaults
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.
As @jozsi pointed out, this is not being used on the recaptcha plugin, therefore the dependency can most likely be removed.
After doing some testing with deepmerge, and puppeteer-extra I found out an issue with deepmerge that it's probably a blocker to use deepmerge, because it does not work with Set and we are using set here
I created an issue in deepmerge about this: TehShrike/deepmerge#202 |
I tried to use object-merge-advanced, but I ran into the same issue as merge-deep. Any thoughts on how to move forward? One possible alternative is to use this fork, which I made to merge-deep and it fixes the issue with NCC. Thoughts? |
What's the latest on this, is there a drop in replacement that works with Sets a well? |
@berstend I think using deepmerge with Do you want me to make update to this PR to using deepmerge with |
@itsdarrylnorris apologies for the "slight" delay on this 😄 This will be fixed in #303, with this commit. |
Problem:
I am having an issue compiling a project using puppeteer-extra-plugin-stealth with NCC.
After some investigation, it looks like the problem it's related to a sub-dependency of the package merge-deep. I created a PR to fix this particular problem in the merge-deep jonschlinkert/merge-deep#14. However, that project does not look like it has been active for the last two years, and I wonder if my PR will even get merge.
Here is the NCC issue explaining the problem: vercel/ncc#500