Problem

When users behind corporate proxies/firewalls can't download the LSP from CDN, the JB extension falls back to a bundled LSP. The bundled LSP currently excludes the entire indexing/ folder (~200MB), which means @file, @folder, and @code context commands don't work for these users.

Solution

Instead of deleting the entire indexing folder during bundling, selectively strip only the heavy platform-specific files that aren't needed for context commands:

• dist/bin/ — ONNX native binaries (25MB)
• dist/build/ — faiss native binaries (11MB)
• models/ — CodeSage ONNX model (124MB)

This keeps extension.js, lspServer.js, tree-sitter WASMs (~30MB uncompressed, ~3MB compressed in plugin .zip), which is everything needed for @file, @folder, @code, and BM25 cross-file context.

Testing

• Tested jb build here: https://github.com/aws/aws-toolkit-jetbrains/releases/tag/pre-jb-partial-indexing
• When unable to download LSP --> falls back to bundled LSP in build --> @code, @folder, @file now work
• Plugin size impact: ~15.3 MB --> ~18.4 MB
  • This 3 MB difference is negligible, and is necessary as this will allow affected customers to gain @code, @folder, @file functionality