You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> Using @sveltejs/adapter-vercel
X [ERROR] No loader is configured for".wasm" files: node_modules/@dqbd/tiktoken/tiktoken_bg.wasm
node_modules/@dqbd/tiktoken/tiktoken.js:1:22:
1 │ import * as wasm from "./tiktoken_bg.wasm";
╵ ~~~~~~~~~~~~~~~~~~~~
error during build:
Error: Build failed with 1 error:
node_modules/@dqbd/tiktoken/tiktoken.js:1:22: ERROR: No loader is configured for".wasm" files: node_modules/@dqbd/tiktoken/tiktoken_bg.wasm
at failureErrorWithLog (C:\Users\crinc\Development\wasm-vercel-edge-runtime\node_modules\esbuild\lib\main.js:1636:15)
at C:\Users\crinc\Development\wasm-vercel-edge-runtime\node_modules\esbuild\lib\main.js:1048:25
at C:\Users\crinc\Development\wasm-vercel-edge-runtime\node_modules\esbuild\lib\main.js:993:52
at buildResponseToResult (C:\Users\crinc\Development\wasm-vercel-edge-runtime\node_modules\esbuild\lib\main.js:1046:7)
at C:\Users\crinc\Development\wasm-vercel-edge-runtime\node_modules\esbuild\lib\main.js:1075:16
at responseCallbacks.<computed> (C:\Users\crinc\Development\wasm-vercel-edge-runtime\node_modules\esbuild\lib\main.js:697:9)
at handleIncomingPacket (C:\Users\crinc\Development\wasm-vercel-edge-runtime\node_modules\esbuild\lib\main.js:752:9)
at Socket.readFromStdout (C:\Users\crinc\Development\wasm-vercel-edge-runtime\node_modules\esbuild\lib\main.js:673:7)
at Socket.emit (node:events:513:28)
at Socket.emit (node:domain:489:12)
Describe the bug
Similar issue to #9890, but using
@sveltejs/adapter-vercel
withruntime: "edge"
When building a project that uses wasm modules the following error is returned:
[ERROR] No loader is configured for ".wasm" files: node_modules/@dqbd/tiktoken/tiktoken_bg.wasm
Reproduction
https://github.com./charlierz/wasm-vercel-edge-runtime
Logs
System Info
Severity
blocking an upgrade
Additional Information
No response
The text was updated successfully, but these errors were encountered: