Make fast-json-stringify optional

[hoangvvo]

Close #83

This is still up to discussion and may be closed if it deems likewise. This is a breaking change

const fastJson = require('fast-json-stringify')
const { compileQuery } = require("graphql-jit");

const compiledQuery = compileQuery(schema, document, { fastJson });

Caveat:

• This may be confusing for end-user.
• queryToJSONSchema is tightly coupled with fast-json-stringify (nullable prop)
• May break if fast-json-stringify has breaking change.

[hoangvvo]

We can also try https://docs.npmjs.com/files/package.json#optionaldependencies

[ruiaraujo]

I will try reviewing this weekend.

[ruiaraujo]

I would prefer to extract the json to a separate package. I am not a fan of having it integrated since there are very limited advantages to having it included.

It would also be natural to expose graphql query to binary.

@boopathi wdyt?

[boopathi]

Yes. I also agree with the caveats mentioned in the description. I think we can start with this and think about a model after we start including serializing to other formats like binary.

[hoangvvo]

I agree to this. I'm actually ok with not even having that separate package in the meantime.

We can still keep customJSONSerializer, but letting it be a function that accepts context from buildCompilationContext and returns a custom stringify function.

customJSONSerializer: (context) => {
  jsonSchema = outOwnQueryToJSONSchema(context);
  return fastJson(jsonSchema)
}

Closing.