Comment 1 for bug 1756292

I've been spending some time trying to hack the Makefile in order to fix this.

This seems to happen because `make doc` depends on `maas-region`, which requires the entire region server to be built in order to generate the API documentation.

The reason webpack is forced to be invoked is due to the dependency on the `bin/webpack` symlink. When the symlink is created, it's de facto state is to be *newer* than whatever its output files are. Even though bin/webpack is listed as a .SECONDARY target in the Makefile, this seems to be causing the JavaScript output files to be considered out-of-date.

I can stop the portion of this behavior that re-runs webpack by using the direct path to the (downloaded from yarn) webpack binary instead of the symlink. It's not clear if this will have any side-effects, but it seems safe.