Update README.md#2
Conversation
Removed the top disclaimers
|
| Filename | Overview |
|---|---|
| README.md | Removed three blockquote callouts: the developer-preview stability warning, the browser/Node storage model note, and the CDN/self-hosting guidance for ONNX Runtime wasm assets including the ortWasmPath option. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[README.md before] -->|Removed| B["> Developer preview warning"]
A -->|Removed| C["> Browser/Node.js storage model note"]
A -->|Removed| D["> ONNX Runtime CDN / ortWasmPath guidance"]
A -->|Kept| E[Badges, See It In Action, rest of README]
B & C & D -.->|deleted in this PR| X[No longer in README]
Reviews (1): Last reviewed commit: "Update README.md" | Re-trigger Greptile
| @@ -19,16 +19,6 @@ | |||
| <img src="https://img.shields.io/badge/Web-Browser%20%7C%20Node.js-3178C6" alt="Browser and Node.js"> | |||
There was a problem hiding this comment.
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).
| @@ -19,16 +19,6 @@ | |||
| <img src="https://img.shields.io/badge/Web-Browser%20%7C%20Node.js-3178C6" alt="Browser and Node.js"> | |||
There was a problem hiding this comment.
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!
Removed the top disclaimers