{"id":14976119,"url":"https://github.com/nicolasdao/schemaglue","last_synced_at":"2025-08-05T08:13:55.115Z","repository":{"id":22894687,"uuid":"97605781","full_name":"nicolasdao/schemaglue","owner":"nicolasdao","description":"Naturally breaks down your monolithic graphql schema into bits and pieces and then glue them back together.","archived":false,"fork":false,"pushed_at":"2023-03-05T06:07:35.000Z","size":296,"stargazers_count":115,"open_issues_count":6,"forks_count":13,"subscribers_count":5,"default_branch":"master","last_synced_at":"2025-07-27T19:50:39.313Z","etag":null,"topics":["apollo-server","graphql","graphql-schema","graphql-tools","neap","resolver","schema"],"latest_commit_sha":null,"homepage":"","language":"JavaScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"bsd-3-clause","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/nicolasdao.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2017-07-18T14:07:23.000Z","updated_at":"2024-10-16T21:57:58.000Z","dependencies_parsed_at":"2024-06-18T17:11:02.562Z","dependency_job_id":null,"html_url":"https://github.com/nicolasdao/schemaglue","commit_stats":{"total_commits":92,"total_committers":6,"mean_commits":"15.333333333333334","dds":"0.30434782608695654","last_synced_commit":"1e94e07d76fb20f5a0361588eca807424e4d13f6"},"previous_names":[],"tags_count":30,"template":false,"template_full_name":null,"purl":"pkg:github/nicolasdao/schemaglue","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nicolasdao%2Fschemaglue","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nicolasdao%2Fschemaglue/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nicolasdao%2Fschemaglue/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nicolasdao%2Fschemaglue/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/nicolasdao","download_url":"https://codeload.github.com/nicolasdao/schemaglue/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nicolasdao%2Fschemaglue/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":268859122,"owners_count":24318874,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-08-05T02:00:12.334Z","response_time":2576,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["apollo-server","graphql","graphql-schema","graphql-tools","neap","resolver","schema"],"created_at":"2024-09-24T13:53:20.892Z","updated_at":"2025-08-05T08:13:55.069Z","avatar_url":"https://github.com/nicolasdao.png","language":"JavaScript","funding_links":[],"categories":["JavaScript"],"sub_categories":[],"readme":"# SchemaGlue \u0026middot;\t[![NPM](https://img.shields.io/npm/v/schemaglue.svg?style=flat)](https://www.npmjs.com/package/schemaglue) [![Tests](https://travis-ci.org/nicolasdao/schemaglue.svg?branch=master)](https://travis-ci.org/nicolasdao/schemaglue) [![License](https://img.shields.io/badge/License-BSD%203--Clause-blue.svg)](https://opensource.org/licenses/BSD-3-Clause) [![Neap](https://neap.co/img/made_by_neap.svg)](#this-is-what-we-re-up-to) [![npm downloads](https://img.shields.io/npm/dt/schemaglue.svg?style=flat)](https://www.npmjs.com/package/schemaglue)\n\nBreak down your big monolitic GraphQl schema.js file into multiple files following the structure that makes sense to you and your team. _**SchemaGlue.js**_ will glue all those files together for you ♥ ʘ‿ʘ.\n\u003e * [Install](#install)\n\u003e * [How To Use It](#how-to-use-it)\n\u003e\t- [In Short](#in-short)\n\u003e\t- [Typescript Support \u0026 Custom Globbing](#typescript-support--custom-globbing)\n\u003e\t- [Ignoring Certain Files](#ignoring-certain-files)\n\u003e\t- [Custom Extensions](#custom-extensions)\n\u003e\t- [Unions \u0026 Interfaces](#unions--interfaces)\n\u003e\t- [Mix `.graphql` files with inline string schemas](#mix-graphql-files-with-inline-string-schemas)\n\u003e\t- [Replacing `.graphql` files with plain `.js` or `.ts` files](#replacing-graphql-files-with-plain-js-or-ts-files)\n\u003e * [Typescript support](#typescript-support)\n\u003e * [Pull-Requests \u0026 Contribution](#contribute)\n\u003e * [About Us](#this-is-what-we-re-up-to)\n\t\n# What It Does\nMake your code more readable and understandable by breaking down your monolithic GraphQL schema and resolver into smaller domain models. _**SchemaGlue.js**_ will help glueing them back together.\n\n_**Without SchemaGlue - Stuck With a Monolithic Schema**_\n```\n- src/\n\t|__ schema.js\n\n- index.js\n- package.json\n```\n_**With SchemaGlue - Structure Your Schema At Will**_\n```\n- src/\n\t|__ graphql/\n\t\t\t|__ product/\n\t\t\t|\t\t|__ schema.graphql\n\t\t\t|\t\t|__ resolver.js\n\t\t\t|\n\t\t\t|__ variant/\n\t\t\t\t\t\t|__ schema.graphql\n\t\t\t\t\t\t|__ resolver.js\n\n- index.js\n- package.json\n```\n\n# Install\n```\nnpm install schemaglue --save\n```\n\n# How To use It\n\n\u003eNOTICE: All the following examples use [__*webfunc*__](https://github.com/nicolasdao/webfunc) and [__*graphql-serverless*__](https://github.com/nicolasdao/graphql-serverless). _graphql-serverless_ makes developing GraphQl server locally dead easy while _webfunc_ is a serverless web framework that allows to write Express-like server to deploy them on any serverless solution.\n\n## In Short\n```js\nconst glue = require('schemaglue')\n\n// This will look for any js files under the 'src/graphql' folder that \n// comply to a certain convention described below. Those files describe\n// bits and pieces of the GraphQL schema and resolver that schemaglue will\n// reassemble into a single 'schema' string and 'resolver' object.\nconst options = {\n\tjs: '**/*.js', // default\n\tignore: '**/somefileyoudonotwant.js'\n}\nconst { schema, resolver } = glue('src/graphql', options)\n```\n\n### Without SchemaGlue\n\u003ePREREQUISITE - Install the following dependencies before running the following code:\n\u003e\n\u003e `npm install webfunc graphql-serverless schemaglue lodash --save`\n\u003e\n\n_Project Structure Example_\n```\n- src/\n\t|__ schema.js\n\n- index.js\n- package.json\n```\n\nWhere the _schema.js_ file would contain the entire GraphQl schema and resolver definition:\n```js\n// src/schema.js\n\nconst { graphqlError } = require('graphql-serverless')\nconst { makeExecutableSchema } = require('graphql-tools') // this dependency is automatically included in 'graphql-serverless'\nconst _ = require('lodash')\n\nconst schema = `\ntype Product {\n\tid: ID!\n\tname: String!\n\tshortDescription: String\n}\n\ntype Variant {\n\tid: ID!\n\tname: String!\n\tshortDescription: String\n}\n\ntype Query {\n\t# ### GET products\n\t#\n\t# _Arguments_\n\t# - **id**: Product id (optional)\n\tproducts(id: Int): [Product]\n\n\t# ### GET variants\n\t#\n\t# _Arguments_\n\t# - **id**: Variant id (optional)\n\tvariants(id: Int): [Variant]\n}\n`\nconst productMocks = [{ id: 1, name: 'Product A', shortDescription: 'First product.' }, { id: 2, name: 'Product B', shortDescription: 'Second product.' }]\nconst productResolver = {\n\tQuery: {\n\t\tproducts(root, { id }, context) {\n\t\t\tconst results = id ? productMocks.filter(p =\u003e p.id == id) : productMocks\n\t\t\tif (results.length \u003e 0)\n\t\t\t\treturn results\n\t\t\telse\n\t\t\t\tthrow graphqlError(404, `Product with id ${id} does not exist.`)\n\t\t}\n\t}\n}\n\nconst variantMocks = [{ id: 1, name: 'Variant A', shortDescription: 'First variant.' }, { id: 2, name: 'Variant B', shortDescription: 'Second variant.' }]\nconst variantResolver = {\n\tQuery: {\n\t\tvariants(root, { id }, context) {\n\t\t\tconst results = id ? variantMocks.filter(p =\u003e p.id == id) : variantMocks\n\t\t\tif (results.length \u003e 0)\n\t\t\t\treturn results\n\t\t\telse\n\t\t\t\tthrow graphqlError(404, `Variant with id ${id} does not exist.`)\n\t\t}\n\t}\n}\n\nconst executableSchema = makeExecutableSchema({\n\ttypeDefs: schema,\n\tresolvers: _.merge(productResolver, variantResolver) \n})\n\nmodule.exports = {\n\texecutableSchema\n}\n```\n\n```js\n// index.js\n\nconst { graphqlHandler } = require('graphql-serverless')\nconst express = require('express')\nconst app = express()\nconst { executableSchema } = require('./src/schema')\n\nconst graphqlOptions = {\n\tschema: executableSchema,\n\tgraphiql: { // If you do not want to host any GraphiQl web interface, leave this property undefined.\n\t\tendpoint: '/graphiql' \n\t}\n}\n\n// Host a GraphQl API on 2 endpoints: '/' and '/graphiql'. '/graphiql' is used to host the GraphiQL web interface.\n// If you're not interested in the GraphiQl web interface, leave the above 'graphqlOptions.graphiql' undefined and \n// replace the path following ['/', '/graphiql'] with '/'.\napp.all(['/', '/graphiql'], graphqlHandler(graphqlOptions))\n\n// Starting the server \napp.listen(4000, () =\u003e console.log('Server start. Go to http://localhost:4000/graphiql'))\n```\n\nSimply run `node index.js` and then browse to [http://localhost:4000/graphiql](http://localhost:4000/graphiql).\n\n### With SchemaGlue\n\u003ePREREQUISITE - Install the following dependencies before running the following code:\n\u003e\n\u003e `npm i express graphql-serverless schemaglue lodash --save`\n\u003e\n\n_Project Structure Example_\n```\n- src/\n\t|__ graphql/\n\t\t\t|__ product/\n\t\t\t|\t\t|__ schema.graphql\n\t\t\t|\t\t|__ resolver.js\n\t\t\t|\n\t\t\t|__ variant/\n\t\t\t\t\t\t|__ schema.graphql\n\t\t\t\t\t\t|__ resolver.js\n\n- index.js\n- package.json\n```\n\nThis is just one example of how to structure the schema and resolver. _**schemaglue**_ looks for all .js and .graphql files under a specific path.\n\n```js\n// src/graphql/product/schema.graphql\n\ntype Product {\n\tid: ID!\n\tname: String!\n\tshortDescription: String\n}\n\ntype Query {\n\t# ### GET products\n\t#\n\t# _Arguments_\n\t# - **id**: Product id (optional)\n\tproducts(id: Int): [Product]\n}\n```\n\n```js\n// src/graphql/product/resolver.js\n\nconst { graphqlError } = require('graphql-serverless')\n\nconst productMocks = [{ id: 1, name: 'Product A', shortDescription: 'First product.' }, { id: 2, name: 'Product B', shortDescription: 'Second product.' }]\n\nexports.resolver = {\n\tQuery: {\n\t\tproducts(root, { id }, context) {\n\t\t\tconst results = id ? productMocks.filter(p =\u003e p.id == id) : productMocks\n\t\t\tif (results.length \u003e 0)\n\t\t\t\treturn results\n\t\t\telse\n\t\t\t\tthrow graphqlError(404, `Product with id ${id} does not exist.`)\n\t\t}\n\t}\n}\n```\n\n```js\n// src/graphql/variant/schema.graphql\n\ntype Variant {\n\tid: ID!\n\tname: String!\n\tshortDescription: String\n}\n\ntype Query {\n\t# ### GET variants\n\t#\n\t# _Arguments_\n\t# - **id**: Variant id (optional)\n\tvariants(id: Int): [Variant]\n}\n```\n\n```js\n// src/graphql/variant/resolver.js\n\nconst { graphqlError } = require('graphql-serverless')\n\nconst variantMocks = [{ id: 1, name: 'Variant A', shortDescription: 'First variant.' }, { id: 2, name: 'Variant B', shortDescription: 'Second variant.' }]\n\nexports.resolver = {\n\tQuery: {\n\t\tvariants(root, { id }, context) {\n\t\t\tconst results = id ? variantMocks.filter(p =\u003e p.id == id) : variantMocks\n\t\t\tif (results.length \u003e 0)\n\t\t\t\treturn results\n\t\t\telse\n\t\t\t\tthrow graphqlError(404, `Variant with id ${id} does not exist.`)\n\t\t}\n\t}\n}\n```\n\n```js\n// index.js\n\nconst { graphqlHandler } = require('graphql-serverless')\nconst express = require('express')\nconst app = express()\nconst { makeExecutableSchema } = require('graphql-tools')\nconst glue = require('schemaglue')\n\nconst { schema, resolver } = glue('src/graphql')\n\nconst executableSchema = makeExecutableSchema({\n\ttypeDefs: schema,\n\tresolvers: resolver\n})\n\nconst graphqlOptions = {\n\tschema: executableSchema,\n\tgraphiql: { // If you do not want to host any GraphiQl web interface, leave this property undefined.\n\t\tendpoint: '/graphiql' \n\t}\n}\n\n// Host a GraphQl API on 2 endpoints: '/' and '/graphiql'. '/graphiql' is used to host the GraphiQL web interface.\n// If you're not interested in the GraphiQl web interface, leave the above 'graphqlOptions.graphiql' undefined and \n// replace the path following ['/', '/graphiql'] with '/'.\napp.all(['/', '/graphiql'], graphqlHandler(graphqlOptions))\n\n// Starting the server \napp.listen(4000, () =\u003e console.log('Server start. Go to http://localhost:4000/graphiql'))\n```\n\nSimply run `node index.js` and then browse to [http://localhost:4000/graphiql](http://localhost:4000/graphiql).\n\n## Typescript Support \u0026 Custom Globbing\n\nBy default, schemaglue uses .js files to define resolvers and .graphql files to define schemas. If your project uses Typescript, it is possible to change the default behavior to target resolvers that use .ts files:\n\n```js\nconst { schema, resolver } = glue('src/graphql', { mode: 'ts' })\n```\n\nYou can go even further by defining your own custom globbing rule if you want to only include certain resolver files:\n\n```js\nconst { schema, resolver } = glue('src/graphql', { mode: 'product/*.js' })\n```\n\nThe above will only get resolvers defined under the `src/graphql/product/` folder.\n\n\n## Ignoring Certain Files\nIn some cases, you might want to ignore some specific files under the schema folder (by default, SchemaGlue will take into account all .js files). SchemaGlue adds support to ignore files or folders using [globbing](https://github.com/isaacs/node-glob):\n```js\nconst { schema, resolver } = glue('./src/graphql', { ignore: '**/somefile.js' })\n```\nThis will take into account all .js files under the folder _./src/graphql_, excluding all _somefile.js_ files. The _**ignore**_ property supports both a single string or an array of strings. \n```js\n// Ignore more than 1 specific .js file\nconst { schema:schema1 } = glue('./src/graphql', { ignore: ['**/somefile.js', '**/someotherfile.js'] })\n// Ignore all files under the ./src/graphql/variant folder\nconst { schema:schema1 } = glue('./src/graphql', { ignore: 'variant/**' })\n```\n\n## Custom Extensions\n\nYou can specify a custom glob to select your resolver files with different extensions.\n```js\nconst { schema, resolver } = glue('./src/graphql', { js: '**/*.ts' })\n```\n\n## Unions \u0026 Interfaces\n\nIf you're not familiar with this concept, check out this great article [GraphQL Tour: Interfaces and Unions](https://medium.com/the-graphqlhub/graphql-tour-interfaces-and-unions-7dd5be35de0d). \n\nIn our case, we're interested is knowing how to structure our code with unions or interfaces. If your schema is small, I would recommend to manage your unions and intefaces definitions inside a single schema.js file per model:\n```\n- src/\n\t|__ graphql/\n\t\t\t|__ product/\n\t\t\t|\t\t|__ schema.graphql\n\t\t\t|\t\t|__ resolver.js\n\t\t\t|\n\t\t\t|__ variant/\n\t\t\t\t\t\t|__ schema.graphql\n\t\t\t\t\t\t|__ resolver.js\n\n- index.js\n- package.json\n```\nLet's take the _schema.graphql_ and _resolver.js_ under _src/graphql/product/_ as an example:\n\n_schema.graphql_\n```js\nunion Product = Bicycle | Racket\n\ntype Bicycle {\n\tid: ID!\n\tbrand: String!\n\twheels: Int!\n}\n\ntype Racket {\n\tid: ID!\n\tbrand: String!\n\tsportType: SportType!\n}\n\nenum SportType {\n\tTENNIS\n\tSQUASH\n}\n\ntype Query {\n\t# ### GET products\n\t#\n\t# _Arguments_\n\t# - **id**: Product id (optional)\n\tproducts(id: Int): [Product]\n}\n```\n\n_resolver.js_\n```js\nconst { graphqlError } = require('graphql-serverless')\n\nconst productMocks = [{ \n\tid: 1,\n\tbrand: 'Giant',\n\twheels: 2 \n},{ \n\tid: 2,\n\tbrand: 'Prince',\n\tsportType: 'TENNIS' \n}]\n\nexports.resolver = {\n\tQuery: {\n\t\tproducts(root, { id }, context) {\n\t\t\tconst results = id ? productMocks.filter(p =\u003e p.id == id) : productMocks\n\t\t\tif (results.length \u003e 0)\n\t\t\t\treturn results\n\t\t\telse\n\t\t\t\tthrow graphqlError(404, `Product with id ${id} does not exist.`)\n\t\t}\n\t},\n\n\tProduct: {\n\t__resolveType(obj, context, info) {\n\t\treturn\tobj.wheels ? 'Bicycle' :\n\t\t\tobj.sportType ? 'Racket' : null\n\t}\n\t}\n}\n```\n\u003e Notice you need to define a _resolveType_ method for the _Product_ type under the _exports.resolver_\n\n## Mix `.graphql` files with inline string schemas\n\n```js\nconst glue = require('schemaglue')\n\nconst { schema } = glue('src/graphql', {\n\tschemas:[`\n\ttype Product {\n\t\tid: ID\n\t\tname: String\n\t}\n\n\ttype Query {\n\t\tproducts(id:ID, name:String): [Product]\n\t}`,\n\t`\n\tenum VehicleEnum {\n\t\tcar\n\t\tbike\n\t\tbus\n\t}\n\n\ttype Mutation {\n\t\tcreateCar: Car\n\t}\n\t`]\n})\n```\n\n## Replacing `.graphql` files with plain `.js` or `.ts` files\n\nThere are some edge cases where some software engineers may want to express their GraphQL schema using `.js` or `.ts` files rather than `.graphql` files (e.g., [Typescript support](#typescript-support)). \n\nIn that case, you will have to transform your files as follow:\n\n__`product.graphql` example:__ \n\n```graphql\ntype Product {\n\tid: ID!\n\tname: String!\n\tshortDescription: String\n}\n\ntype ProductNameChangedMsg {\n\tid: ID!\n\tname: String\n}\n\ntype Query {\n\tproducts(id: Int): [Product]\n}\n\ntype Mutation {\n\tproductUpdateName(id: Int, name: String): ProductNameChangedMsg\n}\n\ntype Subscription {\n\tproductNameChanged(id: Int): ProductNameChangedMsg\n}\n```\n\n__`product.js` example:__ \n\n```js\nexports.schema = `\ntype Product {\n\tid: ID!\n\tname: String!\n\tshortDescription: String\n}\n\ntype ProductNameChangedMsg {\n\tid: ID!\n\tname: String\n}\n`\n\nexports.query = `\n\tproducts(id: Int): [Product]\n`\n\nexports.mutation = `\n\tproductUpdateName(id: Int, name: String): ProductNameChangedMsg\n`\n\nexports.subscription = `\n\tproductNameChanged(id: Int): ProductNameChangedMsg\n`\n```\n\n# Typescript support\n\nAs explained in the [Typescript Support \u0026 Custom Globbing](#typescript-support--custom-globbing) section, Schemaglue supports resolvers written in Typescript. However, Typescript is less than friendly with the `.graphql` file extension. The main challenge occurs when the Typescript code is compiled (for example into a `dist` folder). You'll notice that the `.graphql` files are omitted, therefore breaking your code in production. This article explains how to use Webpack to include those `.graphql` files: [How to resolve import for the .graphql file with typescript and webpack](https://dev.to/open-graphql/how-to-resolve-import-for-the-graphql-file-with-typescript-and-webpack-35lf).\n\nHowever, for those of you who do not wish to mess up with more Webpack configuration, there is a solution with a trade-off. Schemaglue supports GraphQL schema file written in plain JS or TS as explained in the [Replacing `.graphql` files with plain `.js` or `.ts` files](#replacing-graphql-files-with-plain-js-or-ts-files) section. You will loose in readability as your GraphQL schema will have to be expressed as raw Javascript strings. To make this work, update the your code as follow:\n\nBefore:\n\n```js\nconst { schema, resolver } = glue('src/graphql', { mode:'ts' })\n```\n\nAfter:\n\n```js\nconst { schema, resolver } = glue('src/graphql', { mode:'**/*.[jt]s' })\n```\n\nThis example above helps reading `.ts` files and `.js` files at the same time. This is required as your `.ts` files are compiled to `.js` files in your `dist` folder. \n\n\nIf you choose that convention, the GraphQL schema will be properly exported to your `dist` folder.\n\n# Contribute\n## General Guidance\nWe're always super excited to accept pull-requests. We're not too strict about how you implement your fixes or desired features, but we would still highly appreciate if you could:\n\n1. Lint your code using the command `npm run eslint` before pushing your pull-request.\n2. Make sure you've added a unit test under the `test` folder (more about that in the following section).\n3. Make sure all the unit tests pass by running `npm test`\n\n### THANKS A LOT YOU AWESOME CONTRIBUTOR!\n\n## Unit Testing\nAll unit tests are located under the `test` folder. There, you will notice 3 main components:\n\n1. `graphql` folder: This folder contains a series of mock files that you should use to test schemaglue. Feel free to add your own, but please, stick to the already defined naming convention.\n2. `index.js`: This file is the main unit test file. You will most probably add your unit test there. Please, stick with the naming convention in that file.\n3. `utils.js`: This file contains the unit tests for the src/utils.js code. Please, stick with the naming convention in that file.\n\nTo run the test, simply execute this command: `npm test`.\n\n# This Is What We re Up To\nWe are Neap, an Australian Technology consultancy powering the startup ecosystem in Sydney. We simply love building Tech and also meeting new people, so don't hesitate to connect with us at [https://neap.co](https://neap.co).\n\nOur other open-sourced projects:\n#### Web Framework \u0026 Deployment Tools\n* [__*webfunc*__](https://github.com/nicolasdao/webfunc): Write code for serverless similar to Express once, deploy everywhere. \n* [__*now-flow*__](https://github.com/nicolasdao/now-flow): Automate your Zeit Now Deployments.\n\n#### GraphQL\n* [__*graphql-serverless*__](https://github.com/nicolasdao/graphql-serverless): GraphQL (incl. a GraphiQL interface) middleware for [webfunc](https://github.com/nicolasdao/webfunc).\n* [__*schemaglue*__](https://github.com/nicolasdao/schemaglue): Naturally breaks down your monolithic graphql schema into bits and pieces and then glue them back together.\n* [__*graphql-s2s*__](https://github.com/nicolasdao/graphql-s2s): Add GraphQL Schema support for type inheritance, generic typing, metadata decoration. Transpile the enriched GraphQL string schema into the standard string schema understood by graphql.js and the Apollo server client.\n* [__*graphql-authorize*__](https://github.com/nicolasdao/graphql-authorize.git): Authorization middleware for [graphql-serverless](https://github.com/nicolasdao/graphql-serverless). Add inline authorization straight into your GraphQl schema to restrict access to certain fields based on your user's rights.\n\n#### React \u0026 React Native\n* [__*react-native-game-engine*__](https://github.com/bberak/react-native-game-engine): A lightweight game engine for react native.\n* [__*react-native-game-engine-handbook*__](https://github.com/bberak/react-native-game-engine-handbook): A React Native app showcasing some examples using react-native-game-engine.\n\n#### Tools\n* [__*aws-cloudwatch-logger*__](https://github.com/nicolasdao/aws-cloudwatch-logger): Promise based logger for AWS CloudWatch LogStream.\n\n\n# License\nCopyright (c) 2018, Neap Pty Ltd.\nAll rights reserved.\n\nRedistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:\n* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.\n* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.\n* Neither the name of Neap Pty Ltd nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.\n\nTHIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS \"AS IS\" AND\nANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED\nWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE\nDISCLAIMED. IN NO EVENT SHALL NEAP PTY LTD BE LIABLE FOR ANY\nDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES\n(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;\nLOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND\nON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT\n(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS\nSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.\n\n\u003cp align=\"center\"\u003e\u003ca href=\"https://neap.co\" target=\"_blank\"\u003e\u003cimg src=\"https://neap.co/img/neap_color_horizontal.png\" alt=\"Neap Pty Ltd logo\" title=\"Neap\" height=\"89\" width=\"200\"/\u003e\u003c/a\u003e\u003c/p\u003e\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnicolasdao%2Fschemaglue","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fnicolasdao%2Fschemaglue","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnicolasdao%2Fschemaglue/lists"}