@graphcommerce/graphql-mesh 9.0.0 → 9.0.1-canary.1

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.
Files changed (2) hide show
  1. package/CHANGELOG.md +10 -101
  2. package/package.json +4 -4
package/CHANGELOG.md CHANGED
@@ -1,9 +1,19 @@
1
1
  # Change Log
2
2
 
3
+ ## 9.0.1-canary.1
4
+
3
5
  ## 9.0.0
4
6
 
7
+ ### Major Changes
8
+
9
+ - [#2330](https://github.com/graphcommerce-org/graphcommerce/pull/2330) [`bc3ec5e`](https://github.com/graphcommerce-org/graphcommerce/commit/bc3ec5e439b97cea4a2cef23e4008c7e0cfd6797) - Created a new `@graphql-mesh` plugin to forward headers from backends as `forwardedHeaders` in extensions. ([@paales](https://github.com/paales))
10
+
5
11
  ### Minor Changes
6
12
 
13
+ - [#2309](https://github.com/graphcommerce-org/graphcommerce/pull/2309) [`b46e17e`](https://github.com/graphcommerce-org/graphcommerce/commit/b46e17ebe390b4d0040639dfdac33c36a60576ac) - When generating the mesh the configuration is passed through `@graphcommerce/graphql-mesh/meshConfig` allowing plugins to modify the mesh configuration without having to change the `.meshrc.yaml` itself. ([@Renzovh](https://github.com/Renzovh))
14
+
15
+ ### Patch Changes
16
+
7
17
  - [#2380](https://github.com/graphcommerce-org/graphcommerce/pull/2380) [`3710d8b`](https://github.com/graphcommerce-org/graphcommerce/commit/3710d8bf1cceb5a991e5cfdfc15d42e462704c6d) - Solves the issue `TypeError: url?.startsWith is not a function`. The generated `.mesh/index.ts` would be generated as a requirejs module while next.js expects an esm module. In the end we properly generated the mesh correctly and now there is an `import.meta.url` instead of using `require('node:url')`. To solve this we needed to solve a chain of issues:
8
18
 
9
19
  1. The generation of the mesh is based on the version of the mesh that is imported (esm or commonjs). See [source](https://github.com/ardatan/graphql-mesh/blob/bf588d372c0078378aaa24beea2da794af7949e6/scripts/replace-import-meta-url-in-cjs.ts#L9-L10) for the lines that need to be different. This meant that we needed to change the @graphcommerce/cli package to be of type:module instead of a commonjs module.
@@ -11,12 +21,6 @@
11
21
  2) To properly convert the module to an esm module we've migrated the build of the cli package to use 'pkgroll' instead of tsc, because tsc is limited in what it outputs and can't really convert classic imports to esm.
12
22
  3) To load possible mesh plugins we require additional .ts files to be loaded with [tsx](https://tsx.is/). To get the tsx loader to work properly in combination with esm modules, we need at least [node 18.19.0](https://nodejs.org/en/blog/release/v18.19.0#new-nodemodule-api-register-for-module-customization-hooks-new-initialize-hook). Minimal Node version upped to 18.19.0 and add support for node 22. ([@paales](https://github.com/paales))
13
23
 
14
- - [#2309](https://github.com/graphcommerce-org/graphcommerce/pull/2309) [`b46e17e`](https://github.com/graphcommerce-org/graphcommerce/commit/b46e17ebe390b4d0040639dfdac33c36a60576ac) - When generating the mesh the configuration is passed through `@graphcommerce/graphql-mesh/meshConfig` allowing plugins to modify the mesh configuration without having to change the `.meshrc.yaml` itself. ([@Renzovh](https://github.com/Renzovh))
15
-
16
- - [#2330](https://github.com/graphcommerce-org/graphcommerce/pull/2330) [`bc3ec5e`](https://github.com/graphcommerce-org/graphcommerce/commit/bc3ec5e439b97cea4a2cef23e4008c7e0cfd6797) - Created a new `@graphql-mesh` plugin to forward headers from backends as `forwardedHeaders` in extensions. ([@paales](https://github.com/paales))
17
-
18
- ### Patch Changes
19
-
20
24
  - [#2345](https://github.com/graphcommerce-org/graphcommerce/pull/2345) [`d4ae30b`](https://github.com/graphcommerce-org/graphcommerce/commit/d4ae30ba28815ccb9d3a0478da995b7c609618e5) - Solve issue where `customFetch` couldn't be loaded correctly. ([@paales](https://github.com/paales))
21
25
 
22
26
  - [#2336](https://github.com/graphcommerce-org/graphcommerce/pull/2336) [`214bc56`](https://github.com/graphcommerce-org/graphcommerce/commit/214bc56950f397727d2c5417741dc62419080dfa) - Added `traverseSelectionSet` utility function to extract a child selection set from the parent. ([@Renzovh](https://github.com/Renzovh))
@@ -33,101 +37,6 @@
33
37
 
34
38
  - [#2247](https://github.com/graphcommerce-org/graphcommerce/pull/2247) [`6831040`](https://github.com/graphcommerce-org/graphcommerce/commit/68310401448b7b42b53757db4a84de4a01e35aa2) - Suppress warning where a dependency is an expression, Added uglify-es and long as the dependencies couldn’t be found ([@paales](https://github.com/paales))
35
39
 
36
- ## 9.0.0-canary.118
37
-
38
- ## 9.0.0-canary.117
39
-
40
- ## 9.0.0-canary.116
41
-
42
- ## 9.0.0-canary.115
43
-
44
- ### Patch Changes
45
-
46
- - [#2451](https://github.com/graphcommerce-org/graphcommerce/pull/2451) [`af5c1e6`](https://github.com/graphcommerce-org/graphcommerce/commit/af5c1e686792ee7c7294efb0bc3a005946ac5c98) - Made all graphql mesh dependencies peer dependencies so users can upgrade without problems ([@paales](https://github.com/paales))
47
-
48
- ## 9.0.0-canary.114
49
-
50
- ### Patch Changes
51
-
52
- - [#2450](https://github.com/graphcommerce-org/graphcommerce/pull/2450) [`d5d161c`](https://github.com/graphcommerce-org/graphcommerce/commit/d5d161c2a9f9d831962a17ba424925947b018472) - Revert Pin versions of @graphql-mesh/config and utils ([@paales](https://github.com/paales))
53
-
54
- ## 9.0.0-canary.113
55
-
56
- ## 9.0.0-canary.112
57
-
58
- ### Patch Changes
59
-
60
- - [`f28f11c`](https://github.com/graphcommerce-org/graphcommerce/commit/f28f11cf2821b3fd50c3147558f559d808b1046e) - Pin versions of @graphql-mesh/config and utils ([@paales](https://github.com/paales))
61
-
62
- ## 9.0.0-canary.111
63
-
64
- ## 9.0.0-canary.110
65
-
66
- ## 9.0.0-canary.109
67
-
68
- ## 9.0.0-canary.108
69
-
70
- ## 9.0.0-canary.107
71
-
72
- ## 9.0.0-canary.106
73
-
74
- ## 9.0.0-canary.105
75
-
76
- ## 9.0.0-canary.104
77
-
78
- ## 9.0.0-canary.103
79
-
80
- ### Patch Changes
81
-
82
- - [#2421](https://github.com/graphcommerce-org/graphcommerce/pull/2421) [`d500643`](https://github.com/graphcommerce-org/graphcommerce/commit/d500643138799b6db1610cb10a1d065d6219d8ea) - Resolve peer dependency issues so we get a clean install ([@paales](https://github.com/paales))
83
-
84
- ## 9.0.0-canary.101
85
-
86
- ### Minor Changes
87
-
88
- - [#2380](https://github.com/graphcommerce-org/graphcommerce/pull/2380) [`3710d8b`](https://github.com/graphcommerce-org/graphcommerce/commit/3710d8bf1cceb5a991e5cfdfc15d42e462704c6d) - Solves the issue `TypeError: url?.startsWith is not a function`. The generated `.mesh/index.ts` would be generated as a requirejs module while next.js expects an esm module. In the end we properly generated the mesh correctly and now there is an `import.meta.url` instead of using `require('node:url')`. To solve this we needed to solve a chain of issues:
89
-
90
- 1. The generation of the mesh is based on the version of the mesh that is imported (esm or commonjs). See [source](https://github.com/ardatan/graphql-mesh/blob/bf588d372c0078378aaa24beea2da794af7949e6/scripts/replace-import-meta-url-in-cjs.ts#L9-L10) for the lines that need to be different. This meant that we needed to change the @graphcommerce/cli package to be of type:module instead of a commonjs module.
91
-
92
- 2) To properly convert the module to an esm module we've migrated the build of the cli package to use 'pkgroll' instead of tsc, because tsc is limited in what it outputs and can't really convert classic imports to esm.
93
- 3) To load possible mesh plugins we require additional .ts files to be loaded with [tsx](https://tsx.is/). To get the tsx loader to work properly in combination with esm modules, we need at least [node 18.19.0](https://nodejs.org/en/blog/release/v18.19.0#new-nodemodule-api-register-for-module-customization-hooks-new-initialize-hook). Minimal Node version upped to 18.19.0 and add support for node 22. ([@paales](https://github.com/paales))
94
-
95
- ## 9.0.0-canary.71
96
-
97
- ### Patch Changes
98
-
99
- - [#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))
100
-
101
- ## 9.0.0-canary.67
102
-
103
- ### Patch Changes
104
-
105
- - [#2336](https://github.com/graphcommerce-org/graphcommerce/pull/2336) [`214bc56`](https://github.com/graphcommerce-org/graphcommerce/commit/214bc56950f397727d2c5417741dc62419080dfa) - Added traverseSelectionSet utility function to extract a child selection set from the parent. ([@Renzovh](https://github.com/Renzovh))
106
-
107
- ## 9.0.0-canary.59
108
-
109
- ### Minor Changes
110
-
111
- - [#2309](https://github.com/graphcommerce-org/graphcommerce/pull/2309) [`b46e17e`](https://github.com/graphcommerce-org/graphcommerce/commit/b46e17ebe390b4d0040639dfdac33c36a60576ac) - When generating the mesh the configuration is passed through `@graphcommerce/graphql-mesh/meshConfig` allowing plugins to modify the mesh configuration without having to change the `.meshrc.yaml` itself. ([@Renzovh](https://github.com/Renzovh))
112
-
113
- ## 9.0.0-canary.58
114
-
115
- ### Minor Changes
116
-
117
- - [#2330](https://github.com/graphcommerce-org/graphcommerce/pull/2330) [`bc3ec5e`](https://github.com/graphcommerce-org/graphcommerce/commit/bc3ec5e439b97cea4a2cef23e4008c7e0cfd6797) - Created a new @graphql-mesh plugin to forward headers from backends as forwardedHeaders in extensions ([@paales](https://github.com/paales))
118
-
119
- ## 8.1.0-canary.29
120
-
121
- ### Patch Changes
122
-
123
- - [#2290](https://github.com/graphcommerce-org/graphcommerce/pull/2290) [`21f2ac0`](https://github.com/graphcommerce-org/graphcommerce/commit/21f2ac06b95cfc9b51febe19e6859cbba2b578b4) - Fix cors issues with Dynamic Row Property Picker App ([@JoshuaS98](https://github.com/JoshuaS98))
124
-
125
- ## 8.1.0-canary.8
126
-
127
- ### Patch Changes
128
-
129
- - [#2247](https://github.com/graphcommerce-org/graphcommerce/pull/2247) [`6831040`](https://github.com/graphcommerce-org/graphcommerce/commit/68310401448b7b42b53757db4a84de4a01e35aa2) - Suppress warning where a dependency is an expression, Added uglify-es and long as the dependencies couldn’t be found ([@paales](https://github.com/paales))
130
-
131
40
  ## 8.0.0
132
41
 
133
42
  ### Patch Changes
package/package.json CHANGED
@@ -2,7 +2,7 @@
2
2
  "name": "@graphcommerce/graphql-mesh",
3
3
  "homepage": "https://www.graphcommerce.org/",
4
4
  "repository": "github:graphcommerce-org/graphcommerce",
5
- "version": "9.0.0",
5
+ "version": "9.0.1-canary.1",
6
6
  "main": "index.ts",
7
7
  "dependencies": {
8
8
  "@whatwg-node/fetch": "^0.10.1",
@@ -14,9 +14,9 @@
14
14
  },
15
15
  "peerDependencies": {
16
16
  "@apollo/client": "*",
17
- "@graphcommerce/eslint-config-pwa": "^9.0.0",
18
- "@graphcommerce/prettier-config-pwa": "^9.0.0",
19
- "@graphcommerce/typescript-config-pwa": "^9.0.0",
17
+ "@graphcommerce/eslint-config-pwa": "^9.0.1-canary.1",
18
+ "@graphcommerce/prettier-config-pwa": "^9.0.1-canary.1",
19
+ "@graphcommerce/typescript-config-pwa": "^9.0.1-canary.1",
20
20
  "@graphql-mesh/runtime": "*",
21
21
  "@graphql-mesh/types": "*"
22
22
  },