Otherwise, VS Code would assume the extension to not be properly activated until the user closed the "Buildifier not found" notification. And as long as the extension activation did not finish, there was a never-finishing "Loading" indicator on top of the "Bazel Build Targets" tree view.
Otherwise, VS Code would assume the extension to not be properly activated until the user closed the "Buildifier not found" notification. And as long as the extension activation did not finish, there was a never-finishing "Loading" indicator on top of the "Bazel Build Targets" tree view.