-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
mergeWithRules
misjudges the rules.test
equivalent
#212
Comments
Can you send a PR? This package isn't maintained due to lack of funding but I can merge fixes. |
Sure, PR is on the way~ |
RexSkz
added a commit
to RexSkz/webpack-merge
that referenced
this issue
Oct 14, 2023
RexSkz
added a commit
to RexSkz/webpack-merge
that referenced
this issue
Oct 14, 2023
Yup, thanks. I will have a good look today. |
bebraw
pushed a commit
that referenced
this issue
Oct 16, 2023
bebraw
pushed a commit
that referenced
this issue
Oct 16, 2023
bebraw
pushed a commit
that referenced
this issue
Oct 16, 2023
Included in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The issue happens on the latest version of
webpack-merge
.Brief Description
Assume we have two
test
s using object:They should be converted using
less-loader
but with different options, the value ofuse[0].options.lessOptions
should be:The merge result is not as expected, because
webpack-merge
uses thetoString
result to compare thetest
value:The two results are both
"[object Object]"
, causing the latter rule to be missing and itslessOptions
to override the former one.Full Example
Run this script:
And we will get:
Suggestion
Using the deep equal (e.g.
_.isEqual
inlodash
) to compare thetest
value.The text was updated successfully, but these errors were encountered: