@graphcommerce/cli 9.0.0-canary.69 → 9.0.0-canary.71

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.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # @graphcommerce/cli
2
2
 
3
+ ## 9.0.0-canary.71
4
+
5
+ ### Patch Changes
6
+
7
+ - [#2345](https://github.com/graphcommerce-org/graphcommerce/pull/2345) [`d4ae30b`](https://github.com/graphcommerce-org/graphcommerce/commit/d4ae30ba28815ccb9d3a0478da995b7c609618e5) - Solve issue where customFetch coudn’t be loaded correctly ([@paales](https://github.com/paales))
8
+
9
+ ## 9.0.0-canary.70
10
+
3
11
  ## 9.0.0-canary.69
4
12
 
5
13
  ## 9.0.0-canary.68
package/dist/bin/mesh.js CHANGED
@@ -80,7 +80,7 @@ const main = async () => {
80
80
  const { meshConfig } = (await Promise.resolve().then(() => __importStar(require('@graphcommerce/graphql-mesh/meshConfig.interceptor'))));
81
81
  const conf = meshConfig(baseConf, graphCommerce);
82
82
  // We're configuring a custom fetch function
83
- conf.customFetch = require.resolve('@graphcommerce/graphql-mesh/customFetch');
83
+ conf.customFetch = '@graphcommerce/graphql-mesh/customFetch';
84
84
  conf.serve = { ...conf.serve, endpoint: '/api/graphql' };
85
85
  // Rewrite additionalResolvers so we can use module resolution more easily
86
86
  conf.additionalResolvers = conf.additionalResolvers ?? [];
package/package.json CHANGED
@@ -2,7 +2,7 @@
2
2
  "name": "@graphcommerce/cli",
3
3
  "homepage": "https://www.graphcommerce.org/",
4
4
  "repository": "github:graphcommerce-org/graphcommerce",
5
- "version": "9.0.0-canary.69",
5
+ "version": "9.0.0-canary.71",
6
6
  "scripts": {
7
7
  "dev": "tsc --preserveWatchOutput --watch",
8
8
  "build": "tsc",
@@ -39,11 +39,11 @@
39
39
  "tsx": "^4.16.2"
40
40
  },
41
41
  "peerDependencies": {
42
- "@graphcommerce/eslint-config-pwa": "^9.0.0-canary.69",
43
- "@graphcommerce/hygraph-cli": "^9.0.0-canary.69",
44
- "@graphcommerce/next-config": "^9.0.0-canary.69",
45
- "@graphcommerce/prettier-config-pwa": "^9.0.0-canary.69",
46
- "@graphcommerce/typescript-config-pwa": "^9.0.0-canary.69",
42
+ "@graphcommerce/eslint-config-pwa": "^9.0.0-canary.71",
43
+ "@graphcommerce/hygraph-cli": "^9.0.0-canary.71",
44
+ "@graphcommerce/next-config": "^9.0.0-canary.71",
45
+ "@graphcommerce/prettier-config-pwa": "^9.0.0-canary.71",
46
+ "@graphcommerce/typescript-config-pwa": "^9.0.0-canary.71",
47
47
  "graphql": "^16.7.1",
48
48
  "react": "^18.2.0"
49
49
  },
package/src/bin/mesh.ts CHANGED
@@ -68,7 +68,7 @@ const main = async () => {
68
68
  const conf = meshConfig(baseConf, graphCommerce)
69
69
 
70
70
  // We're configuring a custom fetch function
71
- conf.customFetch = require.resolve('@graphcommerce/graphql-mesh/customFetch')
71
+ conf.customFetch = '@graphcommerce/graphql-mesh/customFetch'
72
72
  conf.serve = { ...conf.serve, endpoint: '/api/graphql' }
73
73
 
74
74
  // Rewrite additionalResolvers so we can use module resolution more easily