Skip To Main Content

Fixing Atlas… maybe?

Atlas is broken!

I tried sending a revalidate argument to getNextStaticProps. But it didn’t work. And now I’m chatting in #pe-atlas-merlin and the engineers are basically saying that Incremental Static Regeneration doesn’t work.

Update: it looks like I’ve uncovered a bug in Faust.js where this revalidate property is not propagated to… next?

While this was being diagnosed I carried on with learning React in Scrimba.

One of the things I don’t like about these JS frameworks is that error messages can be so cryptic and unhelpful.

Today I neglected to export a component. And the message I got?

“A cross-origin error was thrown. React doesn’t have access to the actual error object in development”

So basically “There’s an error but I can’t tell you what it is”.

*sigh*

I did more assembling components though and the syntax of this is becoming second nature now.

categories:Uncategorized
tags:AtlasHeadless