Saving LWC doesn't push whole component, only the file you're in

[Steven Hayhurst]

I think this has been around a little while, I’ve just not bothered raising the issue as I have a workaround; but it would be nice to get a fix for this.

When working on LWC components, saving only seems to push the file you’re actually in at the time, rather than the whole component. For example, if you add a variable to the JavaScript file, then open the HTML file and reference it, then save, I get an error that the variable does not exist. If I go back into the JS file and save that, then open the HTML file and save again, this time it works.

A workaround I’ve been using is to open the Metadata file and save from there - that pushes everything. Would be nice to not have to do this though.

[Scott Wells]

Hi. This is the expected behavior when the Tooling API is enabled for LWC (or Aura) components. Deployment via the Tooling API occurs via REST to update only the current bundle file. If you prefer for the entire bundle to be updated, you can disable Tooling API-based deployment of LWC (and/or Aura) components via Illuminated Cloud > Configure Application > Validation and Deployment > Prefer Tooling API for > LWC / Aura.