Re: [Json] Add Extension to JS MIME

["Matthew A. Miller" <[e-mail]>]

On 17/08/09 07:34, Bradley Meck wrote:
> Hiya!
> 
> I would like to ask about adding a new file extension to the IANA MIME
> registry for `application/javascript`. It seems the IESG is in charge of
> that mime
> per https://www.iana.org/assignments/media-types/application/javascript
> <https://www.iana.org/assignments/media-types/application/javascript> .
> 
> The change request is to add `.mjs` as a known extension as Node.js
> merges support for the new Module parse goal of JavaScript. Doing so as
> the PR is merged seemed the best way to get people to update their MIME
> libraries in a timely manner as well.
> 
> Let me know what I need to do to get this process started / if there is
> some better place to ask.
> 

Hello Bradley,

I think the right approach here is create an internet-draft upating RFC
4329, adding .mjs as one of the extensions for "application/javascript".
 That I-D would likely need to be [DISPATCH]ed, as there is no existing
WG  I can see that covers this.

For the document, at the very least it seems necessary to update the
ECMA-262 reference in addition to the updated IANA instructions.  I'm
not sure much of anything does need to be said about differences between
.mjs versus .js -- the content is still JavaScript, but hinting at
differences in module expectations.

The IANA considerations section itself, I don't know what the right
wording is in this case.  I think almost everything stays the same,
other than the file extension(s), and the published specification?


- m&m

Matthew A. Miller
< http://goo.gl/LM55L >

PS: Thanks to Adam Roach for confirming my thoughts, and suggesting some
places to look at.

[DISPATCH] - https://datatracker.ietf.org/wg/dispatch/about/