Tangible Bytes

This is one of those things I wont need again for a while and will forget.

When using nvm to get a new version of nodejs you can find you no longer have packages - including yarn

The JavaScript ecosystem is a sea of choices and it seems to be all too easy to make an incompatible selection.

In my case I am using the Yarn package manager, the VSCode editor and TypeScript flavoured JS (I don’t think it really counts as a different language)

Every import statement was triggering an error in VScode

Cannot find module ’’ or its corresponding type declarations

Hugo - The world’s fastest framework for building websites is pretty awesome. It’s what I use to manage this site.

But much of the web development world has moved in the direction of JavaScript, npm, and Webpack.

So how can you run a Hugo website and manage the embedded JavaScript and CSS that are most commonly managed with npm and Webpack?

What’s the difference between providing a rejection handler for a promise and catching errors ?

And why Does the React AJAX FAQ say

// Note: it's important to handle errors here
// instead of a catch() block so that we don't swallow
// exceptions from actual bugs in components.

Setting up Sonarcloud integration with Gitlab was so easy as to be not worth documenting - just setup an account at each, import your projects on Sonarcloud and follow the step by step guide to start analysis.

But getting test coverage reports was harder.

I’ve been writing software for long enough to know that it pays to be careful at the start. You don’t always know when you’ll be supporting a project long term and may need to upgrade versions of your framework and related tools.

These are my notes of starting to use React with an eye to long term support.