Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@graphql-tools/[email protected]
Minor Changes
#6789
2c70d27
Thanks @n1ru4l! - - New helper function
getAbortPromise
to get apromise rejected when
AbortSignal
is abortedregisterAbortSignalListener
to register a listener to abort a promise whenAbortSignal
is abortedInstead of using
.addEventListener('abort', () => {/* ... */})
, we register a single listener toavoid warnings on Node.js like
MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 abort listeners added. Use emitter.setMaxListeners() to increase limit
.@graphql-tools/[email protected]
Patch Changes
#6789
2c70d27
Thanks @n1ru4l! - Surpress the "possible EventEmitter memory leak
detected." warning occuring on Node.js when passing a
AbortSignal
toexecute
.Each execution will now only set up a single listener on the supplied
AbortSignal
. While thewarning is harmless it can be misleading, which is the main motivation of this change.
Updated dependencies
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:[email protected]
Patch Changes
@graphql-tools/[email protected]
Patch Changes
ddfef2c
Thanks @ardatan! - Avoid importing
process
and use it fromglobalThis
. In some cases,cwd
is not exported with this name in the environment in ESM scope.[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
,ddfef2c
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]:@graphql-tools/[email protected]
Patch Changes
[
2c70d27
]: