Closed sagarchoudhary96 closed 1 year ago
@silentworks can you check it and merge this should solve the problem and also the import cost too.
@silentworks feels like this https://github.com/angus-c/just/issues/421 might be the issue with just packages which is causing this issue with the vercel build for nextjs app mostly. so as better option is to fallback and use "lodash.merge"
Closing this one out as the merge
function is probably better included in the package instead of relying on third party library.
What kind of change does this PR introduce?
This PR should fix #65 by removing the just-merge package and using only lodash.merge as dependency.
What is the current behavior?
65 issue is being caused when deploying to vercel with the new nextjs-13 version. Webpack throws issues as merge not defined.
What is the new behavior?
installed just lodash.merge as dependency and using that for merge.
Additional context
Add any other context or screenshots.