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
console.warn('using deprecated parameters for the initialization function; pass a single object instead')
}}
}}
{default_module_path}
Is it possible to shift this default block to the top of the function (or at least before the object destructuring)?
Alternatively, if the intention was to ensure that the default would be provided in the event that {} was provided, could you add an else if (typeof module_or_path !== 'undefined') before emitting the warning in the console? Or would you recommend swc to change the recommended way to await initSwc({});
The text was updated successfully, but these errors were encountered:
I am currently building the browser extension template project at https://github.com/Mubelotix/wasm-extension-template. When I deploy this template extension to the latest Chrome browser, I get this warning. I think it's a similar situation.
I am currently encountering this issue: swc-project/swc#9443
Seems like the
default_module_path
is performed too late, only after the object destructuring check:wasm-bindgen/crates/cli-support/src/js/mod.rs
Lines 898 to 906 in 8e66719
Is it possible to shift this default block to the top of the function (or at least before the object destructuring)?
Alternatively, if the intention was to ensure that the default would be provided in the event that
{}
was provided, could you add anelse if (typeof module_or_path !== 'undefined')
before emitting the warning in the console? Or would you recommend swc to change the recommended way toawait initSwc({})
;The text was updated successfully, but these errors were encountered: