-
Notifications
You must be signed in to change notification settings - Fork 35
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
use object api #6
Comments
hi, @milahu looks great, would you like to create a pull request? |
nope sorry : / im only using the api could be even simpler, for example ... // vite.config.js
import wasmPack from 'vite-plugin-wasm-pack';
// use both local and npm crate
plugins: [
wasmPack(
// list of packages
[
'./my-local-crate', // local paths start with ./
'test-npm-crate',
'@org/pkg',
{ path: './a/b/c', type: 'emscripten', src: /\.(c|cc|cpp)$/ }, // local options for one packages
{ path: 'another-npm-package', type: 'makefile' },
],
// global options for all packages
{
globalOption1: '...',
globalOption2: '...',
}
),
], the |
https://github.com/milahu/vite-plugin-tree-sitter/blob/master/index.js |
I'm trying to use this plugin to see if it resolves using wasm-pack-ed packages with Quasar. Solving this issue would also allow using the plugin with the Quasar framework. The suggestion seems to me like a breaking change, though. Would that be ok? |
I tried it here: https://github.com/alensiljak/vite-plugin-wasm-pack/tree/object-params |
actual
expected
The text was updated successfully, but these errors were encountered: