Visiting a non-existing package page returns a 200 OK response with JSON error envelope

[lirantal]

Describe the bug

See screenshot straight from the browser, demonstrating the format of the request package name (that is likely non-existent on the npm registry) and the JSON response data returned in an HTTP 200 OK:

Additional context

Expected outcome would be that the npmx.dev return a 404 page

Logs