Skip to content

Commit c8e8b4f

Browse files
authored
Update README.md (#107)
1 parent 546f507 commit c8e8b4f

File tree

1 file changed

+3
-12
lines changed

1 file changed

+3
-12
lines changed

README.md

Lines changed: 3 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -29,29 +29,20 @@ We have [contributed a tentative implementation](https://github.com/MCP-UI-Org/m
2929

3030
## Installation
3131

32-
This repo is in flux and isn't published to npm yet. When it is, it will use the `@modelcontextprotocol/ext-apps` package.
33-
34-
In the meantime you can depend on the SDK library in a Node.js project by installing it with its git URL:
35-
3632
```bash
37-
npm install -S git+https://github.com/modelcontextprotocol/ext-apps.git
33+
npm install -S @modelcontextprotocol/ext-apps
3834
```
3935

40-
Your `package.json` will then look like:
36+
Or edit your `package.json` manually:
4137

4238
```json
4339
{
4440
"dependencies": {
45-
"@modelcontextprotocol/ext-apps": "git+https://github.com/modelcontextprotocol/ext-apps.git"
41+
"@modelcontextprotocol/ext-apps": "^0.0.1"
4642
}
4743
}
4844
```
4945

50-
> [!NOTE]
51-
> The build tools (`esbuild`, `tsx`, `typescript`) are in `dependencies` rather than `devDependencies`. This is intentional: it allows the `prepare` script to run when the package is installed from git, since npm doesn't install devDependencies for git dependencies.
52-
>
53-
> Once the package is published to npm with pre-built `dist/`, these can be moved back to `devDependencies`.
54-
5546
## Examples
5647

5748
Start with these foundational examples to learn the SDK:

0 commit comments

Comments
 (0)