Uncaptured server errors on 404

It looks like right now the server reports 404’s on the console. Sometimes like this (http://localhost:3000/category/performance/):

An error ocurred fetching '/category/mobile-performance/':
 Error: Entity of from endpoint 'categories' with slug 'mobile-performance' not found
    at Api.getIdBySlug (webpack-internal:///./node_modules/@frontity/wp-source/src/libraries/api.ts:9:227)
    at process._tickCallback (internal/process/next_tick.js:68:7)

and sometimes like this (http://localhost:3000/page/8):

An error ocurred fetching '/':
 TypeError: Cannot destructure property `id` of 'undefined' or 'null'.
    at entityList.map (webpack-internal:///./node_modules/@frontity/wp-source/src/libraries/populate.ts:6:47)
    at Array.map (<anonymous>)
    at populate (webpack-internal:///./node_modules/@frontity/wp-source/src/libraries/populate.ts:6:43)
    at process._tickCallback (internal/process/next_tick.js:68:7)

[DAreRodz]

Yeah, well, most cases are expected to return with a 404 page but not all of them (for example, when the server returns a 500 error). And it would also be nice if the error messages were more descriptive for developers.

We have to think of a good way to handle errors.

[luisherranz]

Closed as this doesn’t seem to be an issue anymore.