Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / Menci/vite-plugin-wasm issues and pull requests
#59 - Error: Could not resolve "a" for @virgilsecurity/e3kit-browser
Issue -
State: open - Opened by thecannabisapp 3 months ago
#58 - Load wasm library in obsidian.md plugin using base64
Issue -
State: closed - Opened by tmayoff 4 months ago
- 1 comment
#57 - import working in dev but not production
Issue -
State: open - Opened by FUTC-Coding 7 months ago
- 1 comment
#56 - Unknown file extension ".wasm"
Issue -
State: open - Opened by RobinClowers 9 months ago
- 1 comment
#55 - `npm run build` fails to detect the plugin
Issue -
State: closed - Opened by FredrikNoren 9 months ago
- 2 comments
#54 - Wasm initialization missing using `npm run build`
Issue -
State: open - Opened by finnbear 9 months ago
- 4 comments
#53 - Error: Could not resolve "a"
Issue -
State: closed - Opened by rongaza 9 months ago
- 1 comment
#52 - Top level await support
Issue -
State: open - Opened by ESchouten 9 months ago
- 4 comments
#51 - Plugin fails to load a WASM file create with GOLANG
Issue -
State: closed - Opened by ethastings 10 months ago
- 1 comment
#50 - fix: improve CJS Interoperability
Pull Request -
State: closed - Opened by magic-akari 10 months ago
- 1 comment
#49 - cannot transform `@code-hike/lighter`
Issue -
State: closed - Opened by himself65 10 months ago
- 5 comments
#48 - Change the name
Pull Request -
State: closed - Opened by javad-seyed 10 months ago
#47 - fetch wasm file should append baseUrl base on currenScript running env
Pull Request -
State: open - Opened by joeyrenhuang 10 months ago
- 2 comments
#46 - Plugin always bundles Wasm as base64 when vitest is installed
Issue -
State: open - Opened by willcrichton 11 months ago
- 3 comments
#45 - feat: support Vite 5
Pull Request -
State: closed - Opened by wyatt-herkamp 11 months ago
- 5 comments
#44 - Vite 5 support
Issue -
State: closed - Opened by vanillajonathan 12 months ago
- 2 comments
#43 - [feature request] Support SharedArrayBuffer
Issue -
State: closed - Opened by 2A5F 12 months ago
#42 - Unable to process WASM files from web-tree-sitter
Issue -
State: closed - Opened by devi-prsd about 1 year ago
- 3 comments
#41 - Fix types for "moduleResolution": "bundler"
Pull Request -
State: closed - Opened by segevfiner about 1 year ago
#40 - 404 fetching '.wasm'
Issue -
State: closed - Opened by inzanez about 1 year ago
- 7 comments
#39 - default import is undefined (bun)
Issue -
State: closed - Opened by eye-wave about 1 year ago
- 2 comments
#38 - document is not defined without format: "es"
Issue -
State: closed - Opened by valterkraemer about 1 year ago
- 5 comments
#37 - Asynchronous module loading via top-level `await` breaks SharedWorkers "connect" event
Issue -
State: open - Opened by pvh about 1 year ago
- 6 comments
Labels: need more info
#36 - build error "Could not find a declaration file for module 'vite-plugin-wasm'"
Issue -
State: closed - Opened by hongshu7 over 1 year ago
- 1 comment
#35 - Add option to bundle .wasm file instead of inlining wasm binary as base64
Issue -
State: closed - Opened by hamza1311 over 1 year ago
- 7 comments
#34 - `Could not resolve`, `missing default export` errors in some packages
Issue -
State: closed - Opened by mima0815 over 1 year ago
- 1 comment
#33 - ERROR: No loader is configured for ".wasm" files: node_modules/.pnpm/@[email protected]/node_modules/@dqbd/tiktoken/lite/tiktoken_bg.wasm
Issue -
State: closed - Opened by happysalada over 1 year ago
- 9 comments
#32 - vite 4.x support?
Issue -
State: closed - Opened by laoshaw over 1 year ago
- 2 comments
#31 - RollupError: "default" is not exported by "node_modules/..."
Issue -
State: closed - Opened by happysalada over 1 year ago
- 3 comments
Labels: need more info
#30 - rollup fails with `id.endsWith is not a function`
Issue -
State: closed - Opened by diamondburned over 1 year ago
- 2 comments
#29 - wasm-pack npm module fails with build but not dev
Issue -
State: closed - Opened by hschimke over 1 year ago
- 6 comments
#28 - Memory import from wasm produces an error
Issue -
State: closed - Opened by BLaZeKiLL over 1 year ago
- 4 comments
#27 - how wait for async load to complete
Issue -
State: closed - Opened by BLaZeKiLL over 1 year ago
- 7 comments
#26 - esbuild plugin resolves paths incorrectly on Windows
Issue -
State: closed - Opened by qtow almost 2 years ago
- 8 comments
#25 - [SvelteKit] Importing a WASM module created by wasm-pack from a worker doen't include path prefix
Issue -
State: closed - Opened by TimoWilhelm almost 2 years ago
- 2 comments
#24 - Support status for vite-plugin-wasm and testing env
Issue -
State: open - Opened by Jerboas86 almost 2 years ago
- 12 comments
#23 - Fix `URL` name collision
Pull Request -
State: closed - Opened by Karakatiza666 almost 2 years ago
#22 - Update shields.io badge
Pull Request -
State: closed - Opened by scottbedard almost 2 years ago
#21 - wasm-pack module import is undefined
Issue -
State: closed - Opened by voxelstack almost 2 years ago
- 12 comments
#20 - Uncaught (in promise) SyntaxError: Unexpected reserved word
Issue -
State: closed - Opened by xzxzhixin almost 2 years ago
- 7 comments
#19 - using wasm with Nuxt3
Issue -
State: closed - Opened by cesarecaoduro almost 2 years ago
- 4 comments
#18 - Firefox web workers
Issue -
State: closed - Opened by segevfiner almost 2 years ago
- 3 comments
Labels: enhancement
#17 - wasm-pack WASM file. failing
Issue -
State: closed - Opened by greenpdx about 2 years ago
Labels: no-enough-information
#16 - Initial attempt at Vitest support
Pull Request -
State: closed - Opened by rossng about 2 years ago
- 5 comments
#15 - JsValue gets return value undefined
Issue -
State: closed - Opened by fredrikjacobson about 2 years ago
- 2 comments
#14 - Not found: /node_modules/.vite/deps/<package>_bg.wasm
Issue -
State: closed - Opened by Niedzwiedzw about 2 years ago
- 1 comment
#13 - Error building project with wasm in web worker
Issue -
State: closed - Opened by grahamdaley about 2 years ago
- 6 comments
Labels: enhancement
#12 - [Question] about wasm size
Issue -
State: closed - Opened by katopz about 2 years ago
- 1 comment
#11 - fix: wasm functions return undefined
Pull Request -
State: closed - Opened by sigoden about 2 years ago
- 4 comments
#10 - Rollup error: Unexpected character '' (Note that you need plugins to import files that are not JavaScript)
Issue -
State: closed - Opened by bitlands about 2 years ago
- 7 comments
#9 - Failed to resolve import "wbg" from "node_modules/.../lib_bg.wasm"
Issue -
State: closed - Opened by tedbyron over 2 years ago
- 2 comments
#8 - Error when importing WASM
Issue -
State: closed - Opened by Yaron-Ha over 2 years ago
- 6 comments
#7 - vite 3.0 error Error [ERR_REQUIRE_ESM]: require()
Issue -
State: closed - Opened by gengjiawen over 2 years ago
- 11 comments
#6 - Cannot read properties of undefined (reading 'load')
Issue -
State: closed - Opened by wanglei8381 over 2 years ago
- 5 comments
#5 - wasm-bindgen memory optimization seems to have broken the plugin
Issue -
State: closed - Opened by Secretmapper over 2 years ago
- 4 comments
#4 - SSR support
Issue -
State: closed - Opened by boyeborg over 2 years ago
- 13 comments
Labels: enhancement
#3 - fix: support decoding data URL in Node < v16
Pull Request -
State: closed - Opened by pastelmind over 2 years ago
#2 - Wrong export signature (`default`)
Issue -
State: closed - Opened by schickling over 2 years ago
- 2 comments
#1 - 拿不到wasm的返回值,所有的方法的返回值都是undefined
Issue -
State: closed - Opened by caicai1998 over 2 years ago
- 11 comments