Version Packages (next)#965
Merged
Merged
Conversation
Deploying solid-primitives with
|
| Latest commit: |
16a43f6
|
| Status: | ⚡️ Build in progress... |
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
1 participant
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 next, this PR will be updated.
nextis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonnext.Releases
@solid-primitives/date@3.0.0-next.1
Patch Changes
5fc4efa: Fix named imports breaking under Rolldown (Vite 8+ / Storybook 10.4.6+) bundlers.
These packages re-export their public API via
export * from "./x.js"barrels. Rollup resolves named imports through these at link time, but Rolldown's static analysis doesn't reliably followexport *for named-export resolution, causing errors like:The build now also emits explicit
export { name } from "./x.js"lines for every runtime export reachable through a barrel'sexport *, derived automatically from each submodule's compiled output — sodist/is bundler-agnostic regardless of how a given tool resolves star re-exports.Updated dependencies [5fc4efa]
@solid-primitives/deep@1.0.0-next.1
Patch Changes
5fc4efa: Fix named imports breaking under Rolldown (Vite 8+ / Storybook 10.4.6+) bundlers.
These packages re-export their public API via
export * from "./x.js"barrels. Rollup resolves named imports through these at link time, but Rolldown's static analysis doesn't reliably followexport *for named-export resolution, causing errors like:The build now also emits explicit
export { name } from "./x.js"lines for every runtime export reachable through a barrel'sexport *, derived automatically from each submodule's compiled output — sodist/is bundler-agnostic regardless of how a given tool resolves star re-exports.@solid-primitives/event-bus@3.0.0-next.1
Patch Changes
5fc4efa: Fix named imports breaking under Rolldown (Vite 8+ / Storybook 10.4.6+) bundlers.
These packages re-export their public API via
export * from "./x.js"barrels. Rollup resolves named imports through these at link time, but Rolldown's static analysis doesn't reliably followexport *for named-export resolution, causing errors like:The build now also emits explicit
export { name } from "./x.js"lines for every runtime export reachable through a barrel'sexport *, derived automatically from each submodule's compiled output — sodist/is bundler-agnostic regardless of how a given tool resolves star re-exports.Updated dependencies [5fc4efa]
@solid-primitives/event-listener@3.0.0-next.1
Patch Changes
5fc4efa: Fix named imports breaking under Rolldown (Vite 8+ / Storybook 10.4.6+) bundlers.
These packages re-export their public API via
export * from "./x.js"barrels. Rollup resolves named imports through these at link time, but Rolldown's static analysis doesn't reliably followexport *for named-export resolution, causing errors like:The build now also emits explicit
export { name } from "./x.js"lines for every runtime export reachable through a barrel'sexport *, derived automatically from each submodule's compiled output — sodist/is bundler-agnostic regardless of how a given tool resolves star re-exports.Updated dependencies [5fc4efa]
@solid-primitives/filesystem@3.0.0-next.1
Patch Changes
5fc4efa: Fix named imports breaking under Rolldown (Vite 8+ / Storybook 10.4.6+) bundlers.
These packages re-export their public API via
export * from "./x.js"barrels. Rollup resolves named imports through these at link time, but Rolldown's static analysis doesn't reliably followexport *for named-export resolution, causing errors like:The build now also emits explicit
export { name } from "./x.js"lines for every runtime export reachable through a barrel'sexport *, derived automatically from each submodule's compiled output — sodist/is bundler-agnostic regardless of how a given tool resolves star re-exports.@solid-primitives/gestures@3.0.0-next.1
Patch Changes
5fc4efa: Fix named imports breaking under Rolldown (Vite 8+ / Storybook 10.4.6+) bundlers.
These packages re-export their public API via
export * from "./x.js"barrels. Rollup resolves named imports through these at link time, but Rolldown's static analysis doesn't reliably followexport *for named-export resolution, causing errors like:The build now also emits explicit
export { name } from "./x.js"lines for every runtime export reachable through a barrel'sexport *, derived automatically from each submodule's compiled output — sodist/is bundler-agnostic regardless of how a given tool resolves star re-exports.@solid-primitives/idle@1.0.0-next.1
Patch Changes
5fc4efa: Fix named imports breaking under Rolldown (Vite 8+ / Storybook 10.4.6+) bundlers.
These packages re-export their public API via
export * from "./x.js"barrels. Rollup resolves named imports through these at link time, but Rolldown's static analysis doesn't reliably followexport *for named-export resolution, causing errors like:The build now also emits explicit
export { name } from "./x.js"lines for every runtime export reachable through a barrel'sexport *, derived automatically from each submodule's compiled output — sodist/is bundler-agnostic regardless of how a given tool resolves star re-exports.Updated dependencies [5fc4efa]
@solid-primitives/mouse@4.0.0-next.1
Patch Changes
5fc4efa: Fix named imports breaking under Rolldown (Vite 8+ / Storybook 10.4.6+) bundlers.
These packages re-export their public API via
export * from "./x.js"barrels. Rollup resolves named imports through these at link time, but Rolldown's static analysis doesn't reliably followexport *for named-export resolution, causing errors like:The build now also emits explicit
export { name } from "./x.js"lines for every runtime export reachable through a barrel'sexport *, derived automatically from each submodule's compiled output — sodist/is bundler-agnostic regardless of how a given tool resolves star re-exports.Updated dependencies [5fc4efa]
@solid-primitives/props@4.0.0-next.1
Patch Changes
5fc4efa: Fix named imports breaking under Rolldown (Vite 8+ / Storybook 10.4.6+) bundlers.
These packages re-export their public API via
export * from "./x.js"barrels. Rollup resolves named imports through these at link time, but Rolldown's static analysis doesn't reliably followexport *for named-export resolution, causing errors like:The build now also emits explicit
export { name } from "./x.js"lines for every runtime export reachable through a barrel'sexport *, derived automatically from each submodule's compiled output — sodist/is bundler-agnostic regardless of how a given tool resolves star re-exports.Updated dependencies [5fc4efa]
@solid-primitives/queue@1.0.0-next.1
Patch Changes
5fc4efa: Fix named imports breaking under Rolldown (Vite 8+ / Storybook 10.4.6+) bundlers.
These packages re-export their public API via
export * from "./x.js"barrels. Rollup resolves named imports through these at link time, but Rolldown's static analysis doesn't reliably followexport *for named-export resolution, causing errors like:The build now also emits explicit
export { name } from "./x.js"lines for every runtime export reachable through a barrel'sexport *, derived automatically from each submodule's compiled output — sodist/is bundler-agnostic regardless of how a given tool resolves star re-exports.Updated dependencies [5fc4efa]
@solid-primitives/range@1.0.0-next.1
Patch Changes
5fc4efa: Fix named imports breaking under Rolldown (Vite 8+ / Storybook 10.4.6+) bundlers.
These packages re-export their public API via
export * from "./x.js"barrels. Rollup resolves named imports through these at link time, but Rolldown's static analysis doesn't reliably followexport *for named-export resolution, causing errors like:The build now also emits explicit
export { name } from "./x.js"lines for every runtime export reachable through a barrel'sexport *, derived automatically from each submodule's compiled output — sodist/is bundler-agnostic regardless of how a given tool resolves star re-exports.Updated dependencies [5fc4efa]
@solid-primitives/sensors@1.0.0-next.1
Patch Changes
5fc4efa: Fix named imports breaking under Rolldown (Vite 8+ / Storybook 10.4.6+) bundlers.
These packages re-export their public API via
export * from "./x.js"barrels. Rollup resolves named imports through these at link time, but Rolldown's static analysis doesn't reliably followexport *for named-export resolution, causing errors like:The build now also emits explicit
export { name } from "./x.js"lines for every runtime export reachable through a barrel'sexport *, derived automatically from each submodule's compiled output — sodist/is bundler-agnostic regardless of how a given tool resolves star re-exports.@solid-primitives/share@4.0.0-next.1
Patch Changes
5fc4efa: Fix named imports breaking under Rolldown (Vite 8+ / Storybook 10.4.6+) bundlers.
These packages re-export their public API via
export * from "./x.js"barrels. Rollup resolves named imports through these at link time, but Rolldown's static analysis doesn't reliably followexport *for named-export resolution, causing errors like:The build now also emits explicit
export { name } from "./x.js"lines for every runtime export reachable through a barrel'sexport *, derived automatically from each submodule's compiled output — sodist/is bundler-agnostic regardless of how a given tool resolves star re-exports.@solid-primitives/signal-builders@1.0.0-next.2
Patch Changes
5fc4efa: Fix named imports breaking under Rolldown (Vite 8+ / Storybook 10.4.6+) bundlers.
These packages re-export their public API via
export * from "./x.js"barrels. Rollup resolves named imports through these at link time, but Rolldown's static analysis doesn't reliably followexport *for named-export resolution, causing errors like:The build now also emits explicit
export { name } from "./x.js"lines for every runtime export reachable through a barrel'sexport *, derived automatically from each submodule's compiled output — sodist/is bundler-agnostic regardless of how a given tool resolves star re-exports.Updated dependencies [5fc4efa]
@solid-primitives/upload@1.0.0-next.1
Patch Changes
5fc4efa: Fix named imports breaking under Rolldown (Vite 8+ / Storybook 10.4.6+) bundlers.
These packages re-export their public API via
export * from "./x.js"barrels. Rollup resolves named imports through these at link time, but Rolldown's static analysis doesn't reliably followexport *for named-export resolution, causing errors like:The build now also emits explicit
export { name } from "./x.js"lines for every runtime export reachable through a barrel'sexport *, derived automatically from each submodule's compiled output — sodist/is bundler-agnostic regardless of how a given tool resolves star re-exports.Updated dependencies [5fc4efa]
@solid-primitives/utils@7.0.0-next.1
Patch Changes
5fc4efa: Fix named imports breaking under Rolldown (Vite 8+ / Storybook 10.4.6+) bundlers.
These packages re-export their public API via
export * from "./x.js"barrels. Rollup resolves named imports through these at link time, but Rolldown's static analysis doesn't reliably followexport *for named-export resolution, causing errors like:The build now also emits explicit
export { name } from "./x.js"lines for every runtime export reachable through a barrel'sexport *, derived automatically from each submodule's compiled output — sodist/is bundler-agnostic regardless of how a given tool resolves star re-exports.