What shipped: All @journeyapps/* npm packages in the JS SDK are being renamed to @powersync/* (e.g. @journeyapps/powersync-sdk-common → @powersync/common). This is a breaking change requiring users to update package.json dependencies and import paths. The PR itself calls out the need to update reference docs before merging.
Why this needs docs: Breaking change — all SDK installation guides, code snippets, and import examples that reference @journeyapps/* package names will be incorrect after this lands.
Likely affected pages/sections:
- All SDK installation / getting started guides — replace every
@journeyapps/* package name with the corresponding @powersync/* name across all framework-specific guides (React, React Native, Vue, Angular, etc.)
- API reference / package reference pages — update package names throughout
- Migration guide — add a dedicated section for the
@journeyapps → @powersync rename with a mapping table and step-by-step upgrade instructions
- Any code examples, snippets, or demo READMEs linked from the docs — verify all import paths are updated
Source PR: powersync-ja/powersync-js#224
CC: @benitav @DominicGBauer
What shipped: All
@journeyapps/*npm packages in the JS SDK are being renamed to@powersync/*(e.g.@journeyapps/powersync-sdk-common→@powersync/common). This is a breaking change requiring users to updatepackage.jsondependencies and import paths. The PR itself calls out the need to update reference docs before merging.Why this needs docs: Breaking change — all SDK installation guides, code snippets, and import examples that reference
@journeyapps/*package names will be incorrect after this lands.Likely affected pages/sections:
@journeyapps/*package name with the corresponding@powersync/*name across all framework-specific guides (React, React Native, Vue, Angular, etc.)@journeyapps→@powersyncrename with a mapping table and step-by-step upgrade instructionsSource PR: powersync-ja/powersync-js#224
CC: @benitav @DominicGBauer