What is the problem this feature will solve?
When a 404 not found response is made for an HTTP/s import, the error thrown is currently:
Error [ERR_NETWORK_IMPORT_BAD_RESPONSE]: import 'https://h3manth.com/foo' received a bad response: HTTP response returned status code of 404
it might be useful to convert this into a full ERR_MODULE_NOT_FOUND error to properly match semantics in error handling code paths.
What is the feature you are proposing to solve the problem?
Return an ERR_MODULE_NOT_FOUND for 404 network errors in HTTP/s imports.
What alternatives have you considered?
Keeping it as a custom error or network not found error creates divergence between local and remote resolvers. It can be useful to streamline the error path handling by having a singular code to check.
What is the problem this feature will solve?
When a 404 not found response is made for an HTTP/s import, the error thrown is currently:
it might be useful to convert this into a full
ERR_MODULE_NOT_FOUNDerror to properly match semantics in error handling code paths.What is the feature you are proposing to solve the problem?
Return an
ERR_MODULE_NOT_FOUNDfor 404 network errors in HTTP/s imports.What alternatives have you considered?
Keeping it as a custom error or network not found error creates divergence between local and remote resolvers. It can be useful to streamline the error path handling by having a singular code to check.