chore: version packages - #255
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
@tenphi/tasty@3.0.1
Patch Changes
#254
5a176ccThanks @tenphi! - FixtastyIntegration()failing every Astro build in 3.0.0.The integration registered its middleware with
new URL('./astro-middleware.js', import.meta.url). That URL is resolved against the emitted chunk, and the v3 build hoiststastyIntegrationout ofdist/ssr/astro.jsinto a shared chunk at thedist/root — so it pointed atdist/astro-middleware.js, which does not exist, while the real file shipped atdist/ssr/astro-middleware.js. Astro now receives a package subpath instead, which is resolved through theexportsmap and cannot be invalidated by chunk layout.This also fixes
tastyIntegration({ islands: false })silently keeping the class-list transfer script. The flag was passed through module-level state written by the integration at config-load time and read by the middleware at request time — different module instances, and different processes entirely for built output, so the middleware always saw thetruedefault. Each variant now bakes its own setting in.Adds two entry points,
@tenphi/tasty/ssr/astro-middlewareand@tenphi/tasty/ssr/astro-middleware-static. They exist so Astro can resolve the middleware by specifier and are not meant to be imported directly — usetastyMiddleware()for manual middleware composition.Anyone who worked around this with a manual
src/middleware.tscan revert totastyIntegration()once on this release, or keep the manual setup — both are supported.