Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016PFhdmTPKsQSS3fENqTi5b
🦋 Changeset detectedLatest commit: 60f3a1f 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 |
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
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.
Requested by Ryan · project thread
Problem
OpenClaw's Solid 2 migration hit this in Vitest browser mode: Vite re-optimized
@solidjs/signalsmid-run and reloaded the page, which showed up as 14 WebKit "import failures". Their workaround was adding@solidjs/signalstooptimizeDeps.includeby hand.The first optimizer pass reaches signals only through
solid-js, so it bundles signals inside thesolid-jspre-bundle. When a module the scanner never reached (a browser-mode test file, a non-literal dynamic import) then imports@solidjs/signalsby name, Vite treats it as a newly discovered dep, re-optimizes, and does a full reload.Fix
Under
serve, add@solidjs/signalstooptimizeDeps.includewhen it resolves from the project root. That is the samefindPackageDirgateresolve.dedupealready uses for it. If signals doesn't resolve from the root (pnpm's isolated layout with only a transitive dependency), the app can't import it by name anyway, and an unresolvable include entry would warn on every start. So that case is unchanged.Verified
I tested a plain Vite 8 app:
main.tsxusessolid-jsand later runsimport(/* @vite-ignore */ '/late.ts'), andlate.tsimports@solidjs/signals. I drove it with Playwright.dependency optimized: @solidjs/signals→optimized dependencies changed. reloading, and 2 navigations.solid-js.jsimports from the@solidjs_signals.jspre-bundle, so there is still one engine.There's a patch changeset.
Generated by Claude Code