We have identified this extension as being potentially responsible for high loads in the extension host. That is likely because it runs potentially expensive minify operations in the extension host threads. That means execution of other extension features is blocked. I'd recommend, to shell out the expensive operations as we do it for linters, like vscode-eshint. See here for samples or ask @dbaeumer.
We have identified this extension as being potentially responsible for high loads in the extension host. That is likely because it runs potentially expensive minify operations in the extension host threads. That means execution of other extension features is blocked. I'd recommend, to shell out the expensive operations as we do it for linters, like vscode-eshint. See here for samples or ask @dbaeumer.