You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is this issue currently blocking your project? (yes/no): no
is this issue affecting a production system? (yes/no): no
Context
node version: v12+
module version: v5/v6
environment (e.g. node, browser, native): node
used with (e.g. hapi application, another framework, standalone, ...): hapi
any other relevant information: This would be a breaking change that would propagate to hapi's API 🚨 , since hapi exposes an instance of mimos through server.mime.
What problem are you trying to solve?
The interface of the Mimos instance can be awkward to work with (particularly with typescript) because mimos.type() returns an empty object {} when there is no mime type match, and an object with some properties when there is a match.
Do you have a new or modified API suggestion to solve the problem?
The proposal from #37 is for mimos.path() to return null when there is no mime type match.
The text was updated successfully, but these errors were encountered:
Support plan
Context
server.mime
.What problem are you trying to solve?
The interface of the
Mimos
instance can be awkward to work with (particularly with typescript) becausemimos.type()
returns an empty object{}
when there is no mime type match, and an object with some properties when there is a match.Do you have a new or modified API suggestion to solve the problem?
The proposal from #37 is for
mimos.path()
to returnnull
when there is no mime type match.The text was updated successfully, but these errors were encountered: