feat: mark MIMEType as stable #56548
Draft
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The PR proposes to graduate
MIMEType
utility class from experimental to stable (or drop it completely, also a possible option).This class was introduced in Node.js v19.1.0 and v18.13.0 as an experimental feature (circa 2 years ago). It provides a utility class for working with MIME types.
The number of issues and PRs related to this class has been minimal and the API has not suffer biggest changes since its introduction.
Most of the issues related to it has been for extensions or mere references to it.
mimetype
- 4 issues - 3 PRsmime type
- 3 issues - 3 PRsIts adoption can be considered as lower in range, doing a quick search of
new MIMEType
in GitHub, seems to throw a vast majority of resultsrelated to the
whatwg-mime
userland library (util.MIMEType
is also based onWHATWG
MIME Type spec.).These are the few known limitations of the class: