Skip to content
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

Do not clone config objects #12

Merged
merged 2 commits into from
Jan 5, 2021
Merged

Do not clone config objects #12

merged 2 commits into from
Jan 5, 2021

Conversation

jnv
Copy link
Contributor

@jnv jnv commented Dec 28, 2020

Fixes #2.

Also fix docs on passing plugin options via next-compose-plugins.

@jnv
Copy link
Contributor Author

jnv commented Dec 28, 2020

Actually, defaultsDeep doesn't seem to be a correct replacement for deepmerge, because it merges arrays as well: lodash/lodash#2802 (comment)

@jnv jnv marked this pull request as draft December 28, 2020 15:03
next-compose-plugins require a nested array to pass plugin-specific options.
@jnv jnv changed the title Use lodash's defaultsDeep for Next config Do not clone config objects Dec 28, 2020
@jnv jnv marked this pull request as ready for review December 28, 2020 15:40
@jnv
Copy link
Contributor Author

jnv commented Dec 28, 2020

As explained in #2 (comment) I kept using deepmerge. I have only added clone: false option to fix the experimental warning.

@KidkArolis KidkArolis merged commit 6ba6d87 into humaans:master Jan 5, 2021
@KidkArolis
Copy link
Contributor

Thanks so much!

@jnv jnv deleted the defaultsdeep branch January 6, 2021 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Move config into an internal object instead of piggy backing on next config
2 participants