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
After waaay too long, I'm rolling out a v2 to address some long-standing issues with this module. One of which is how to resolve the occasional conflict where more than one type is associated with an extension.
mime-types has a partial solution for this, but this doesn't resolve all conflicts. In v2, I'm planning to do use this approach when compiling type maps to insure they're consistent.
Oddly enough I looked at that recently, and it makes sense from what I recall. Yes, the mime-types method is rudimentary :) I'll try to take a closer look, but from what I recall of the changes it makes a lot of sense.
After waaay too long, I'm rolling out a v2 to address some long-standing issues with this module. One of which is how to resolve the occasional conflict where more than one type is associated with an extension.
mime-types
has a partial solution for this, but this doesn't resolve all conflicts. In v2, I'm planning to do use this approach when compiling type maps to insure they're consistent.See also jshttp/mime-types#23
FYI, What it looks like when resolving the inconsistencies currently in mime-db:
The text was updated successfully, but these errors were encountered: