[Snyk] Upgrade graphql-jit from 0.7.4 to 0.8.4

[mattkrick]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade graphql-jit from 0.7.4 to 0.8.4.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 5 versions ahead of your current version.
• The recommended version was released 8 months ago, on 2023-07-04.

Release notes

Package name: graphql-jit

• 0.8.4 - 2023-07-04
  

  Improvements:

  • Remove memoization for collectSubFields to reduce memory pressure and gc (#214)
• 0.8.3 - 2023-06-29
  

  Fixes:

  • Move the initialization of __internalShouldIncludePath behind the option useExperimentalPathBasedSkipInclude to avoid unnecessary object generation and increased garbage collection runs when the feature is not in use #210

  The option introduced in the release https://github.com/zalando-incubator/graphql-jit/releases/tag/v0.8.1 will now be used to control initialization of field node metadata. This is to avoid increased garbage collection runs observed in the previous release.

  Dependency updates:

  • upgrade jest from v27.0.3 to v29.5.2 (#206)
  • upgrade @ graphql-typed-document-node/core from 3.1.1 to 3.1.2 (#198)
  • upgrade fast-json-stringify to ^5.7.0 (#203)
  • upgrade @ graphql-typed-document-node/core from 3.1.2 to 3.2.0 (#207)
• 0.8.2 - 2023-04-27
  

  Fixes:

  • fix: improve event loop lag of compilation - use the option(useExperimentalPathBasedSkipInclude) to compute path based skip/include (#200)

  The option introduced in the previous release https://github.com/zalando-incubator/graphql-jit/releases/tag/v0.8.1 will now be used in the computation of the skip include compiled code as well. This is to avoid high event-loop-lag observed in the previous release.

• 0.8.1 - 2023-03-30
  

  Bug Fixes:

  • fix: skip include logic handling multiple paths to same node (PR: #197) (Issue: #166)

  This release introduces a new CompilerOption useExperimentalPathBasedSkipInclude. If you have multiple "fragment spreads" pointing to the same fragment and use skip include inside the fragment, it is recommended to use this option to avoid a bug. In future releases, this option will be removed when it becomes the default.

  For example,

  const compiledQuery = compileQuery(
    schema, ast, operationName,
    {
      useExperimentalPathBasedSkipInclude: true
    }
  );

• 0.8.0 - 2023-01-30
  

  What's Changed

  Breaking Changes:

  • Drop build for Node 12, add 18 (#188)

  Bug fixes:

  • fix: validation for skip/include with default values (#193)
  • fix: field expansion - fill only relevant fields while traversing abstract types (#180)
  • fix: update deprecated API in GraphQL JS to new API (#179)

  Version updates:

  • Bump minimatch from 3.0.4 to 3.1.2 (#192)
  • Bump decode-uri-component from 0.2.0 to 0.2.2 (#186)
  • Bump json5 from 1.0.1 to 1.0.2 (#187)

  Other changes:

  • Add test case to json.test.ts (#191)

  Full Changelog: v0.7.4...v0.8.0

• 0.7.4 - 2022-05-24
  

  What's Changed

  • Allow +1 from collaborators by @ ruiaraujo in #165
  • fix: parse Date scalar object arguments properly by @ andrew0 in #158
  • Bump minimist from 1.2.5 to 1.2.6 by @ dependabot in #169
  • Bump async from 2.6.2 to 2.6.4 by @ dependabot in #170
  • [Snyk] Upgrade fast-json-stringify from 1.13.0 to 1.21.0 by @ snyk-bot in #168
  • fix: apply directives skip/include for mutation by @ boopathi in #172
  • Bump release to 0.7.4 by @ boopathi in #173

  New Contributors

  • @ andrew0 made their first contribution in #158
  • @ snyk-bot made their first contribution in #168

  Full Changelog: v0.7.3...v0.7.4

from graphql-jit GitHub release notes

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs