-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Fix build.client
and build.server
resolve behaviour
#11916
Conversation
🦋 Changeset detectedLatest commit: e0e65e1 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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 PR is blocked because it contains a major
changeset. A reviewer will merge this at the next release if approved.
Co-authored-by: Florian Lefebvre <[email protected]>
The previous one was correct because we started the paragraph with an example
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 currently documented" is my favourite kind of feature add! 😆
Amazing change set, just a couple of tiny tweaks for you! 💜
Co-authored-by: Sarah Rainsberger <[email protected]>
Thanks for the review! |
Changes
Ensure that
build.client
andbuild.server
will actually resolve relative to theoutDir
as currently documented. The changesets have extra information of the previous behaviour.Testing
Existing tests should pass. I also remove the previously set
build.client
andbuild.server
options as the workaround is no longer needed.Docs
Added changesets explaining the breaking change.