Skip to content

Error loading .wasm files when using edge runtime of @sveltejs/adapter-vercel #9930

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
charlierz opened this issue May 15, 2023 · 0 comments · Fixed by #9944
Closed

Error loading .wasm files when using edge runtime of @sveltejs/adapter-vercel #9930

charlierz opened this issue May 15, 2023 · 0 comments · Fixed by #9944
Assignees

Comments

@charlierz
Copy link

Describe the bug

Similar issue to #9890, but using @sveltejs/adapter-vercel with runtime: "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

> 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)

System Info

System:
    OS: Windows 10 10.0.22621
    CPU: (16) x64 AMD Ryzen 7 7800X3D 8-Core Processor
    Memory: 15.73 GB / 31.16 GB
  Binaries:
    Node: 18.16.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.5.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22621.1702.0), Chromium (113.0.1774.42)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    @sveltejs/adapter-auto: ^2.0.0 => 2.0.1
    @sveltejs/adapter-vercel: ^2.4.3 => 2.4.3
    @sveltejs/kit: ^1.5.0 => 1.16.3
    svelte: ^3.54.0 => 3.59.1
    vite: ^4.3.0 => 4.3.6

Severity

blocking an upgrade

Additional Information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants