New Features

• Run Slicknode locally or host it in any data center with: slicknode start
• Apply database migrations after schema changes: slicknode migrate
• Slicknode runtime handlers now support ESM modules.

Check out the documentation for more details.

New Features

• Create projects from Git URL, for example:

   slicknode init my-project https://github.com/slicknode/starter-nextjs-blog.git
  

• slicknode module create now creates a template with examples and documentation.

Improvements:

• slicknode deploy can now be executed in a project that does not have cached dependencies loaded. This allows you to clone a repository and just run slicknode deploy to deploy a backend, without having to run slicknode pull first.
• Console/playground URLs are now loaded dynamically from the API instead of hardcoded values from the config. URLs are removed from the local .slicknoderc file to keep them upgradeable in the future.

Bugfixes

• Fail with error message if project is initialized in an existing directory with content
• Improve cluster latency accuracy with keepAlive, reduce timeout

New Features

• Multi-cluster support
• Support for extensions written in NodeJS 10x, 12x

New Features

• New command slicknode module remove <module-name> to remove a module folder via CLI #17

• The runtime can now be launched on a local machine for improved development workflows:
  slicknode runtime start --watch

  The --watch flag enables hot reload.

This release comes with some major changes. The underlying library for the CLI was migrated to oclif. This allows for better testing, extensibility, etc.

Breaking

The GraphQL version was upgraded to 14.3. This version has a stricter validation of directives in the GraphQL schema. The builtin directives were previously not part of the schemas, therefore validation and deployment will fail with those directives missing.

To be able to validate the schema again and deploy changes, the schemas have to be updated in the project directories:

slicknode pull

Afterwards, everything should work as usual, just with strict directives validation.