Custom Content-Type

[trousyt]

Hi, I have a need to serve some non-standard files and currently the plugin uses the mime-types package, which doesn't correctly recognize my file extensions. Would you be opposed to accepting a PR for a change to be able to supply a custom Content-Type when a match is made?

It could look like this:

{
    pattern: /^\/metadata\.json/,
    resolve: "./metadata.json",
    contentType: "application/xml"
}

or possibly even:

{
    pattern: /^\/metadata\.json/,
    resolve: "./metadata.json",
    headers: {
        "Content-Type": "application/xml"
    }
}

[typeparameter]

Hi @trousyt. Pull requests are welcome, so feel free to create one. In fact, this exact use case came up before, but I never found the time to implement something that I liked. Excited to see what you come up with!

[typeparameter]

Hi @trousyt, I've put together a proposed solution for this in #43. If you're still interested in this feature, could you let me know your thoughts on the API for adding custom content types?

[trousyt]

That's exactly what I was looking for.

[github-actions]

🎉 This issue has been resolved in version 2.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀