Change log

v2.12.6

v2.12.5

v2.12.4 (2021-04-29)

v2.12.3

v2.12.2

v2.12.1

v2.12.0

  • The graphql-tag repository has been converted to TypeScript, adding type safety and enabling both ECMAScript and CommonJS module exports. While these changes are intended to be as backwards-compatible as possible, we decided to bump the minor version to reflect the significant refactoring. @PowerKiKiarrow-up-right and @benjamnarrow-up-right in #325arrow-up-right

v2.11.0 (2020-07-28)

v2.10.4 (2020-07-08)

v2.10.3 (2020-02-05)

v2.10.2 (2020-02-04)

v2.10.1

v2.10.0

v2.9.1

v2.9.0

v2.8.0

v2.7.{0,1,2,3}

v2.6.1

v2.6.0

v2.5.0

v2.4.{1,2}

v2.4.0

v2.3.0

v2.2.2

v2.2.1

v2.2.0

v2.1.0

v2.0.0

Restore dependence on graphql module abhiaiyer91arrow-up-right in PR #46arrow-up-right addressing #6arrow-up-right

v1.3.2

v1.3.1

v1.3.0

v1.2.4

Restore Node < 6 compatibility. DragosRotaruarrow-up-right in PR #41arrow-up-right addressing #39arrow-up-right

v1.2.1

Fixed an issue with fragment imports. PR #35arrow-up-right.

v1.2.0

Added ability to import other GraphQL documents with fragments using #import comments. PR #33arrow-up-right

v1.1.2

Fix issue with interpolating undefined values Issue #19arrow-up-right

v1.1.1

Added typescript definitions for the below.

v1.1.0

We now emit warnings if you use the same name for two different fragments.

You can disable this with:

v1.0.0

Releasing 0.1.17 as 1.0.0 in order to be explicit about Semantic Versioning.

v0.1.17

  • Allow embedding fragments inside document strings, as in

See also http://dev.apollodata.com/react/fragments.html

v0.1.16

v0.1.15

  • Add Webpack loader to graphql-tag/loader.

v0.1.14

Changes were not tracked before this version.

Last updated