mime-db vs mime-types
MIME Type Libraries Comparison
1 Year
mime-dbmime-typesSimilar Packages:
What's MIME Type Libraries?

MIME type libraries are essential for web development as they provide a way to map file extensions to their respective MIME types. This mapping is crucial for serving the correct content type in HTTP responses, ensuring that browsers handle files appropriately. The two packages, 'mime-db' and 'mime-types', serve this purpose but have different functionalities and use cases. 'mime-db' is a comprehensive database of MIME types and their associated file extensions, while 'mime-types' is a utility for working with MIME types, allowing for easy retrieval and manipulation of MIME types based on file extensions or vice versa.

Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
mime-db70,806,0481,137219 kB477 months agoMIT
mime-types63,190,0001,36018.3 kB11-MIT
Feature Comparison: mime-db vs mime-types

Data Source

  • mime-db:

    The 'mime-db' package provides a comprehensive and detailed database of MIME types, including their associated file extensions, media types, and other relevant metadata. It is regularly updated to include new MIME types and is suitable for applications that require a thorough understanding of MIME types across various file formats.

  • mime-types:

    The 'mime-types' package is a lightweight utility that offers a predefined set of MIME types and their corresponding file extensions. It does not provide a full database but focuses on quick lookups and basic MIME type functionality, making it less comprehensive than 'mime-db'.

Usage Complexity

  • mime-db:

    Using 'mime-db' can be more complex due to its extensive dataset, requiring developers to understand how to query and utilize the data effectively. It is designed for applications that need detailed MIME type information and may involve more intricate logic to handle various file types.

  • mime-types:

    The 'mime-types' package is straightforward and easy to use. It provides simple methods for retrieving MIME types based on file extensions and vice versa, making it ideal for developers looking for quick and efficient MIME type handling without additional complexity.

Performance

  • mime-db:

    Due to its comprehensive nature, 'mime-db' may introduce some performance overhead when accessing its extensive dataset. However, it is optimized for quick lookups, and the trade-off for detailed information is often worth it for applications that require accuracy in MIME type handling.

  • mime-types:

    The 'mime-types' package is optimized for performance, allowing for rapid retrieval of MIME types with minimal overhead. It is ideal for applications that prioritize speed and efficiency, especially when dealing with a high volume of requests.

Maintenance and Updates

  • mime-db:

    The 'mime-db' package is actively maintained and regularly updated to include new MIME types and changes in standards. This ensures that developers have access to the latest information and can serve files with the correct MIME types accurately.

  • mime-types:

    The 'mime-types' package is also maintained but may not receive updates as frequently as 'mime-db'. It is suitable for applications that do not require the latest MIME type information and can operate with a stable set of predefined types.

Extensibility

  • mime-db:

    'mime-db' allows for extensibility as developers can add custom MIME types and file extensions to the database if needed. This feature is beneficial for applications that handle unique file types not covered by standard MIME types.

  • mime-types:

    The 'mime-types' package is less extensible compared to 'mime-db' since it relies on a predefined set of MIME types. Customization is limited, making it less suitable for applications that require handling of non-standard file types.

How to Choose: mime-db vs mime-types
  • mime-db:

    Choose 'mime-db' if you need an extensive and up-to-date database of MIME types for various file formats. It is particularly useful for applications that require detailed MIME type information and support for a wide range of file types. This package is ideal for backend services that need to serve files with the correct MIME type based on their extensions.

  • mime-types:

    Choose 'mime-types' if you need a lightweight utility for quickly retrieving MIME types based on file extensions or vice versa. It is best suited for applications that require simple and efficient MIME type handling without the overhead of a full database. This package is ideal for scenarios where performance and simplicity are prioritized.

README for mime-db

mime-db

NPM Version NPM Downloads Node.js Version Build Status Coverage Status

This is a large database of mime types and information about them. It consists of a single, public JSON file and does not include any logic, allowing it to remain as un-opinionated as possible with an API. It aggregates data from the following sources:

  • https://www.iana.org/assignments/media-types/media-types.xhtml
  • https://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/conf/mime.types
  • https://hg.nginx.org/nginx/raw-file/default/conf/mime.types

Installation

npm install mime-db

Database Download

If you intend to use this in a web browser, you can conveniently access the JSON file via jsDelivr, a popular CDN (Content Delivery Network). To ensure stability and compatibility, it is advisable to specify a release tag instead of using the 'master' branch. This is because the JSON file's format might change in future updates, and relying on a specific release tag will prevent potential issues arising from these changes.

https://cdn.jsdelivr.net/gh/jshttp/mime-db@master/db.json

Usage

var db = require('mime-db')

// grab data on .js files
var data = db['application/javascript']

Data Structure

The JSON file is a map lookup for lowercased mime types. Each mime type has the following properties:

  • .source - where the mime type is defined. If not set, it's probably a custom media type.
  • .extensions[] - known extensions associated with this mime type.
  • .compressible - whether a file of this type can be gzipped.
  • .charset - the default charset associated with this type, if any.

If unknown, every property could be undefined.

Contributing

The primary way to contribute to this database is by updating the data in one of the upstream sources. The database is updated from the upstreams periodically and will pull in any changes.

Registering Media Types

The best way to get new media types included in this library is to register them with the IANA. The community registration procedure is outlined in RFC 6838 section 5. Types registered with the IANA are automatically pulled into this library.

Direct Inclusion

If that is not possible / feasible, they can be added directly here as a "custom" type. To do this, it is required to have a primary source that definitively lists the media type. If an extension is going to be listed as associateed with this media type, the source must definitively link the media type and extension as well.

To edit the database, only make PRs against src/custom-types.json or src/custom-suffix.json.

The src/custom-types.json file is a JSON object with the MIME type as the keys and the values being an object with the following keys:

  • compressible - leave out if you don't know, otherwise true/false to indicate whether the data represented by the type is typically compressible.
  • extensions - include an array of file extensions that are associated with the type.
  • notes - human-readable notes about the type, typically what the type is.
  • sources - include an array of URLs of where the MIME type and the associated extensions are sourced from. This needs to be a primary source; links to type aggregating sites and Wikipedia are not acceptable.

To update the build, run npm run build.