Rename project to OwlSQL (@owlsql/core)#14
Conversation
Renamed the project and npm package. "TypeSQL" was the original pick but an
existing, actively-maintained project with the same name and nearly
identical pitch already exists (github.com/wsporto/typesql) - checked before
committing to anything, landed on OwlSQL instead, verified free on npm and
no existing project collision.
Scoped as @owlsql/core (not a bare "owlsql") specifically so a future real
split into separate driver/tool packages doesn't require renaming again -
but this is a naming decision only, the package structure is unchanged
(adapters and the ts-plugin stay as subpath exports, e.g. @owlsql/core/pg,
same as before).
- package.json: name -> @owlsql/core, bin -> owlsql, version -> 0.1.4
(continuing the existing version history rather than resetting), added
repository/homepage/bugs pointing at the upcoming renamed GitHub repo.
- README/COMPARISON.md/CONTRIBUTING.md: prose and code samples updated,
distinguishing narrative mentions ("OwlSQL ships...") from literal
package references (`@owlsql/core`, `npx @owlsql/core generate` - not
`npx owlsql generate`, since a bare unscoped npx call would try to fetch a
nonexistent package before anything's installed locally).
- CLI usage string, cosmetic temp-dir-prefix strings in three test files.
Verified against a real build: full test suite green under the new name,
plus a separate throwaway project installing the freshly-built local
package and importing both @owlsql/core and @owlsql/core/pg with zero type
errors, not just a visual diff check.
Still pending (not done here, deliberately): renaming the GitHub repository
itself, creating the owlsql org on npmjs.com, and the actual npm publish
under the new name - all separate, higher-blast-radius actions.
The repo is now tiagolauer/OwlSQL (confirmed via gh repo view) - matching casing in package.json's repository/homepage/bugs fields instead of the lowercase guess from before the rename happened.
|
Warning Review limit reached
Next review available in: 7 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (8)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Summary
Renames the project and npm package from
sql-template-typedto OwlSQL (@owlsql/core)."TypeSQL" was the original pick, but an existing, actively-maintained project with the same name and a nearly identical pitch already exists (github.com/wsporto/typesql, generates typesafe TypeScript APIs from raw SQL, supports Postgres/MySQL/SQLite/LibSQL/D1) — checked before committing to anything, landed on OwlSQL instead. Verified free on npm (
owlsqland@owlsql/coreboth) and no existing project collision found.Scoped as
@owlsql/core(not a bareowlsql) specifically so a future real split into separate driver/tool packages doesn't require renaming again — but this PR is a naming decision only. Package structure is unchanged: adapters and the ts-plugin stay as subpath exports (@owlsql/core/pg,@owlsql/core/ts-plugin, etc), same as before.package.json: name →@owlsql/core, bin →owlsql, version →0.1.4(continuing the existing version history rather than resetting to 0.1.0), addedrepository/homepage/bugspointing at the GitHub repo (already renamed totiagolauer/OwlSQL— confirmed viagh repo view, casing matched).@owlsql/core,npx @owlsql/core generate— notnpx owlsql generate, since a bare unscopednpxcall would try to fetch a nonexistent package before anything's installed locally).Test plan
npm run test:types && npm run test:runtime— full suite green under the new name (47 tests)@owlsql/coreand@owlsql/core/pg— 0 type errors, not just a visual diff checkStill pending (not this PR)
owlsqlorg on npmjs.com and publishing under the new scoped name — account-level action, stays the maintainer's call.github-polishbranch (ROADMAP.md, example projects) predates this rename and still needs its naming swept — follow-up PR.