chore(wab): diagnostic + fixup scripts for commerce-elastic-path hostless publish failure - #399
Open
jameswillis99 wants to merge 2 commits into
Open
chore(wab): diagnostic + fixup scripts for commerce-elastic-path hostless publish failure#399jameswillis99 wants to merge 2 commits into
jameswillis99 wants to merge 2 commits into
Conversation
…hostless publish failure The commerce-elastic-path hostless project stopped publishing because plasmic-commerce-ep-add-to-cart-button dropped enableStockCheck (and other props) in the composable-components refactor (9b2e5e7), which trips updateHostlessPackage's "nothing existing may be removed" safety assertion against the project's last-published site. diagnose-commerce-elastic-path.ts reproduces updateHostlessPackage read-only to surface the real assertion message (the ECS logger drops Error.message via JSON.stringify). migrate-commerce-elastic-path.ts runs the real publish flow, retrying past the expected "Deleted param/slot" errors since the underlying sync already applies the removal correctly before the assertion fires reactively. Already run once against the non-prod DB, bumping the project's pkg_version from 0.1.0 to 0.2.0.
Explains root cause, what each script does, how to run them, and current migration status.
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
2 participants
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.
Summary
commerce-elastic-pathwith a bareAssertionError(message lost to lossy JSON logging)plasmic-commerce-ep-add-to-cart-buttondroppedenableStockCheck(and other props) in the composable-components refactor (9b2e5e777), which tripsupdateHostlessPackage's "nothing existing may be removed" safety check against the project's last-published site (2026-01-09, predates that refactor)publishHostlessProjects()runs every hostless project in one shared transaction with no per-project isolation, this one failure was blocking all hostless package publishes, not just this oneDbCustomScripts.ts, run directly) plus a README:diagnose-commerce-elastic-path.ts— read-only repro that surfaces the real assertion messagemigrate-commerce-elastic-path.ts— runs the real publish flow, retrying past the expected "Deleted param/slot" errors (the underlying sync already applies the fix correctly; the assertion just complains reactively) — no application source is modifiedCOMMERCE_ELASTIC_PATH_HOSTLESS_FIX.md— root cause writeup, usage, and status0.1.0to0.2.0. Confirmed viaproject-deps.ts's dependency-upgrade logic that any existing customer project referencing this component handles a removed prop by cleanly dropping the arg — no crash. Confirmed nothing currently relies onenableStockCheck.Test plan
migrate-commerce-elastic-path.tsagainst non-prod, verified newpkg_version(0.2.0) registers the new global-context providers and no longer containsenableStockCheck