You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Point @lynx-js/source-field at src/index.ts, so a bundler in this repo can (#3404)
resolve the package without waiting for its dist/.
@lynx-js/css-serializer has no build script - its dist/ is emitted by the
repository's root tsc --build, which is a separate turbo task with no ordering
relationship to any package's build. That was invisible while every consumer
was itself type-checked rather than bundled, but @lynx-js/web-core bundles its
client with rspack, and rspack resolving main: dist/index.js before the root
build has emitted it fails outright.
@rsbuild/plugin-source-build is already how this repository answers that - @lynx-js/web-elements and @lynx-js/web-worker-rpc declare the same field and
are consumed straight from source. Declaring it here removes the ordering
question rather than scheduling around it.
The field is inert outside such a build: it is a plain, unknown top-level package.json key, so no exports map is introduced and no existing entry point
or deep import changes.
Replace node:path with pathe in generateHref so the package can be bundled for browsers. (#3401)
Hrefs resolved from a projectRoot or filename containing a backslash change, because pathe normalizes Windows separators on every platform. Pure POSIX inputs, including the defaults, are unaffected.
Configuration
📅 Schedule: (UTC)
Branch creation
At any time (no schedule defined)
Automerge
At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
If you want to rebase/retry this PR, check this box
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
renovateBot
changed the title
fix(deps): update dependency @lynx-js/css-serializer to v0.1.8
fix(deps): update dependency @lynx-js/css-serializer to v0.1.9
Aug 25, 2026
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
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 contains the following updates:
0.1.7→0.1.9Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
lynx-family/lynx-stack (@lynx-js/css-serializer)
v0.1.9Compare Source
Patch Changes
Point
@lynx-js/source-fieldatsrc/index.ts, so a bundler in this repo can (#3404)resolve the package without waiting for its
dist/.@lynx-js/css-serializerhas nobuildscript - itsdist/is emitted by therepository's root
tsc --build, which is a separate turbo task with no orderingrelationship to any package's
build. That was invisible while every consumerwas itself type-checked rather than bundled, but
@lynx-js/web-corebundles itsclient with rspack, and rspack resolving
main: dist/index.jsbefore the rootbuild has emitted it fails outright.
@rsbuild/plugin-source-buildis already how this repository answers that -@lynx-js/web-elementsand@lynx-js/web-worker-rpcdeclare the same field andare consumed straight from source. Declaring it here removes the ordering
question rather than scheduling around it.
The field is inert outside such a build: it is a plain, unknown top-level
package.jsonkey, so noexportsmap is introduced and no existing entry pointor deep import changes.
v0.1.8Compare Source
Patch Changes
Replace
node:pathwithpatheingenerateHrefso the package can be bundled for browsers. (#3401)Hrefs resolved from a
projectRootorfilenamecontaining a backslash change, becausepathenormalizes Windows separators on every platform. Pure POSIX inputs, including the defaults, are unaffected.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.