feat: user client.response.text turn from frontend#6
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting
| "../layercode-js-sdk": { | ||
| "name": "@layercode/js-sdk", | ||
| "version": "2.2.0", | ||
| "license": "MIT", | ||
| "dependencies": { | ||
| "@ricky0123/vad-web": "^0.0.24", | ||
| "onnxruntime-web": "^1.21.1" |
There was a problem hiding this comment.
The lockfile now resolves @layercode/js-sdk from ../layercode-js-sdk and marks it as a linked package. Anyone who runs npm install in a fresh clone will fail unless they have that sibling directory available, whereas the previous lockfile pulled the dependency from the registry. This breaks reproducible installs and blocks builds for other developers. Regenerate package-lock.json so the dependency points to the published 2.2.0 package instead of a local path.
Useful? React with 👍 / 👎.
|
@codex please review |
|
Codex Review: Didn't find any major issues. Delightful! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting |
HananAlsawy
deleted the
feat-user-client.response.text-turn-from-frontend
branch
1 participant
@HananAlsawy to run
npm ibefore marking the PR ready for review