Releases: 0no-co/graphql.web
Releases · 0no-co/graphql.web
v1.0.11
Patch Changes
- Export Extensions type
Submitted by @jaulz (See #36)
v1.0.9
Patch Changes
- Remove
for-of
syntax from valueFromTypeNode
and valueFromASTUntyped
helpers for JSC memory reduction
Submitted by @kitten (See #33)
v1.0.8
Patch Changes
- ⚠️ Fix typo causing complex string parsing to fail on subsequent runs
Submitted by @kitten (See #31)
v1.0.7
Patch Changes
- ⚠️ Fix
@ts-ignore
on TypeScript peer dependency import in typings not being applied due to a leading !
character
Submitted by @IvanUkhov (See #27)
v1.0.6
Patch Changes
- ⚠️ Fix aliased field name followed by arguments causing parsing error
Submitted by @kitten (See 65c73a0
)
v1.0.5
Patch Changes
- Update build process to align with other
@0no-co
packages. Effectively, this will mean that the JS features range we support will now match urql
, and in practice, this means that for-of
is now used in our build output
Submitted by @kitten (See #21)
- Improve parser performance
Submitted by @kitten (See #25)
- Improve printer performance
Submitted by @kitten (See #24)
@0no-co/graphql.web@1.0.4
Patch Changes
- ⚠️ Fix empty string matches being too eager, e.g.
"", ""
Submitted by @kitten (See 29cbe5c
)
@0no-co/graphql.web@1.0.3
Patch Changes
- ⚠️ Fix string and block string matches eagerly matching past the end boundary of strings and ignoring escaped closing characters. In certain cases,
"""
and "
boundaries would be skipped if any other string boundary follows in the input document
Submitted by @kitten (See #17)
@0no-co/graphql.web@1.0.2
Patch Changes
- ⚠️ Fix browser quirk occurring in Safari 10–13 causing sticky regular expressions in the parser to match when they shouldn't / match too eagerly
Submitted by @kitten (See #15)
@0no-co/graphql.web@1.0.1
Patch Changes
- Publish with npm provenance
Submitted by @kitten (See #12)