@graphcommerce/graphql-mesh 9.0.1-canary.0 → 9.0.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 +11 -102
  2. package/package.json +4 -4
package/CHANGELOG.md CHANGED
@@ -1,11 +1,21 @@
1
1
  # Change Log
2
2
 
3
- ## 9.0.1-canary.0
3
+ ## 9.0.1
4
+
5
+ ## 9.0.1-canary.1
4
6
 
5
7
  ## 9.0.0
6
8
 
9
+ ### Major Changes
10
+
11
+ - [#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))
12
+
7
13
  ### Minor Changes
8
14
 
15
+ - [#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))
16
+
17
+ ### Patch Changes
18
+
9
19
  - [#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:
10
20
 
11
21
  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.
@@ -13,12 +23,6 @@
13
23
  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.
14
24
  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))
15
25
 
16
- - [#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))
17
-
18
- - [#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))
19
-
20
- ### Patch Changes
21
-
22
26
  - [#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))
23
27
 
24
28
  - [#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))
@@ -35,101 +39,6 @@
35
39
 
36
40
  - [#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))
37
41
 
38
- ## 9.0.0-canary.118
39
-
40
- ## 9.0.0-canary.117
41
-
42
- ## 9.0.0-canary.116
43
-
44
- ## 9.0.0-canary.115
45
-
46
- ### Patch Changes
47
-
48
- - [#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))
49
-
50
- ## 9.0.0-canary.114
51
-
52
- ### Patch Changes
53
-
54
- - [#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))
55
-
56
- ## 9.0.0-canary.113
57
-
58
- ## 9.0.0-canary.112
59
-
60
- ### Patch Changes
61
-
62
- - [`f28f11c`](https://github.com/graphcommerce-org/graphcommerce/commit/f28f11cf2821b3fd50c3147558f559d808b1046e) - Pin versions of @graphql-mesh/config and utils ([@paales](https://github.com/paales))
63
-
64
- ## 9.0.0-canary.111
65
-
66
- ## 9.0.0-canary.110
67
-
68
- ## 9.0.0-canary.109
69
-
70
- ## 9.0.0-canary.108
71
-
72
- ## 9.0.0-canary.107
73
-
74
- ## 9.0.0-canary.106
75
-
76
- ## 9.0.0-canary.105
77
-
78
- ## 9.0.0-canary.104
79
-
80
- ## 9.0.0-canary.103
81
-
82
- ### Patch Changes
83
-
84
- - [#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))
85
-
86
- ## 9.0.0-canary.101
87
-
88
- ### Minor Changes
89
-
90
- - [#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:
91
-
92
- 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.
93
-
94
- 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.
95
- 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))
96
-
97
- ## 9.0.0-canary.71
98
-
99
- ### Patch Changes
100
-
101
- - [#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))
102
-
103
- ## 9.0.0-canary.67
104
-
105
- ### Patch Changes
106
-
107
- - [#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))
108
-
109
- ## 9.0.0-canary.59
110
-
111
- ### Minor Changes
112
-
113
- - [#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))
114
-
115
- ## 9.0.0-canary.58
116
-
117
- ### Minor Changes
118
-
119
- - [#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))
120
-
121
- ## 8.1.0-canary.29
122
-
123
- ### Patch Changes
124
-
125
- - [#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))
126
-
127
- ## 8.1.0-canary.8
128
-
129
- ### Patch Changes
130
-
131
- - [#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))
132
-
133
42
  ## 8.0.0
134
43
 
135
44
  ### 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.1-canary.0",
5
+ "version": "9.0.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.1-canary.0",
18
- "@graphcommerce/prettier-config-pwa": "^9.0.1-canary.0",
19
- "@graphcommerce/typescript-config-pwa": "^9.0.1-canary.0",
17
+ "@graphcommerce/eslint-config-pwa": "^9.0.1",
18
+ "@graphcommerce/prettier-config-pwa": "^9.0.1",
19
+ "@graphcommerce/typescript-config-pwa": "^9.0.1",
20
20
  "@graphql-mesh/runtime": "*",
21
21
  "@graphql-mesh/types": "*"
22
22
  },