Fwd: Proposal: Add .mjs file extension to known to be JS
bradley.meck at gmail.com
Tue Jul 13 17:48:51 UTC 2021
The proposal instructions on the nginx website state that it is for
bug fixes and so it seems that would be the wrong place to put a proposal.
I can do so and cross reference.
To be clear; whatwg is using it in their specifications without any Node
usage implied; if files are produced with that file extension by copy and
pasting the specification examples (such as those in HTML Standard
they would fail on nginx. There is also an IETF MIME update that should
ECMAScript Media Types Updates
the goal is not to be compatible, but only to apply to file extensions
after they are popular, that seems a bit odd to me at least since it means
knowing that upcoming things are potentially incompatible and willfully not
preparing until after the problems occur.
On Tue, Jul 13, 2021 at 12:36 PM Maxim Dounin <mdounin at mdounin.ru> wrote:
> On Mon, Jul 12, 2021 at 09:24:49AM -0500, Bradley Farias wrote:
> > See Add .mjs file extension to known JS mime types by bmeck · Pull
> > #71 · nginx/nginx (github.com) <https://github.com/nginx/nginx/pull/71>
> > the related Use .mjs for modules more consistently by mathiasbynens ·
> > Request #3810 · whatwg/html (github.com)
> > <https://github.com/whatwg/html/pull/3810>
> Interestingly enough, the pull request in whatwg you are referencing
> claims that "on the web file extensions doesn't matter", yet your
> suggested change means exactly the opposite.
> For a mime.types change you think is needed, consider opening a
> ticket on trac.nginx.org. If/when there is a consensus that the
> change is needed, the change will be committed. For now the mjs
> extension does not seem to be widely used except by Node.js.
> Maxim Dounin
> nginx-devel mailing list
> nginx-devel at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx-devel