Conversation
A module marked `client-only` and loaded through `clientOnly(() => import(...))` failed the server build. The server build resolves every dynamic import to emit its chunk, so it resolved the client-only module and errored, even though that module never runs on the server. The resolve-time hook cannot tell a clientOnly() lazy import apart from a real server import, and throwing at eval time instead hangs the SSR stream, so `client-only` now resolves to an empty module in both environments. Client-only code that does reach the server still fails there on its own. `server-only` is unchanged and still fails a client build. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: afe53c4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
✅ Deploy Preview for solid-start-landing-page ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A module marked
client-onlyand loaded throughclientOnly(() => import(...))failed the server build. The server build resolves every dynamic import to emit its chunk, so it resolved the client-only module and errored, even though that module never runs on the server.client-onlynow resolves to an empty module in both environments, so the lazy pattern builds and SSRs. Client-only code that does reach the server still fails there on its own.server-onlyis unchanged and still fails a client build.A build-time check could not be kept: the resolve hook cannot tell a
clientOnly()lazy import from a real server import, and throwing at eval time hangs the SSR stream instead of erroring cleanly.Testing
client-onlypattern builds and SSRs 200 (was a build failure)./client-onlyroute.🤖 Generated with Claude Code