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
do you want to share maintenance? you could add me as a collaborator or i can add you to the expressjs org and you can move this repo to the organization. this library is pretty much used everywhere in node, so it would be nice if there were more collaborators.
Types used by express core are probably of universal enough interest to warrant adding them to node.types in this project.
I'm not sure about the contentType method. 'Kind of thinking that might be best left out of the core API, but not 100% sure. However I do think globally extending the mime API is bad practice if it can be avoided. It's going to lead to confusion over what methods are actually part of mime .vs. what aren't. And lead to breakage of code that depends on the express version of the mime API, when that code is pulled into non-express projects.
what about the other types? there are PRs about them that are still open. don't really want to create more unless you merge them or just add me as a collab/move to expressjs
there are a bunch of mime types i want to add as well as features. for now, i just created https://github.com/expressjs/mime-extended instead of bothering making PRs.
do you want to share maintenance? you could add me as a collaborator or i can add you to the expressjs org and you can move this repo to the organization. this library is pretty much used everywhere in node, so it would be nice if there were more collaborators.
this module would play very nicely with a lot of mime-related utilities in the organization like https://github.com/expressjs/compressible
The text was updated successfully, but these errors were encountered: