Skip to content

Plugin doesn't respect webpack watchOptions? Spawns new compilation without canceling? #130

@EndilWayfare

Description

@EndilWayfare

Every time a change is detected, a new compilation is started even if one is already running.

I'm using rust-analyzer in VS Code, so turning off aggressive auto-save also turns off error checking and linting. But with auto-save on, webpack also wants to rebuild the WASM every few keystrokes. I'm using pure Rust (with yew), so there's no funny business with JS framework interactions (a la NextJS SSR).

I tried using watchOptions.aggregateTimeout to debounce the watcher, but that only seems to apply to non-Rust files.

It would be awesome if the Rust compilation could be debounced, or at least if in-flight compilations could be cancelled so they're not competing for resources when I stop typing and there's like 5 of them. 😄 It's entirely possible that I'm just missing something and have misconfigured.

I'm using the latest wasm-pack-plugin@1.6.0 and the latest webpack 4

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions