This resolves an issue which arrived as part of 1.1.0 esbuild changes whereby the package.json that was being considered was the top-level one (not the module one) and the population of the 'external' definition in esbuild (telling it what NOT to bundle) was therefore fumbled.
This resolves an issue which arrived as part of 1.1.0 esbuild changes whereby the package.json that was being considered was the top-level one (not the module one) and the population of the 'external' definition in esbuild (telling it what NOT to bundle) was therefore fumbled.