Skip to content

refactor: rename npm package to @posit-dev/shinyreact - #297

Merged
schloerke merged 1 commit into
mainfrom
schloerke/npm-package-name
Sep 10, 2026
Merged

schloerke merged 1 commit into
mainfrom
schloerke/npm-package-name

Conversation

@schloerke

Copy link
Copy Markdown
Collaborator

The npm package was named @posit/shinyreact; it should be @posit-dev/shinyreact, matching the GitHub org.

Neither name is published on npm yet (npm view 404s on both), so this is a free rename — no deprecation, no migration path.

Left alone: the @posit/shiny devDependency and the vendored upstream @posit/shiny-react (a separate, frozen artifact).

Covers all 32 tracked files that mentioned the name — pkg-js/package.json + lockfile, typedoc.json, the npm entry and error messages, the release workflow, examples/09-hmr, Python/R docstrings and .Rd files, the shipped skills (re-copied with make update-skills), FEATURES.md, DESIGN.md, the decision record, and the Quarto docs.

Verification

  • npx vitest run — 281 passed (29 files)
  • make py-check-tests — 159 passed

Note: examples/09-hmr depends on file:../../pkg-js, so an existing local node_modules/@posit/ there goes stale; npm install refreshes it.

Neither @posit/shinyreact nor @posit-dev/shinyreact is published yet, so
this is a free rename with no migration path needed. The vendored upstream
@posit/shiny-react and the @posit/shiny devDependency are untouched.
@schloerke
schloerke enabled auto-merge (squash) September 10, 2026 20:38
@schloerke
schloerke merged commit 8451cef into main Sep 10, 2026
20 checks passed
@schloerke
schloerke deleted the schloerke/npm-package-name branch September 10, 2026 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant