fix vscode-graphql-execution esbuild.js (#3480)

* Update esbuild.js A possibly naive way to make vscode extension work after esbuild upgrade. * Update esbuild.js Turns out I was quite naive about just excluding graphql-config. The extension worked under the Test Runner, but not when bundled and installed. This change actually does work, even when the plugin is bundled and installed separately. It uses the technique outlined in evanw/esbuild#2441 * add changeset --------- Co-authored-by: Rikki Schulte <[email protected]>
graphql · Jan 6, 2024 · a1fced1 · a1fced1
1 parent a808019
commit a1fced1
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 0 deletions.
diff --git a/.changeset/smooth-clocks-try.md b/.changeset/smooth-clocks-try.md
@@ -0,0 +1,6 @@
+---
+"vscode-graphql-execution": patch
+"vscode-graphql": patch
+---
+
+Fix execution extension esbuild bundling
diff --git a/packages/vscode-graphql-execution/esbuild.js b/packages/vscode-graphql-execution/esbuild.js
@@ -49,6 +49,10 @@ build({
  ],
  format: 'cjs',
  sourcemap: true,
+ define: { 'import.meta.url': '_importMetaUrl' },
+ banner: {
+ js: "const _importMetaUrl=require('url').pathToFileURL(__filename)",
+ },
 })
  .then(({ errors, warnings }) => {
  if (warnings.length) {