Home / Blog /

GatsbyJS And OpenBSD: Outta Luck I'm Afraid

  • 2
  • 2 mins

If you've been following me for a while (since I started the iBSD channel), you'll remember that I started messing around with Jekyll after 10 years of Wordpress, fell in love with it, then used it to build the first iBSD site.

Well, static site generators have become a massive rabbit hole since then.

It's become an obsession. :smile:

I moved on to Hugo, then Gridsome and now finally GatsbyJS, and I've built over a dozen income-generating websites using GatsbyJS (it's only my main language blog that I still haven't rebuilt yet).

In the span of about 12 months, I've gone from zero knowledge of React to building web apps, dashboards and blogs for various niche projects.


As you can tell, I've redeveloped the original iBSD site as a GatsbyJS site (getting between 96 - 99 performance score through Google Lighthouse).

It's still a bit rough in design but I'm mostly happy with it.

There's only one problem.

OpenBSD does not play nice with GatsbyJS

I use FreeBSD with Gatsby which works pretty much flawlessly (some minor issues with pngquant and sharp but easy to remedy).

OpenBSD won't work with GatsbyJS, however.

I think it's a sharp issue but not sure - mostly ends up with:

ERR! cb() never called

No verbose details on why shit isn't working.

I'm out of ideas.

Anyone managed to get GatsbyJS working properly in OpenBSD?

It's frustrating because my laptop runs OpenBSD but this means that I can only maintain/develop for web at home on my FreeBSD machine (or SSH into another machine to develop).

If you've had success -- or care to try -- please comment below and offer some pointers.


Redpill your friends:
Donovan Nagel
Applied Linguistics graduate, translator and entrepreneur who uses FreeBSD and OpenBSD exclusively for work.
Subscribe to my YouTube channel.

Got something to share?

Comment Policy: This is a free-speech zone but cuntery isn't tolerated. Also no "Linux can do that" flame wars.
All comments are moderated before being published.
  • This issue is probably related to npm. If you look at the source code, you can see that there was a changeset years ago which added extra logging in case of a "cb() never called" error: https://github.com/npm/cli/commit/8ea0de98563648ba0db032acd4d23d27c4a50a66#diff-ea839362e48d860c85a946add8714476
    My hunch - but it's not a solution of course - is that you are using an older version of npm that doesn't have this extra logging - and maybe even some extra bit of logic. In the OpenBSD package repository as of now the node version is 10.16.3 whereas on FreeBSD it's 13.10.1_1 (I tacitly supposed that you're running FreeBSD 12 and OpenBSD 6.6 at the moment). Could you try updating node on OpenBSD to the newest version and see what happens if you retry? In the OpenBSD 6.7 repository I found node version 12.16.1, maybe that will work.

  • @Bran,

    Thanks for this.

    I'll give this a try hopefully this week and get back to you on it.