Skip to content

Update README.md #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dewana-sl wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update README.md #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 0 additions & 10 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,16 +19,6 @@
<img src="https://img.shields.io/badge/Web-Browser%20%7C%20Node.js-3178C6" alt="Browser and Node.js">
Copy link
Copy Markdown

@greptile-apps greptile-apps Bot May 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Developer-preview disclaimer removed — confirm API is stable

The removed blockquote stated "Developer preview. APIs may change between releases." If the library is still in an early/unstable phase, dropping this notice could lead consumers to assume API stability they should not assume, leading to surprise breaking changes between releases. Please confirm the API has stabilised before removing this warning, or replace it with a versioned stability guarantee (e.g. SemVer commitment).

Copy link
Copy Markdown

@greptile-apps greptile-apps Bot May 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Production CDN/self-hosting guidance removed

The deleted note explained that ONNX Runtime wasm assets are loaded from a CDN by default and that ortWasmPath can be set to self-host them for supply-chain or offline scenarios. This is actionable information for production users — without it, there is no hint in the docs that CDN loading happens or that it can be overridden. Consider moving this content to a dedicated "Configuration" or "Production" section rather than dropping it entirely.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

</p>

> Developer preview. APIs may change between releases.

> Browser apps use ONNX Runtime Web and browser storage. Node.js apps use ONNX
> Runtime Web with filesystem storage by default.

> Browser ONNX Runtime wasm assets are loaded from the matching ONNX Runtime Web
> CDN by default. For production apps that need CDN independence or stricter
> supply-chain controls, self-host those ONNX Runtime assets and set
> `ortWasmPath`.

## See It In Action

<p align="center">
Expand Down