Skip to content

Releases: HiThereCommunity/example-graphql-server

v1.1

24 Sep 21:19

Choose a tag to compare

Improvement

  • Improvement to the development workflow. npm run start now automatically performs a flow and linter check on every file change in addition to restarting the server.
  • Improved the production workflow. npm run serve now automatically compiles and runs the code in the background using forever.
  • Errors returned by the graphql response when running the server in development contain the stacktrace; this makes debugging the code a lot easier.

Removed

  • Removed support for windows. Supporting both linux and windows overcomplicated the project.
  • Removed the tutorial from the project. It was too difficult to keep in sync with the actual code in repo anymore given that the project was becoming a bit larger.

v1.0.3

28 Aug 13:40

Choose a tag to compare

  • Added the linter standard to the project and updated the existing
    code to conform to the linter. The linter can be run using the command
$ npm run lint
  • Updated dependency graphql to v0.7.0. The dependency
    express-graphql had to be updated to 0.5.4 support this change.

v1.0.2

12 Aug 07:17

Choose a tag to compare

  • Added support for starting the server on windows using the scripts: npm run startWindows and npm run serveWindows.
  • Updated the tutorial with a description on how to set the environment variables to distinguish between development and production.

v1.0.1

04 Aug 19:54

Choose a tag to compare

  • Added development/production as an environment variable in node that can be accessed using process.env.NODE_ENV.
  • The production server automatically runs on port 80
  • The development server automatically runs on port 3000
  • Added better definition of the node versions that are supported for running the server in the package.json

v1.0.0

30 Jul 11:20

Choose a tag to compare

Initial release