chore(deps): bump commerce-elastic-path to 0.5.3 in the three consumers (#531) - #554
Merged
Merged
Conversation
…loader-bundle-env and the example app 0.5.3 raises the InstantSearch dependency floors (#531), which clears the ERESOLVE against React 19. The lockfiles are the load-bearing change: publish-hostless installs with --frozen-lockfile, and a ^0.5.x range already admitted the patch bump, so the manifests alone move nothing. The floors move real versions in the bundle environments, not only declarations: before after react-instantsearch-core 7.41.0 7.49.0 (7.44.1 in the example app) instantsearch.js 4.108.0 4.116.0 (4.111.1 in the example app) react-instantsearch-nextjs 0.3.21 1.4.8 react-instantsearch-nextjs is a major bump with no importer yet, so it is inlined into no bundle until SSR catalog search lands (#539). The search library itself moves eight minors inside the hostless bundle every Studio project loads; exercise search before publish-hostless runs, since --frozen-lockfile succeeding only proves it installed.
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.
Completes #531. 0.5.3 is published; this is the half that could not land before it, because these three lockfiles pin the published tarball's own dependency ranges.
The lockfiles are the load-bearing change —
publish-hostlessinstalls with--frozen-lockfile, and^0.5.xalready admitted the patch bump, so the manifests alone move nothing.What the resolve actually moved
react-instantsearch-coreinstantsearch.jsreact-instantsearch-nextjs@elasticpath/plasmic-ep-commerce-elastic-pathreact-instantsearch-nextjsis a major bump with no importer yet, so it is inlined into no bundle until SSR catalog search lands (#539).The search library itself moves eight minors inside the hostless bundle every Studio project loads. Semver-compatible and the hooks in use are stable public API, but nothing tests it: the package's catalog-search suites run under pnpm's resolution, not these lockfiles'. Worth exercising search in the browser before
publish-hostlessruns —--frozen-lockfilesucceeding only proves it installed, which is already confirmed here (yarn install --frozen-lockfileincanvas-packagesreports "Already up-to-date").Closing out #531
With this merged, the remaining acceptance criteria are met: the published package installs into React 19 + Next 15 without
ERESOLVE, the three lockfiles carry the new ranges, and the hostless publish can run against them.