fresh install of basic-host example fails
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- build-system
Research direction
Start in ext-apps/examples/basic-host by running npm install and inspect the generate-schemas.ts entry point referenced in the error. Verify that a fresh install provides ts-to-zod and that the generate-schemas command and subsequent build complete successfully.
Written by the indexing model from the issue text.
Description
Describe the bug
When getting started with the basic-host example, the generate-schemas script fails due to the package ts-to-zod not being installed.
To Reproduce
Steps to reproduce the behavior:
- clone this repo
- run
cd ext-apps/examples/basic-host - run
npm install
Logs
> tsx scripts/generate-schemas.ts && prettier --write "src/generated/**/*"
node:internal/modules/run_main:104
triggerUncaughtException(
^
Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'ts-to-zod' imported from /Users/sam/Developer/ext-apps/scripts/generate-schemas.ts
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:267:9)
at packageResolve (node:internal/modules/esm/resolve:768:81)
at moduleResolve (node:internal/modules/esm/resolve:854:18)
at defaultResolve (node:internal/modules/esm/resolve:984:11)
at nextResolve (node:internal/modules/esm/hooks:748:28)
at resolveBase (file:///Users/sam/Developer/ext-apps/node_modules/tsx/dist/esm/index.mjs?1781172307493:2:3744)
at resolveDirectory (file:///Users/sam/Developer/ext-apps/node_modules/tsx/dist/esm/index.mjs?1781172307493:2:4243)
at resolveTsPaths (file:///Users/sam/Developer/ext-apps/node_modules/tsx/dist/esm/index.mjs?1781172307493:2:4984)
at resolve (file:///Users/sam/Developer/ext-apps/node_modules/tsx/dist/esm/index.mjs?1781172307493:2:5361)
at nextResolve (node:internal/modules/esm/hooks:748:28) {
code: 'ERR_MODULE_NOT_FOUND'
}
Node.js v23.11.0
npm error code 1
npm error path /ext-apps
npm error command failed
npm error command sh -c npm run build && husky
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 387
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from modelcontextprotocol/ext-apps
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
modelcontextprotocol/ext-apps#767 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
modelcontextprotocol/ext-apps#742 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
modelcontextprotocol/ext-apps#711 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
modelcontextprotocol/ext-apps#706 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelcontextprotocol/ext-apps#703 · 1 reaction ·
All issues in modelcontextprotocol/ext-apps
Similar issues
-
blocklist removal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MetaMask/eth-phishing-detect#296544 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pastelsky/bundlephobia#1122 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
category/development priority/P2 scope/file-operations scope/testing type/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100