[ci] release#2
Merged
Merged
Conversation
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@tinloof/tanstack-wsr@0.1.2
Patch Changes
1a9a9ba: Fix
/sw.jsbuild failing for apps with server routes or server-only imports.The worker bundle now reproduces TanStack Start's full client transform, not
just the server-fn compiler. Pure-server routes (a
createFileRoutewith only aserverhandler) and their server-only dependencies (DB clients, auth libraries,etc.) are pruned from the worker graph exactly as in the app's own client build,
so they never reach
/sw.js.Previously the worker pulled those handlers in and the build crashed with
environment.transformRequest is not a function. Root cause: the server-fncompiler was forced into dev mode (for dev-matching function ids) inside a
build()that has notransformRequest, and its dev module loader then chokedon cross-module server imports (e.g. an auth lib).
Now route pruning removes those server-only modules from the graph first, so dev
mode is safe again — the dev-mode forcing is kept (scoped to the server-fn
compiler, dev only) so that server functions called during the in-worker render
still get dev-matching ids and work in dev. Production is unchanged (both worker
and origin use build-mode sha256 ids). Route pruning applies to the default
router-derived entry; a custom
entry(advanced) still gets server-fncompilation alone.