Skip to content
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

Plugin doesn't recompile rust code on change, because watchpack never triggers 'aggregate' event #133

Open
MaxchilKH opened this issue Jun 26, 2022 · 0 comments

Comments

@MaxchilKH
Copy link

MaxchilKH commented Jun 26, 2022

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

No branches or pull requests

1 participant