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.

Sign up for GitHub

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

Jump to bottom

feat(config): add configOverrides for loadNuxt and loadNuxtConfig #7263

Merged
merged 4 commits into from
Apr 24, 2020
Merged

feat(config): add configOverrides for loadNuxt and loadNuxtConfig #7263

merged 4 commits into from
Apr 24, 2020

Conversation

clarkdo
Copy link
Member

@clarkdo clarkdo commented Apr 23, 2020 •
edited

Types of changes

  • Bug fix (a non-breaking change which fixes an issue)
  • New feature (a non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Description

Add configOverrides on loadNuxtConfig to make overriding config during loadNuxt possible.

BTW, @pi0 https://github.com/nuxt/serve-placeholder needs a release to use defu v2.

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly. (PR: #)
  • I have added tests to cover my changes (if not applicable, please state why)
  • All new and existing tests are passing.

@clarkdo clarkdo requested a review from pi0 April 23, 2020 19:52
pi0
pi0 previously approved these changes Apr 23, 2020
View reviewed changes
@clarkdo clarkdo merged commit 1ce8041 into dev Apr 24, 2020
@clarkdo clarkdo deleted the load-nuxt-config branch April 24, 2020 09:00
@pi0 pi0 mentioned this pull request Jun 10, 2020
Merged
@danielroe danielroe added the 2.x label Jan 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@pi0 pi0 pi0 left review comments

Assignees
No one assigned
Labels
2.x
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@clarkdo @pi0 @danielroe