Version Packages - #66
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
@intentface/chat@0.1.2
Patch Changes
#65
987e276Thanks @valstu! - Add the missing.jsextensions to single-quoted specifiers indist, whichmade the package unloadable under SSR.
add-dist-extensionsmatched only double-quoted specifiers. The vendored filesunder
src/internal/rendercame from Base UI's source and use single quotes, so21 of their relative specifiers (13 in
.js, 8 in.d.ts) shippedextensionless. Bundlers resolve those, which is why the browser was fine; Node's
ESM resolver requires fully-specified paths and threw
Cannot find module .../internal/render/useMergedRefson the first import. Everypart goes through
useRenderElement, so importing any entry point on a serverfailed — a Next or TanStack Start app rendered nothing server-side and silently
fell back to client rendering.
The pattern now captures the quote character and backreferences it, so both
styles are rewritten and the quote is preserved.
The build now ends with a smoke test that imports every subpath in
publishConfig.exportsunder Node — the entire consumer-reachable surface. Thefailure was a resolution error the rewrite script could not see (its own pattern
was the blind spot) and publint does not resolve the internal graph, so the guard
tests resolution itself: against the previous rewrite, 8 of the 11 entries fail
to load; the next regression breaks the build instead of a consumer's server.