search

ricky0123 / vad

Voice activity detector (VAD) for the browser with a simple API
https://www.vad.ricky0123.com
Other
909 stars 144 forks source link

Issue compiling - maybe related to pnpm #135

Open matmill5 opened 2 months ago

matmill5 commented 2 months ago

Next.js (14.2.5) out of date (learn more) (turbo) ./node_modules/.pnpm/onnxruntime-web@1.19.2/node_modules/onnxruntime-web/dist/ort.min.js:1802:6893 Module not found 1800 | Shader source: 1801 | ${e}`);return r}deleteShader(e){this.gl.deleteShader(e)}bindTextureToUniform(e,o,t){let r=this.gl;r.activeTexture(r.TEXTURE0+o),this.checkError(),r.bindTexture(r.TEXTURE_2D,e),this.checkError(),r.uniform1i(t,o),this.checkError()}draw()

I am getting this error.

It looks like the path is wrong: node_modules nested inside of node_modules...

It may be related to nextjs' turbo functionality? Not sure.

Please advise

jorgekorgut commented 2 months ago

I had the same problem when I accidentally run pnpm update. This command updated onnxruntime-web to 1.19 and the vad stopped working. I dont know why :/. A workaround to this issue was pnpm install --workspace-root onnxruntime-web@1.18.0 at the root of the project, delete node_modules and pnpm-lock.yaml and run pnpm install again.

winterdelta commented 1 month ago

I had the same problem when I accidentally run pnpm update. This command updated onnxruntime-web to 1.19 and the vad stopped working. I dont know why :/. A workaround to this issue was pnpm install --workspace-root onnxruntime-web@1.18.0 at the root of the project, delete node_modules and pnpm-lock.yaml and run pnpm install again.

This worked for me - thanks!