Lambdas handlers can be invoked with many different, but always complex, event arguments. Add to that the context, callback, matching return type and you basically start listing all the different ways that your function can fail in production.

From time to time you might need to expose your locally running service to the external world - for example you might want to test a webhook that calls your service. To speed up the test/development feedback loop it would be great to be able to point that webhook to your local machine.

From time to time I still see a for loop in JavaScript codebases. Linters are frequently angry about them. Let's see how we can replace them.

Simplify your Chimp-based project even further with a new @predefined Scalar directive.

In today's video I go through a preparation of the official Apollo Platform Tutorial App for adding Chimp to it. I decided to divide that task into two steps - first is adding TypeScript to the codebase. Watch me work, struggle, fly through code, hopefully you will learn some tricks :)

A discussion about issues we've stumbled upon and a solution that simplified our CDK workflow.

We've just released a new version of the cypress-cucumber-preprocessor package with TSX/React testing and Multiline Step Arguments.

The Chimp 3.0 and previous versions always generated resolveReferences resolvers for all federated types. It turned out to be excessive, so we make it configurable.

Introducing useComplexState hook, - a small wrapper combining Redux Toolkit, useReducer with some extra syntax sugar to make things even simpler and more to-the-point.

A few patterns to help you deal with randomness in your codebase.

Short discussion about helpful error messages, and a solution to the problem

A simple example that demonstrates when useState is no longer a good idea, and how to make useReducer less scary to work with.

We are happy to announce that the example showing many advanced patterns related to GraphQL usage is updated to Chimp 3.0

I'm sharing my day-to-day pattern for prototyping with JavaScript

If you have been doing serious work with GraphQL over the last few years, you surely saw the "more than one instance of GraphQL error". Let me help you deal with it.

We will show you how to add chimp to an existing application based on our simple example

We've rewrote Chimp, simplified the setup and fixed some defaults. We hope you will enjoy the new development experience!

What do you do when you are in need to figure out a complex type? Many just give up - they either make a use of any or jump through a lot of hoops that in the end makes their code less maintainable.. but at least they didn't have to figure out the types, right? :)

Simple git trick to have a global .gitignore file

TypeScript documentation generously helps us with an example, that, usually does not work out of the box.

Learn how to write automate tests for your federated GQL µservices