chore(deps): update and migrate (#31)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: enisdenjo

.yarn/releases/yarn-3.2.4.cjs renamed to .yarn/releases/yarn-3.3.1.cjs

@@ -4,4 +4,4 @@ plugins:
   - path: .yarn/plugins/@yarnpkg/plugin-interactive-tools.cjs
     spec: '@yarnpkg/plugin-interactive-tools'
 
-yarnPath: .yarn/releases/yarn-3.2.4.cjs
+yarnPath: .yarn/releases/yarn-3.3.1.cjs

.yarnrc.yml

@@ -253,7 +253,7 @@ will be created from the provided schema.
 | `documentAST` | `DocumentNode` | - |
 | `rules?` | readonly `ValidationRule`[] | - |
 | `options?` | `Object` | - |
-| `typeInfo?` | `TypeInfo` | **`Deprecated`**  will be removed in 17.0.0 |
+| `typeInfo?` | `TypeInfo` | **`Deprecated`** will be removed in 17.0.0 |
 
 ##### Returns
 

docs/interfaces/handler.HandlerOptions.md

@@ -18,10 +18,42 @@ The necessary API from the fetch environment for the handler.
 
 ### ReadableStream
 
-• **ReadableStream**: <R\>(`underlyingSource?`: `UnderlyingSource`<`R`\>, `strategy?`: `QueuingStrategy`<`R`\>) => `ReadableStream`<`R`\>
+• **ReadableStream**: (`underlyingSource`: `UnderlyingByteSource`, `strategy?`: {}) => `ReadableStream`<`Uint8Array`\><R\>(`underlyingSource`: `UnderlyingDefaultSource`<`R`\>, `strategy?`: `QueuingStrategy`<`R`\>) => `ReadableStream`<`R`\><R\>(`underlyingSource?`: `UnderlyingSource`<`R`\>, `strategy?`: `QueuingStrategy`<`R`\>) => `ReadableStream`<`R`\>
 
 #### Type declaration
 
+• **new FetchAPI**(`underlyingSource`, `strategy?`): `ReadableStream`<`Uint8Array`\>
+
+##### Parameters
+
+| Name | Type |
+| :------ | :------ |
+| `underlyingSource` | `UnderlyingByteSource` |
+| `strategy?` | `Object` |
+
+##### Returns
+
+`ReadableStream`<`Uint8Array`\>
+
+• **new FetchAPI**<`R`\>(`underlyingSource`, `strategy?`): `ReadableStream`<`R`\>
+
+##### Type parameters
+
+| Name | Type |
+| :------ | :------ |
+| `R` | `any` |
+
+##### Parameters
+
+| Name | Type |
+| :------ | :------ |
+| `underlyingSource` | `UnderlyingDefaultSource`<`R`\> |
+| `strategy?` | `QueuingStrategy`<`R`\> |
+
+##### Returns
+
+`ReadableStream`<`R`\>
+
 • **new FetchAPI**<`R`\>(`underlyingSource?`, `strategy?`): `ReadableStream`<`R`\>
 
 ##### Type parameters

docs/interfaces/use_fetch.FetchAPI.md

@@ -3,8 +3,8 @@ _* This report was auto-generated by graphql-http_
 # GraphQL over HTTP audit report
 
 - **79** audits in total
-- ✅ **43** pass
-- ⚠️ **36** warnings (optional)
+- ✅ **53** pass
+- ⚠️ **26** warnings (optional)
 
 ## Passing
 1. SHOULD accept application/graphql-response+json and match the content-type
@@ -25,31 +25,41 @@ _* This report was auto-generated by graphql-http_
 16. SHOULD use 400 status code on array {query} parameter when accepting application/graphql-response+json
 17. SHOULD allow string {query} parameter when accepting application/graphql-response+json
 18. MUST allow string {query} parameter when accepting application/json
-19. SHOULD allow string {operationName} parameter when accepting application/graphql-response+json
-20. MUST allow string {operationName} parameter when accepting application/json
-21. SHOULD allow null {variables} parameter when accepting application/graphql-response+json
-22. MUST allow null {variables} parameter when accepting application/json
-23. SHOULD allow null {operationName} parameter when accepting application/graphql-response+json
-24. MUST allow null {operationName} parameter when accepting application/json
-25. SHOULD allow null {extensions} parameter when accepting application/graphql-response+json
-26. MUST allow null {extensions} parameter when accepting application/json
-27. SHOULD use 400 status code on string {variables} parameter when accepting application/graphql-response+json
-28. SHOULD allow map {variables} parameter when accepting application/graphql-response+json
-29. MUST allow map {variables} parameter when accepting application/json
-30. SHOULD use 400 status code on string {extensions} parameter when accepting application/graphql-response+json
-31. SHOULD allow map {extensions} parameter when accepting application/graphql-response+json
-32. MUST allow map {extensions} parameter when accepting application/json
-33. SHOULD use 4xx or 5xx status codes on JSON parsing failure when accepting application/graphql-response+json
-34. SHOULD use 400 status code on JSON parsing failure when accepting application/graphql-response+json
-35. SHOULD use 4xx or 5xx status codes if parameters are invalid when accepting application/graphql-response+json
-36. SHOULD use 400 status code if parameters are invalid when accepting application/graphql-response+json
-37. SHOULD not contain the data entry if parameters are invalid when accepting application/graphql-response+json
-38. SHOULD use 4xx or 5xx status codes on document parsing failure when accepting application/graphql-response+json
-39. SHOULD use 400 status code on document parsing failure when accepting application/graphql-response+json
-40. SHOULD not contain the data entry on document parsing failure when accepting application/graphql-response+json
-41. SHOULD use 4xx or 5xx status codes on document validation failure when accepting application/graphql-response+json
-42. SHOULD use 400 status code on document validation failure when accepting application/graphql-response+json
-43. SHOULD not contain the data entry on document validation failure when accepting application/graphql-response+json
+19. SHOULD use 400 status code on object {operationName} parameter when accepting application/graphql-response+json
+20. SHOULD use 400 status code on number {operationName} parameter when accepting application/graphql-response+json
+21. SHOULD use 400 status code on boolean {operationName} parameter when accepting application/graphql-response+json
+22. SHOULD use 400 status code on array {operationName} parameter when accepting application/graphql-response+json
+23. SHOULD allow string {operationName} parameter when accepting application/graphql-response+json
+24. MUST allow string {operationName} parameter when accepting application/json
+25. SHOULD allow null {variables} parameter when accepting application/graphql-response+json
+26. MUST allow null {variables} parameter when accepting application/json
+27. SHOULD allow null {operationName} parameter when accepting application/graphql-response+json
+28. MUST allow null {operationName} parameter when accepting application/json
+29. SHOULD allow null {extensions} parameter when accepting application/graphql-response+json
+30. MUST allow null {extensions} parameter when accepting application/json
+31. SHOULD use 400 status code on string {variables} parameter when accepting application/graphql-response+json
+32. SHOULD use 400 status code on number {variables} parameter when accepting application/graphql-response+json
+33. SHOULD use 400 status code on boolean {variables} parameter when accepting application/graphql-response+json
+34. SHOULD use 400 status code on array {variables} parameter when accepting application/graphql-response+json
+35. SHOULD allow map {variables} parameter when accepting application/graphql-response+json
+36. MUST allow map {variables} parameter when accepting application/json
+37. SHOULD use 400 status code on string {extensions} parameter when accepting application/graphql-response+json
+38. SHOULD use 400 status code on number {extensions} parameter when accepting application/graphql-response+json
+39. SHOULD use 400 status code on boolean {extensions} parameter when accepting application/graphql-response+json
+40. SHOULD use 400 status code on array {extensions} parameter when accepting application/graphql-response+json
+41. SHOULD allow map {extensions} parameter when accepting application/graphql-response+json
+42. MUST allow map {extensions} parameter when accepting application/json
+43. SHOULD use 4xx or 5xx status codes on JSON parsing failure when accepting application/graphql-response+json
+44. SHOULD use 400 status code on JSON parsing failure when accepting application/graphql-response+json
+45. SHOULD use 4xx or 5xx status codes if parameters are invalid when accepting application/graphql-response+json
+46. SHOULD use 400 status code if parameters are invalid when accepting application/graphql-response+json
+47. SHOULD not contain the data entry if parameters are invalid when accepting application/graphql-response+json
+48. SHOULD use 4xx or 5xx status codes on document parsing failure when accepting application/graphql-response+json
+49. SHOULD use 400 status code on document parsing failure when accepting application/graphql-response+json
+50. SHOULD not contain the data entry on document parsing failure when accepting application/graphql-response+json
+51. SHOULD use 4xx or 5xx status codes on document validation failure when accepting application/graphql-response+json
+52. SHOULD use 400 status code on document validation failure when accepting application/graphql-response+json
+53. SHOULD not contain the data entry on document validation failure when accepting application/graphql-response+json
 
 ## Warnings
 The server _SHOULD_ support these, but is not required.
@@ -81,119 +91,79 @@ Status code 400 is not 200
 ```
 Status code 400 is not 200
 ```
-8. SHOULD use 400 status code on object {operationName} parameter when accepting application/graphql-response+json<br />
+8. SHOULD use 200 status code with errors field on object {operationName} parameter when accepting application/json<br />
 ```
-Status code 200 is not 400
-```
-9. SHOULD use 400 status code on number {operationName} parameter when accepting application/graphql-response+json<br />
-```
-Status code 200 is not 400
-```
-10. SHOULD use 400 status code on boolean {operationName} parameter when accepting application/graphql-response+json<br />
-```
-Status code 200 is not 400
-```
-11. SHOULD use 400 status code on array {operationName} parameter when accepting application/graphql-response+json<br />
-```
-Status code 200 is not 400
-```
-12. SHOULD use 200 status code with errors field on object {operationName} parameter when accepting application/json<br />
-```
-Execution result {"data":{"__typename":"Query"}} does not have a property 'errors'
-```
-13. SHOULD use 200 status code with errors field on number {operationName} parameter when accepting application/json<br />
-```
-Execution result {"data":{"__typename":"Query"}} does not have a property 'errors'
-```
-14. SHOULD use 200 status code with errors field on boolean {operationName} parameter when accepting application/json<br />
-```
-Execution result {"data":{"__typename":"Query"}} does not have a property 'errors'
-```
-15. SHOULD use 200 status code with errors field on array {operationName} parameter when accepting application/json<br />
-```
-Execution result {"data":{"__typename":"Query"}} does not have a property 'errors'
-```
-16. SHOULD use 400 status code on number {variables} parameter when accepting application/graphql-response+json<br />
-```
-Status code 200 is not 400
-```
-17. SHOULD use 400 status code on boolean {variables} parameter when accepting application/graphql-response+json<br />
-```
-Status code 200 is not 400
-```
-18. SHOULD use 400 status code on array {variables} parameter when accepting application/graphql-response+json<br />
-```
-Status code 200 is not 400
+Status code 400 is not 200
 ```
-19. SHOULD use 200 status code with errors field on string {variables} parameter when accepting application/json<br />
+9. SHOULD use 200 status code with errors field on number {operationName} parameter when accepting application/json<br />
 ```
 Status code 400 is not 200
 ```
-20. SHOULD use 200 status code with errors field on number {variables} parameter when accepting application/json<br />
+10. SHOULD use 200 status code with errors field on boolean {operationName} parameter when accepting application/json<br />
 ```
-Execution result {"data":{"__typename":"Query"}} does not have a property 'errors'
+Status code 400 is not 200
 ```
-21. SHOULD use 200 status code with errors field on boolean {variables} parameter when accepting application/json<br />
+11. SHOULD use 200 status code with errors field on array {operationName} parameter when accepting application/json<br />
 ```
-Execution result {"data":{"__typename":"Query"}} does not have a property 'errors'
+Status code 400 is not 200
 ```
-22. SHOULD use 200 status code with errors field on array {variables} parameter when accepting application/json<br />
+12. SHOULD use 200 status code with errors field on string {variables} parameter when accepting application/json<br />
 ```
-Execution result {"data":{"__typename":"Query"}} does not have a property 'errors'
+Status code 400 is not 200
 ```
-23. MAY allow URL-encoded JSON string {variables} parameter in GETs when accepting application/graphql-response+json<br />
+13. SHOULD use 200 status code with errors field on number {variables} parameter when accepting application/json<br />
 ```
 Status code 400 is not 200
 ```
-24. MAY allow URL-encoded JSON string {variables} parameter in GETs when accepting application/json<br />
+14. SHOULD use 200 status code with errors field on boolean {variables} parameter when accepting application/json<br />
 ```
 Status code 400 is not 200
 ```
-25. SHOULD use 400 status code on number {extensions} parameter when accepting application/graphql-response+json<br />
+15. SHOULD use 200 status code with errors field on array {variables} parameter when accepting application/json<br />
 ```
-Status code 200 is not 400
+Status code 400 is not 200
 ```
-26. SHOULD use 400 status code on boolean {extensions} parameter when accepting application/graphql-response+json<br />
+16. MAY allow URL-encoded JSON string {variables} parameter in GETs when accepting application/graphql-response+json<br />
 ```
-Status code 200 is not 400
+Status code 400 is not 200
 ```
-27. SHOULD use 400 status code on array {extensions} parameter when accepting application/graphql-response+json<br />
+17. MAY allow URL-encoded JSON string {variables} parameter in GETs when accepting application/json<br />
 ```
-Status code 200 is not 400
+Status code 400 is not 200
 ```
-28. SHOULD use 200 status code with errors field on string {extensions} parameter when accepting application/json<br />
+18. SHOULD use 200 status code with errors field on string {extensions} parameter when accepting application/json<br />
 ```
 Status code 400 is not 200
 ```
-29. SHOULD use 200 status code with errors field on number {extensions} parameter when accepting application/json<br />
+19. SHOULD use 200 status code with errors field on number {extensions} parameter when accepting application/json<br />
 ```
-Execution result {"data":{"__typename":"Query"}} does not have a property 'errors'
+Status code 400 is not 200
 ```
-30. SHOULD use 200 status code with errors field on boolean {extensions} parameter when accepting application/json<br />
+20. SHOULD use 200 status code with errors field on boolean {extensions} parameter when accepting application/json<br />
 ```
-Execution result {"data":{"__typename":"Query"}} does not have a property 'errors'
+Status code 400 is not 200
 ```
-31. SHOULD use 200 status code with errors field on array {extensions} parameter when accepting application/json<br />
+21. SHOULD use 200 status code with errors field on array {extensions} parameter when accepting application/json<br />
 ```
-Execution result {"data":{"__typename":"Query"}} does not have a property 'errors'
+Status code 400 is not 200
 ```
-32. SHOULD use 200 status code on JSON parsing failure when accepting application/json<br />
+22. SHOULD use 200 status code on JSON parsing failure when accepting application/json<br />
 ```
 Status code 400 is not 200
 ```
-33. SHOULD use 200 status code if parameters are invalid when accepting application/json<br />
+23. SHOULD use 200 status code if parameters are invalid when accepting application/json<br />
 ```
 Status code 400 is not 200
 ```
-34. SHOULD use 200 status code on document parsing failure when accepting application/json<br />
+24. SHOULD use 200 status code on document parsing failure when accepting application/json<br />
 ```
 Status code 400 is not 200
 ```
-35. SHOULD use 200 status code on document validation failure when accepting application/json<br />
+25. SHOULD use 200 status code on document validation failure when accepting application/json<br />
 ```
 Status code 400 is not 200
 ```
-36. SHOULD not contain the data entry on JSON parsing failure when accepting application/graphql-response+json<br />
+26. SHOULD not contain the data entry on JSON parsing failure when accepting application/graphql-response+json<br />
 ```
 Response body is not valid JSON. Got "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n<meta charset=\"utf-8\">\n<title>Error</title>\n</head>\n<body>\n<pre>SyntaxError: Unexpected end of JSON input<br> &nbsp; &nbsp;at JSON.parse (&lt;anonymous&gt;)<br> &nbsp; &nbsp;at parse (/home/runner/work/graphql-http/graphql-http/node_modules/body-parser/lib/types/json.js:89:19)<br> &nbsp; &nbsp;at /home/runner/work/graphql-http/graphql-http/node_modules/body-parser/lib/read.js:128:18<br> &nbsp; &nbsp;at AsyncResource.runInAsyncScope (node:async_hooks:203:9)<br> &nbsp; &nbsp;at invokeCallback (/home/runner/work/graphql-http/graphql-http/node_modules/raw-body/index.js:231:16)<br> &nbsp; &nbsp;at done (/home/runner/work/graphql-http/graphql-http/node_modules/raw-body/index.js:220:7)<br> &nbsp; &nbsp;at IncomingMessage.onEnd (/home/runner/work/graphql-http/graphql-http/node_modules/raw-body/index.js:280:7)<br> &nbsp; &nbsp;at IncomingMessage.emit (node:events:513:28)<br> &nbsp; &nbsp;at endReadableNT (node:internal/streams/rea...
 ```

implementations/apollo-server/README.md

@@ -7,7 +7,7 @@
     "start": "node ."
   },
   "dependencies": {
-    "@apollo/server": "^4.1.1",
+    "@apollo/server": "^4.3.0",
     "graphql": "^16.6.0"
   }
 }