joaoh82 / rust_sqlite / 24912288973
69%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 29
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 66.922%. Remained the same
24912288973

push

github

web-flow 
Rename npm package to @joaoh82/sqlrite (scoped) (#30)

The unscoped `sqlrite` name on npm was rejected during the v0.1.5
canary setup with:

  403 Forbidden — Package name too similar to existing packages
  sqlite, sqlite3; try renaming your package to '@joaoh82/sqlrite'
  and publishing with 'npm publish --access=public' instead.

Levenshtein distance between "sqlrite" and "sqlite" is 1, which
trips npm's similar-names check. This is a registry-side policy,
not something we can work around with a suffix — `sqlrite-db`,
`sqlrite-node`, etc. all share the same stem and would hit the
same check.

**Switch to `@joaoh82/sqlrite`** — npm's own recommended fix, and
the standard pattern in the Node ecosystem (`@napi-rs/canvas`,
`@aws-sdk/client-s3`, `@swc/core`, `@types/*`). Scoped names
bypass the similarity check because the scope itself is a
namespace. The scope `@joaoh82` is auto-owned by the author's
npm user account, so no additional reservation step needed.

**Paralleling the crates.io workaround:** this is the same
registry-forced rename pattern we hit with `sqlrite-engine` on
crates.io (the `sqlrite` name there was taken by an unrelated
RAG-SQLite wrapper). Different registries, different reasons,
same pragmatic outcome — rename the *package* while keeping the
Rust import alias stable inside the codebase.

Files touched (12):

  Source & manifests:
    sdk/nodejs/package.json        — name: "@joaoh82/sqlrite"
    sdk/nodejs/package-lock.json   — refreshed via npm install
    sdk/nodejs/Cargo.toml          — description + comment
    sdk/nodejs/src/lib.rs          — module doc-comment

  Workflows:
    .github/workflows/release.yml  — npm URL + install/require
                                     snippets in release body,
                                     comment block explaining
                                     --access public requirement

  Docs:
    README.md                      — Phase 6c runbook summary
    docs/embedding.md             ... (continued)

4012 of 5995 relevant lines covered (66.92%)

1.23 hits per line

Jobs
ID Job ID Ran Files Coverage
1 24912288973.1 29
66.92
 GitHub Action Run
Source Files on build 24912288973