Knappi codingWritten by Nils Knappmeier who has been a full-time web-developer since 2006, programming since he was 10 years old.
When I ran out of CI/CD minutes on gitlab.com, I had to find a solution to run my own gitlab-runner, preferably so that I didn't have to pay for the computing time. I decided to run it on my own computer.
This article shows two tools that help you write tests with the mock-service-worker library.
The mock-service-worker can be used to mock backends. You can use it in tests, but also in demos. Unlike real http-server frameworks like express.js, the mock-service-worker does not have that notion have "middleware", and I struggled a bit my mock-authentication for the Gachou demo implemented... Here is a solution, and may be feature-suggestion for the mswjs team.
We can convert OpenAPI specs to TypeScript clients. We can create mock-APIs with the mock-service-worker library. How about converting an OpenAPI spec to TypeScript types for the mock-service-worker library. It's magic...
End-to-end tests tend to be slow and flaky. So how about using a mock backend to test your frontend. The "mock-service-worker" library helps you create such backends. And you can use it for more than just testing.
Many backend frameworks, independent of the language in use, can automatically generate OpenAPI specifications the server code. We can use this specification to build documentation and a user-interface for testing. But we can also use it to generate client code for our web-frontend. Here are some code-generators.
When going mono-repo, I noticed that the Node.js package "husky" can actually be replaced by a single line of code. And it works for people that do not have Node.js installed.
How I converted my project of three repositories into one monorepo - without losing the git history!
I actually wanted to use Preact for my pet project. Several build-tools and frameworks later, I stuck with the things that I know mostly. Read on, if you are interested in a non-comprehensive evaluation...
End-to-End tests require the whole application to be running. This includes backend and database - which have to talk to each other. I thought it was not possible to do such a setup in Gitlab-CI. Now I know better.
In Spring-Boot, creating test-data was easily done via the `@SqlGroup`. Quarkus does not support this feature. Even worse: If you want to run Quarkus-tests against a native image, you don't have access to the internals of the project at all. This article describes my way of solving the issue of providing predictable test-data to integration tests.
For my pet-project Gachou, I decided to use Java and Quarkus to implement the backend. And since I have used clean-architecture at work for a couple now, I decided to use the same thing here. A pity, that we always used Spring Boot and Quarkus has some quirks of its own in this respect. Read on, if you want to know how I solved the exercise...
The obvious benefits of TypeScript is type-safety in function calls, variables assignments and so on. This post describes use-cases that are not obvious, but can still help you with your typings: The benefit of using typed strings in your path-patterns and router-functions.
This article describes the basic project setup of the Gachou frontend in more detail.
The ultimate frontend setup I had the luck to work on two green-field projects in the last one and two years. The frontend setup, that we…
A couple of years ago, I was looking for software to manage our family photos and videos. The following features were important to me…
