“Fake” e2e tests with react-testing-library
How to run fake e2e tests using react-testing-librabry? Here's a quick tutorial on how to speed up your feedback loop when working in front end applications.
37 posts
Tech debt & refactoring an old front-end codebase: a field manual
Improve your front-end project's performance and maintainability with our guide to refactoring a codebase. Learn about tackling technical debt, assessing your code, planning a strategy, and exploring refactoring techniques.
Why you don't need estimates
How should you estimate your work? Are estimations needed when developing software? What is the value of estimations? What is an alternative to estimating work?
Why is it good to deploy frequently
Do you deploy every day? Your team probably should. Here's why.
Modern front-end monorepos — Part 2: running scripts
In the previous article, we set up a monorepo project with 2 applications and a package. We also enabled Yarn workspaces to manage the dependencies and linking of the workspaces. One inconvenience so far was having to start 2 separate terminal windows to run the applications. This isn’t a...
Modern front-end monorepos — Part 1: managing dependencies and sharing code
I’ve really learned to love a good monorepo setup, a repository that contains multiple packages and/or applications. Being able to make changes across applications or packages in 1 pull request (PR), having the option to centralize and reuse code over applications, and unifying documentation and processes greatly simplifies...
Creating a Scientific Pitch Notation Type using template literal types
Ok. So. The honeymoon phase is over. I can say TypeScript is steadily becoming a part of my daily stack. While working on converting music-fns from Flow to TypeScript I bumped into a feature I didn’t know existed. But first, a little bit of context. music-fns is a utility...
Serverless functions with Vercel
As you (might) know, our current website is built on Gatsby. I love the fact we’re generating a super cacheable, fully static site with every build, but this adds a couple of limitations. One of the limitations of this setup is having no backend (I know that sounds funny)...
Optimizing JavaScript packages for tree shaking
As an author of (open source) packages, I think you have the responsibility to protect the bundle size of your package consumer. When you publish a package that exports a whole range of modules (for example lodash, ramda, date-fns…) you want to make sure the package is exported in such...