Why is the extension .mjs ?

[rabol]

I have been using a old version for a very long time as I 'only' use the view functionality and I have not see any issues so for me there have not really been a reason to read, however... npm continue to nag me with a 'security' warning so I decided to try to upgrade from v 3.10.111 to the latest v5.1.91

one major thing I notcied was that now the files are named .mjs

I looked at the github issues and saw that one have to reconfigure the web server - that might not be a trivial task.

Now, my real question is: who has decided that .mjs is a valid mime type ?

if it is a 'common' and defined mine type, then a issue should be created at nginx/apachec/xxxx, to support this type

If this is not a common mimetype, tnen why is it then used as it casues a lot of trouble

I did check here: https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/MIME_types/Common_types

and mjs is not on the list. I did find some infomration saying that mjs. is deprecated, but not 100% sure if that is correct

Thanks

[calixteman]

.mjs is a file extension not a mime type.
Anyway, I check too in MDN (ctrl+F .mjs):

I don't really see what the problem is...
A server can serve whatever file with the extension you want, it's just a matter of configuration.

[rabol]

as it javascript why not keep the extension as .js I don't really see the problem in having it as .js and the change to .mjs causes a lot of issues.

[nicolo-ribaudo]

Because in Node.js (the largest servee-side JS platform) .mjs is needes to mark files as using standard JavaScript modules syntax.

[zlac]

Is there a way to create a .js build instead of .mjs build from the source? I tried changing gulpfile.mjs

{
filename: defines.MINIFIED ? "pdf.min.mjs" : "pdf.mjs",
library: {
type: "module",
},
}

to

{
filename: defines.MINIFIED ? "pdf.min.js" : "pdf.js",
library: {
name: "pdfjsLib",
type: "var",
},
}

and same for pdf.worker.js

I got pdf.js and pdf.worker.js in build folder, but I am getting errors when using this script:

pdf.js:12225 Uncaught SyntaxError: Cannot use 'import.meta' outside a module
Uncaught (in promise) ReferenceError: pdfjsLib is not defined

I see that import is used only in couple of places in pdf.js, maybe this can be fixed to allow users to make js build of pdf.js?

Or we should just switch to .mjs and ignore legacy browsers and servers that don't support .mjs by default?

[nicolo-ribaudo]

Or we should just switch to .mjs and ignore legacy browsers and servers that don't support .mjs by default?

No browser ever looked at the file extension, so the extension is not going to make a difference in browser compatibility.

I got pdf.js and pdf.worker.js in build folder, but I am getting errors when using this script:

That's because even if you rename to .js, you still need to load it as a module (<script type="module">) and not as a script.