-
-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v2 Feedback request] Resolving conflicts over extensions #162
Labels
Comments
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. |
v2 is out. closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: