houdini 1.0.0-next.22 → 1.0.0-next.23

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -78683,8 +78683,8 @@ async function updatePackageJSON(targetPath) {
78683
78683
  }
78684
78684
  packageJSON.devDependencies = {
78685
78685
  ...packageJSON.devDependencies,
78686
- houdini: "^1.0.0-next.22",
78687
- "houdini-svelte": "^1.0.0-next.22"
78686
+ houdini: "^1.0.0-next.23",
78687
+ "houdini-svelte": "^1.0.0-next.23"
78688
78688
  };
78689
78689
  await fs_exports.writeFile(packagePath, JSON.stringify(packageJSON, null, 4));
78690
78690
  }
@@ -78688,8 +78688,8 @@ async function updatePackageJSON(targetPath) {
78688
78688
  }
78689
78689
  packageJSON.devDependencies = {
78690
78690
  ...packageJSON.devDependencies,
78691
- houdini: "^1.0.0-next.22",
78692
- "houdini-svelte": "^1.0.0-next.22"
78691
+ houdini: "^1.0.0-next.23",
78692
+ "houdini-svelte": "^1.0.0-next.23"
78693
78693
  };
78694
78694
  await fs_exports.writeFile(packagePath, JSON.stringify(packageJSON, null, 4));
78695
78695
  }
@@ -196,7 +196,7 @@ export type PluginHooks = {
196
196
  }) => string;
197
197
  /**
198
198
  * A hook to customize the return type of the graphql function. If you need to add an import to the file
199
- * in order to resolve the import, you can use the `ensure_import` utility.
199
+ * in order to resolve the import, you can use the `ensureImport` utility.
200
200
  */
201
201
  graphqlTagReturn?: (args: {
202
202
  config: Config;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "houdini",
3
- "version": "1.0.0-next.22",
3
+ "version": "1.0.0-next.23",
4
4
  "description": "The disappearing GraphQL clients",
5
5
  "keywords": [
6
6
  "typescript",