Use webpack for all big extensions

[jrieken]

We can ship less and gain more. This is a simple sample that enables webpack for extensions: extension.webpack.config.js. All configs should inherit from the shared config, get in touch with me if something doesn't work.

• it is important to name the file extension.webpack.config.js
• try this with npx webpack --config extensions/<your-extension>/extension.webpack.config.js
• update the .vscodeignoe file, exclude the out folder and config-file
• run a full product build via yarn run gulp vscode-darwin etc before pushing

Extensions that should be webpack'ed:

• markdown @mjbvz
• extension-editing @chrmarti
• npm @egamma
• configuration-editing @jrieken
• php @aeschli @roblourens
• merge-conflict @jrieken @chrmarti
• search-rg @roblourens

---

• 💪 node2 @roblourens
• 💪 node @weinand or @roblourens

[roblourens]

How about the debug extensions? It's more complicated because I'd have to webpack the vscode-chrome-debug-core npm module but node-debug2 is much bigger than search-rg.

chrome-debug was webpacked a long time ago but was too hard to maintain, I think it's easier now.

[jrieken]

sure, everything that reduces the bundles size is good

[jrieken]

microsoft/ApplicationInsights-node.js#426 is about making the AppInsights module (which most extension depend on via vscode-extension-telemetry) webpack friendly. Having that will reduce the bundle size drastically.

[weinand]

@jrieken how should extensions living outside of VS Code source tree "inherit from the shared config"?

[jrieken]

Yeah, that's the question. The config can be copied but more tweaks will be required because some build trickery that we do in VS Code won't be available to you.

[weinand]

Ok. I will look into that in October... Moved my first attempts to a aweinand/webpack branch