Fix: ensure splitting is disabled in esbuild configuration

[alexweininger]

Seeing if this fixes #1352

[Copilot]

Pull request overview

This PR addresses issue #1352 where the Azure panel fails to load after installing the Azure Resources extension with an Azure Functions project open. The fix explicitly disables code splitting in the esbuild configuration to prevent VS Code from encountering issues when loading the extension bundles.

Changes:

• Added splitting: false to the esbuild configuration to prevent esbuild from creating separate code chunks

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[bwateratmsft]

Approved, but are we sure it's the splitting that's causing the problem?

In any case, there will be splitting done with the telemetry bundle, so it can't be avoided altogether.

[alexweininger]

Approved, but are we sure it's the splitting that's causing the problem?

In any case, there will be splitting done with the telemetry bundle, so it can't be avoided altogether.

I think it is caused by splitting. But it's a VS Code bug that allows the extension to start loading before everything from the VSIX is unpacked... speculation here

[alexweininger]

I'm going to have Jing/CTI test this out before merging to see if this fixes it.

[bwateratmsft]

Sounds good. We should have CTI check the folder to see if that file exists after the error has appeared, or if it's still gone...

[alexweininger]

Sounds good. We should have CTI check the folder to see if that file exists after the error has appeared, or if it's still gone...

Good idea

[bwateratmsft]

This is strange...the format should be 'cjs' by default...

[alexweininger]

Very strange. The splitting false option didn't work unless this was also set. Not sure why but Copilot suggested it and it works :)