chat-sample run error

[Aoyia]

Extension sample

chat-sample

VS Code version

1.90.0

What went wrong?

The operation is as follows:
git clone https://github.com/microsoft/vscode-extension-samples.git
cd chat-sample
npm i
npm run watch

errot message:

[10:37:24] File change detected. Starting incremental compilation...

node_modules/@vscode/prompt-tsx/dist/base/index.d.ts:1:22 - error TS6053: File '/Users/xxx/Desktop/aoyi/vscode-extension-samples/chat-sample/src/base/vscode.proposed.lmTools.d.ts' not found.

1 ///
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

view screenshots

[dehilsterlexis]

I have the same problem. It was working June 7, 2024.

[ntrogh]

Can you try to update to the latest version of prompt-tsx in the package.json and do an npm install?

[in0ho1no]

I also encountered the same issue today.
My environment was WSL2 + Docker.

In my case, I resolved it with the following steps:

1. Add the following to the Dockerfile and rebuild the container:
   RUN npm install -g @vscode/prompt-tsx
2. Navigate to the root of the chat-sample directory.
3. Run npm install.

[dehilsterlexis]

1. npm install -g @vscode/prompt-tsx

I tried npm install -g @vscode/prompt-tsx after the regular install. I getting the same error still which is identical to the first person;s screenshot in this issue. It was working on the end of last week.

[ntrogh]

@dehilsterlexis In the package.json, can you make sure to use the latest prompt-tsx version: "@vscode/prompt-tsx": "^0.2.3-alpha"
Then make sure to do an npm install to pull in that latest version.

[dehilsterlexis]

That worked! I'm back in business. Thanks!

[in0ho1no]

I also encountered the same issue today. My environment was WSL2 + Docker.

In my case, I resolved it with the following steps:

1. Add the following to the Dockerfile and rebuild the container:
   RUN npm install -g @vscode/prompt-tsx
2. Navigate to the root of the chat-sample directory.
3. Run npm install.

I apologize. When I followed my steps again, it did not work.

Following the steps provided by ntrogh and using the latest version of prompt-tsx resolved the issue.

[ntrogh]

We have a PR to fix this. Thanks for raising this issue!