chore: 0.1.1 package metadata for npm search - #57
Merged
Merged
Conversation
Add description, keywords, repository, homepage, and bugs so npm view no longer falls back to README HTML. Bump version to 0.1.1. Co-authored-by: Darwin <darekaze@users.noreply.github.com>
Match current main after #19–#21/#40 and #50/#52: document waitForReady / hasSynced / waitForFirstSync as the status contract, describe native httpFetch as the live path, and keep remaining limits (Explorer, desktop recipes, abort-before-headers residual). Co-authored-by: Darwin <darekaze@users.noreply.github.com>
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.
FM-PS-LYNX-019 — package searchability + version bump for 0.1.1, plus README sync-status refresh.
Await captain merge instruction. Do not merge without it.
Why
npm view powersync-lynx descriptioncurrently returns README HTML (<div align="center" markdown>) becausepackage.jsonhad nodescriptionfield, so npm fell back to the README.Sync caveats in the root README were written while #19–#21 / #40 (status UX) and #50/#52 (packed web-host + abort-before-headers) were still in flight. Those lands are on
main; the README now matches current behavior.Changes
package.jsonmetadataversion:0.1.0→0.1.1description: plain-text GitHub repo description (not README HTML)keywords: GitHub topics (powersync,lynx,lynxjs,sqlite,offline-first,local-first,sync,typescript,reactlynx,android,ios,wasm)repository:git+https://github.com/countertek/powersync-lynx.githomepage:https://github.com/countertek/powersync-lynxbugs.url:https://github.com/countertek/powersync-lynx/issuesREADME
waitForReady/waitForFirstSync/waitForStatus(s => s.connected)).httpFetch+streamingId/onData*→onEnd), not an open caveat. Dropped “rebuild after pulling streaming changes” and the fix(sync): abort native streams, drop iOS 150s cap, release earlyEvents #36 leftover cite.hasSynced/lastSyncedAtvs this-sessionconnected/ download evidence.NativePowerSyncModule; Windows/macOS recipe-only (desktop not a full Autolink product path); native abort-before-headers residual (JS settlement may precede native cancel until thestreamingIdCallback — ADR 0003); demo tokens are static HS256 JWT.No export, install-graph, or backlog implementation changes.