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
One possible solution is to move watchpacks initialization into apply and pass it watchOptions from the config. That would also solve issues like #130 and potential issues with setups requiring polling.
$ wasm-pack --version
wasm-pack 0.10.3
The text was updated successfully, but these errors were encountered:
@wasm-tool/[email protected]
doesn't recompile on Rust source code change, which is expected, because Watchpack never triggers 'aggregate' event.Form what i understand it's happening because according to Watchpacks readme it's not going to trigger one if
aggregateTimeout
is undefined, but the plugin creates an instance without any options specified.One possible solution is to move watchpacks initialization into
apply
and pass itwatchOptions
from the config. That would also solve issues like #130 and potential issues with setups requiring polling.The text was updated successfully, but these errors were encountered: