rebrand: remove remaining @inferedge/moss and inferedge_moss references#161
rebrand: remove remaining @inferedge/moss and inferedge_moss references#161ashvathsureshkumar wants to merge 7 commits intomainfrom
Conversation
ashvathsureshkumar
requested review from
CoderOMaster,
HarshaNalluru,
r4ghu and
yatharthk2
as code owners
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| ## 1. Go to Moss Portal and Get API Keys | ||
|
|
||
| - Visit [usemoss.dev](https://usemoss.dev/) to sign up, create an account, confirm your email, and sign in. | ||
| - Visit [moss.dev](https://moss.dev/) to sign up, create an account, confirm your email, and sign in. |
There was a problem hiding this comment.
🚩 Partial URL migration: portal.usemoss.dev references remain across many files
The PR updates some usemoss.dev URLs to moss.dev (e.g., in getting-started.md:11, image-search/readme.md:43), but many files outside the diff still reference portal.usemoss.dev — including apps/pipecat-moss/pipecat-quickstart/README.md:20, apps/next-js/README.md:23, apps/livekit-moss-vercel/.../README.md:12, packages/pipecat-moss/README.md:14, Python bot scripts, and the LlamaIndex frontend. If the portal URL has genuinely changed, these are incomplete migrations. If portal.usemoss.dev is still valid (perhaps separate from the main site), this is intentional. Worth confirming whether the portal domain has migrated too.
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Pull request overview
This PR completes the repo-wide rebrand cleanup by replacing remaining legacy Inferedge package/import/doc references with the new Moss names and URLs, including SDK dependency updates and logo asset swaps.
Changes:
- Updated JS/TS and Python-facing documentation snippets and imports to use
@moss-dev/moss/moss. - Replaced old portal/docs/samples URLs with
moss.dev/docs.moss.dev. - Swapped remaining InferEdge logo assets for Moss equivalents and updated references.
Reviewed changes
Copilot reviewed 57 out of 62 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
sdks/javascript/bindings/Cargo.toml |
Fixes npm install comment to the correct @moss-dev/moss-core package. |
packages/vitepress-plugin-moss/package.json |
Updates published files list and switches dependency to @moss-dev/moss. |
packages/vitepress-plugin-moss/moss-logo.png |
Adds Moss logo asset used by the plugin UI. |
packages/vitepress-plugin-moss/demo-site/documentation/docs/reference/** |
Bulk-renames generated reference docs headers/breadcrumbs/install snippets to the new package names. |
packages/vitepress-plugin-moss/demo-site/documentation/docs/{index,getting-started}.md |
Updates portal URLs and install/import examples to new Moss package names. |
packages/vitepress-plugin-moss/demo-site/documentation/MAINTAINERS.md |
Updates the listed Python reference-docs source path (but command/path details need correction—see comment). |
packages/vitepress-plugin-moss/Search.vue |
Updates type/runtime imports to @moss-dev/moss and swaps the logo import. |
packages/vitepress-plugin-moss/README.md |
Updates runtime SDK reference to @moss-dev/moss. |
packages/pipecat-moss/README.md |
Updates docs URL to docs.moss.dev. |
moss-live-labs/examples/image-search/readme.md |
Updates portal URL to moss.dev. |
moss-live-labs/examples/image-search/react-app/src/pages/ItemsPage.tsx |
Updates logo paths to Moss asset. |
apps/pipecat-moss/pipecat-quickstart/README.md |
Updates docs URL to docs.moss.dev. |
apps/next-js/package.json |
Switches dependency from @inferedge/moss to @moss-dev/moss. |
apps/next-js/package-lock.json |
Updates lockfile to reflect the new SDK package and dependency graph changes. |
apps/next-js/app/actions.ts |
Updates import to @moss-dev/moss. |
apps/next-js/app/actions.test.ts |
Updates module mock to @moss-dev/moss. |
apps/next-js/README.md |
Updates install instructions to @moss-dev/moss. |
apps/livekit-moss-vercel/livekit-voice-agent/livekit-moss-agent/README.md |
Updates Moss link to moss.dev. |
README.md |
Updates badges/links to new npm/PyPI identifiers. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| | --- | --- | --- | | ||
| | `docs/reference/js/**/*` | `javascript/user-facing-sdk/typedoc.json` | `npm run docs` (inside `javascript/user-facing-sdk/`) | | ||
| | `docs/reference/python/**/*` | `python/user-facing-sdk/src/inferedge_moss/__init__.pyi` | `python scripts/generate_docs.py` (inside `python/user-facing-sdk/`) | | ||
| | `docs/reference/python/**/*` | `sdks/python/sdk/src/moss/__init__.pyi` | `python scripts/generate_docs.py` (inside `sdks/python/sdk/`) | |
There was a problem hiding this comment.
The MAINTAINERS table now points Python reference docs generation at sdks/python/sdk/src/moss/__init__.pyi, but the command python scripts/generate_docs.py (inside sdks/python/sdk/) appears to be incorrect: there is no scripts/ directory or generate_docs.py in sdks/python/sdk/. Please update this entry (and the regeneration workflow section below, which still references python/user-facing-sdk) to the actual path/command used to regenerate docs/reference/python/**/* from the current Python SDK.
| [](https://opensource.org/licenses/BSD-2-Clause) | ||
| [](https://pypi.org/project/moss/) | ||
| [](https://pepy.tech/project/inferedge-moss-core) | ||
| [](https://pepy.tech/project/moss) |
There was a problem hiding this comment.
We will be using inferedge-moss-core as the core package downloads indicator.
| [](https://pepy.tech/project/moss) | ||
| [](https://www.npmjs.com/package/@moss-dev/moss) | ||
| [](https://www.npmjs.com/package/@inferedge/moss) | ||
| [](https://www.npmjs.com/package/@moss-dev/moss) |
There was a problem hiding this comment.
Lets make this change once our @moss-dev/moss installs reach critical number and/or crosses our old package installs.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
|
next-js and vitepress are using the webpackage of moss. |
| @@ -1,8 +1,8 @@ | |||
| [**@inferedge/moss v1.0.0-beta.7**](../README.md) | |||
| [**@moss-dev/moss v1.0.0-beta.7**](../README.md) | |||
There was a problem hiding this comment.
beta version does not exist for this package
| --- | ||
|
|
||
| [inferedge-moss v1.0.0b16](../README.md) | ||
| [moss v1.0.0b16](../README.md) |
There was a problem hiding this comment.
no beta version for this package
| }, | ||
| "dependencies": { | ||
| "@inferedge/moss": "^1.0.0-beta.7", | ||
| "@moss-dev/moss": "^1.0.0", |
There was a problem hiding this comment.
@moss-dev/moss-web needs to be used.
Please test the app before merging.
| }, | ||
| "dependencies": { | ||
| "@inferedge/moss": "^1.0.0-beta.7", | ||
| "@moss-dev/moss": "^1.0.0", |
There was a problem hiding this comment.
I think we need @moss-dev/moss-web here
Three follow-ups from PR review: 1. Revert README badge slugs for PyPI downloads and npm downloads per @r4ghu. The download counters should continue to reflect the old `inferedge-moss-core` / `@inferedge/moss` packages until the new `moss` / `@moss-dev/moss` installs reach critical volume. Keeps the PyPI version + npm version badges (the top-of-page links) pointing at the new packages. 2. Revert the MAINTAINERS.md Python doc-source path change. The old entry pointed at `python/user-facing-sdk/src/inferedge_moss/__init__.pyi` and my previous edit moved it to `sdks/python/sdk/src/moss/__init__.pyi`, but Copilot correctly flagged that the regen command (`python scripts/generate_docs.py`) doesn't exist in the current repo — neither script nor script dir are present anywhere under `sdks/`. The whole regen workflow is stale in ways beyond this rebrand; leaving the path as it was so it's obviously-stale for the docs team to rewrite properly, rather than half-updated. 3. Regenerate `packages/vitepress-plugin-moss/pnpm-lock.yaml` via `pnpm install --lockfile-only`. The previous commit renamed the `@inferedge/moss` dep in package.json but didn't refresh the lock, so `pnpm install --frozen-lockfile` would have failed in CI (Devin flag). Lock now cleanly references `@moss-dev/moss` with zero `@inferedge` entries. Not addressed (out of scope for this PR): - `packages/vitepress-plugin-moss/demo-site/package-lock.json` has 2 pre-existing `@inferedge/moss` refs. That file exists on `main` before this PR, the demo-site is a pnpm workspace (pnpm-lock.yaml is the active lockfile and is clean), and npm can't even regenerate it because it uses `link:..` for the workspace dep. Orphan from a prior npm-era install; leaving for separate cleanup. - `portal.usemoss.dev` references throughout — intentionally preserved per the rebrand policy decision.
|
Addressed review feedback in @r4ghu — reverted both download-counter badge slugs per your guidance. @Copilot — good catch on MAINTAINERS.md. Verified: @devin-ai-integration — regenerated The secondary Partial-portal-URL-migration flag acknowledged but intentional: per the rebrand decision, |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
|
Round 2 of review fixes in @HarshaNalluru / @yatharthk2 — you were right,
@HarshaNalluru on the reference-doc version labels — fixed:
Verification:
All other |
| napi-derive = "3.0.0" | ||
| # The `moss` crate is not included in this repository. | ||
| # Pre-built binaries are available on npm: npm install @anthropic-ai/moss-core | ||
| # Pre-built binaries are available on npm: npm install @moss-dev/moss-core |
There was a problem hiding this comment.
🚩 Cargo.toml comment references @moss-dev/moss-core — may need verification
The comment in sdks/javascript/bindings/Cargo.toml:18 was changed from @anthropic-ai/moss-core to @moss-dev/moss-core. This is a comment-only change and doesn't affect the build, but @moss-dev/moss-core should be verified as the correct published npm package name for the pre-built native binaries. The rest of the PR uses @moss-dev/moss-web for the high-level SDK, so @moss-dev/moss-core for the low-level bindings seems plausible but worth confirming.
Was this helpful? React with 👍 or 👎 to provide feedback.
Sweep of leftover old-name references after the rename to Moss. Touches
READMEs, badges, demo-app manifests, import statements across TS/JS/Vue
and Python, generated TypeDoc reference docs in the vitepress plugin
demo-site, and dead InferEdge logo assets.
- @inferedge/moss -> @moss-dev/moss
- inferedge_moss -> moss (Python imports)
- inferedge-moss -> moss (PyPI deps)
- @anthropic-ai/moss-core copy-paste typo -> @moss-dev/moss-core
(sdks/javascript/bindings/Cargo.toml)
- pepy.tech badge slug inferedge-moss-core -> moss (root README + org
profile README badges)
- npmjs.com/package/@inferedge/moss -> @moss-dev/moss (badge links)
- docs.usemoss.dev -> docs.moss.dev (prose-only)
- usemoss.dev root-domain prose links -> moss.dev
- github.com/usemoss/moss-samples (404s) -> github.com/usemoss/moss
- InferEdgeLogo_Dark_Icon.png (vitepress plugin + moss-live-labs image
search) replaced with the canonical assets/moss-logo.png; dead PNGs
removed
- MAINTAINERS.md doc-source path updated to match current layout
(sdks/python/sdk/src/moss/)
- Generated TypeDoc reference docs under packages/vitepress-plugin-moss/
demo-site/documentation/docs/reference/{js,python}/ — bulk-renamed
header and breadcrumb text
- inferedge-moss-core Rust bindings distribution name in
sdks/python/bindings/pyproject.toml
- inferedge-moss-core==0.8.7 transitive dep pin in sdks/python/sdk/
pyproject.toml (moss-core on PyPI is only at 0.2.3 and has an
incompatible API)
- @inferedge-rest/moss (target @moss-dev/moss-rest package doesn't
exist yet; left in README dependency-split prose and in
packages/moss-md-indexer/src/uploader.ts)
- InferEdge Inc. legal-entity references in copyright comments and in
apps/moss-llamaindex/frontend/components/common/footer.tsx
- portal.usemoss.dev and service.usemoss.dev subdomains
- Historical changelog lines ('previously published as inferedge-moss',
'Initial release of @inferedge/moss') in sdks/python/sdk/CHANGELOG.md
and sdks/javascript/sdk/CHANGELOG.md
- apps/next-js: clean npm install + tsc --noEmit passes against the
new @moss-dev/moss dep
- Full-repo grep for remaining stale strings (excluding -core, the
historical changelogs, @inferedge-rest, and node_modules/lockfiles)
returns zero hits
The previous sweep rewrote `github.com/usemoss/moss-samples/blob/main/
{python,javascript}/*` to `github.com/usemoss/moss/blob/main/
{python,javascript}/*`. Those paths 404 because the sample files live
under `examples/` in the current repo layout. Corrected to
`examples/{python,javascript}/*` — all four paths now return 200.
Three follow-ups from PR review: 1. Revert README badge slugs for PyPI downloads and npm downloads per @r4ghu. The download counters should continue to reflect the old `inferedge-moss-core` / `@inferedge/moss` packages until the new `moss` / `@moss-dev/moss` installs reach critical volume. Keeps the PyPI version + npm version badges (the top-of-page links) pointing at the new packages. 2. Revert the MAINTAINERS.md Python doc-source path change. The old entry pointed at `python/user-facing-sdk/src/inferedge_moss/__init__.pyi` and my previous edit moved it to `sdks/python/sdk/src/moss/__init__.pyi`, but Copilot correctly flagged that the regen command (`python scripts/generate_docs.py`) doesn't exist in the current repo — neither script nor script dir are present anywhere under `sdks/`. The whole regen workflow is stale in ways beyond this rebrand; leaving the path as it was so it's obviously-stale for the docs team to rewrite properly, rather than half-updated. 3. Regenerate `packages/vitepress-plugin-moss/pnpm-lock.yaml` via `pnpm install --lockfile-only`. The previous commit renamed the `@inferedge/moss` dep in package.json but didn't refresh the lock, so `pnpm install --frozen-lockfile` would have failed in CI (Devin flag). Lock now cleanly references `@moss-dev/moss` with zero `@inferedge` entries. Not addressed (out of scope for this PR): - `packages/vitepress-plugin-moss/demo-site/package-lock.json` has 2 pre-existing `@inferedge/moss` refs. That file exists on `main` before this PR, the demo-site is a pnpm workspace (pnpm-lock.yaml is the active lockfile and is clean), and npm can't even regenerate it because it uses `link:..` for the workspace dep. Orphan from a prior npm-era install; leaving for separate cleanup. - `portal.usemoss.dev` references throughout — intentionally preserved per the rebrand policy decision.
@HarshaNalluru and @yatharthk2 pointed out that the correct npm package for browser / WebAssembly usage is `@moss-dev/moss-web` (not the Node SDK `@moss-dev/moss`). Applied the correction in the two subtrees that run in a browser: - apps/next-js: package.json dep, actions.ts import, actions.test.ts vi.mock, README install command -> @moss-dev/moss-web. Regenerated package-lock.json. Also fixed a pre-existing type mismatch now surfaced by the new SDK: `results.timeTakenInMs` -> `timeTakenMs` (the new SearchResult shape). - packages/vitepress-plugin-moss: package.json dep, Search.vue (static + dynamic imports), README dependency-split prose -> @moss-dev/moss-web. Regenerated pnpm-lock.yaml. - packages/vitepress-plugin-moss/demo-site getting-started.md and index.md JS install commands and imports -> @moss-dev/moss-web. - Generated TypeDoc reference docs under packages/vitepress-plugin-moss/demo-site/documentation/docs/reference/: - js/*: renamed @moss-dev/moss -> @moss-dev/moss-web and dropped the inherited v1.0.0-beta.7 version suffix down to v1.0.0 (moss-web has no betas published) - python/*: dropped the inherited v1.0.0b16 -> v1.0.0 (moss@1.0.0 is the only version on PyPI; same flag from @HarshaNalluru on reference/python/classes/MossClient.md) Verification: - `npm install` + `npx tsc --noEmit` on apps/next-js: clean - `pnpm install --lockfile-only` on packages/vitepress-plugin-moss: clean; lock now has 3 @moss-dev/moss-web entries and zero non-hyphen @moss-dev/moss entries All other @moss-dev/moss references in the repo (SDK source, Node demo apps like moss-bun, docker/javascript, the Vercel SDK, test fixtures, moss-live-labs TypeScript examples, root README code snippet, etc.) are Node contexts and stay on @moss-dev/moss — those are not browser usage.
Re-ran `npm install` in apps/next-js and `pnpm install --lockfile-only` in packages/vitepress-plugin-moss after rebasing onto main. Main picked up dependabot bumps (#159) and the new examples/javascript-web/ directory (#162) while this branch was open; this commit makes both lockfiles consistent with the current package.json deps.
ashvathsureshkumar
force-pushed
the
rebrand/inferedge-to-moss
branch
from
a85c35e to
07134ba
Compare
There was a problem hiding this comment.
🚩 Pre-existing: Search.vue passes raw number instead of QueryOptions to query()
At Search.vue:321-322, the code reads topk as a number and passes it directly as the third argument to mossClient.value.query(). All @moss-dev/moss-web examples (e.g., examples/javascript-web/load_and_query_sample.ts:54) pass { topK: 3 } as a QueryOptions object. Additionally, the option is read as (options.value as any).topk (lowercase k) while types.ts:9 defines it as topK (camelCase), so the config value would never be found and always fall back to 20. This is a pre-existing issue not introduced by this PR, but the import switch to @moss-dev/moss-web makes it worth noting in case the new SDK is stricter about argument types.
Was this helpful? React with 👍 or 👎 to provide feedback.
The @moss-dev/moss-web SDK uses `timeTakenMs` on SearchResult, not the old `timeTakenInMs`. Earlier in this PR I updated the source in actions.ts but missed the matching property in the test mock, so the 'returns success with docs and timeTaken' case read `undefined` from the mock and CI failed. Mock now produces `timeTakenMs: 42`, test passes locally (3/3).
There was a problem hiding this comment.
🚩 Two distinct JS SDK packages documented differently across pages
The getting-started guide (getting-started.md:31) tells users to npm install @moss-dev/moss-web, while the JS SDK reference (reference/js/README.md:24) says npm install @moss-dev/moss. These are intentionally different packages: @moss-dev/moss-web is the browser/WASM SDK, and @moss-dev/moss is the Node.js SDK (confirmed by sdks/javascript/sdk/CHANGELOG.md:8 which states "Node-only: Dropped browser/WASM support"). However, the getting-started page links directly to the JS reference docs at line 149: [JavaScript SDK](/reference/js/README.md). A user following the getting-started flow would install the web SDK but then land on docs for the Node.js SDK, which has slightly different APIs (e.g., timeTakenInMs vs timeTakenMs). This could cause confusion.
Was this helpful? React with 👍 or 👎 to provide feedback.
Devin correctly flagged that my previous commit was internally inconsistent: the headers of `reference/js/**/*.md` got renamed to `@moss-dev/moss-web` but the underlying interface definitions (e.g. SearchResult.timeTakenInMs) still come from the Node SDK's typedoc output. The two packages have slightly different APIs — moss-web uses timeTakenMs, moss (Node) uses timeTakenInMs — so mislabelled headers would send users reading property tables down the wrong path. The correct target is the package the typedoc actually ran against, which is `@moss-dev/moss` (Node). Pinning the reference docs to `@moss-dev/moss v1.0.1` (the current latest on npm, no beta) keeps the header consistent with the content. Separately, @HarshaNalluru's guidance that `apps/next-js` and `packages/vitepress-plugin-moss/Search.vue` should use `@moss-dev/moss-web` is unchanged — those files stay on moss-web (the browser/WASM runtime).
|
Round 3 fixes — thanks @devin-ai-integration: Devin (2026-04-21T01:42, SearchResult.md:22 and globals.md:1) — correct catch. My previous commit relabelled the generated JS ref-doc headers to App code unchanged: Devin (README.md:24 install/import mismatch) — resolved by the same revert. Install is now Devin (Cargo.toml:18 @moss-dev/moss-core verification) — verified: Devin (Search.vue:322 query signature) — pre-existing pattern difference across Search.vue vs actions.ts, not introduced by this PR. Leaving untouched; flag it on a future API-consistency pass. Devin (earlier actions.ts:36 timeTakenMs-is-wrong) — Devin self-resolved in the 01:42 pass after inspecting the new |
| <div className="hero-header-inner"> | ||
| <img | ||
| src="/images/InferEdgeLogo_Dark_Icon.png" | ||
| src="/Moss-logo.jpeg" |
There was a problem hiding this comment.
I dont see the new named image in public/images
Summary
Full sweep of leftover old-name references left in this repo after the rename from Inferedge to Moss. 62 files changed across READMEs, demo-app manifests, Python and TS/JS imports, Vue assets, generated TypeDoc reference docs in the vitepress-plugin-moss demo-site, and dead InferEdge logo assets.
Renames applied
@inferedge/moss(npm)@moss-dev/mossinferedge_moss(Python import)mossinferedge-moss(PyPI dep)moss@anthropic-ai/moss-core(copy-paste typo insdks/javascript/bindings/Cargo.toml)@moss-dev/moss-coreinferedge-moss-core(root + org-profile README)moss@inferedge/moss(root + org-profile README)@moss-dev/mosshttps://docs.usemoss.dev(prose)https://docs.moss.devhttps://usemoss.dev/https://www.usemoss.dev(root-domain prose only)https://moss.devgithub.com/usemoss/moss-samples(404s)github.com/usemoss/mossInferEdgeLogo_Dark_Icon.png(packages/vitepress-plugin-moss/+moss-live-labs/examples/image-search/react-app/)assets/moss-logo.png/ existingMoss-logo.jpeg; dead PNGs removedinferedge_moss/__init__.pyipath inMAINTAINERS.mdsdks/python/sdk/src/moss/__init__.pyiGenerated TypeDoc reference docs under
packages/vitepress-plugin-moss/demo-site/documentation/docs/reference/{js,python}/had their header text, breadcrumb links, and install-command snippets bulk-renamed. The next regeneration run will overwrite these anyway; this just stops them from shipping stale.Not changed (intentional, flag for follow-up)
inferedge-moss-coreRust-bindings distribution name insdks/python/bindings/pyproject.toml.inferedge-moss-core==0.8.7transitive dep pin insdks/python/sdk/pyproject.toml.moss-coreon PyPI is only at 0.2.3 and the API is incompatible.@inferedge-rest/mossinpackages/moss-md-indexer/src/uploader.tsand in README dependency-split prose — target@moss-dev/moss-restdoesn't exist yet on npm.InferEdge Inc.legal-entity references in copyright comments and inapps/moss-llamaindex/frontend/components/common/footer.tsx.portal.usemoss.devandservice.usemoss.devsubdomains — leave per rebrand decision.Verification
apps/next-js: freshnpm installinstalls@moss-dev/mosscleanly;npx tsc --noEmitpasses.@inferedge/moss | inferedge_moss | inferedge-moss(excluding-core, the two SDK changelogs,@inferedge-rest/moss, andnode_modules/ lockfiles) returns zero hits.docs.usemoss.devreturns zero prose hits.InferEdgeLogoreturns zero references from code (the remaining match is an incidental byte sequence insideapps/moss-llamaindex/frontend/public/Icon.pngbinary data).Audit context
Part of the full-surface Moss rebrand audit. Sibling PRs: