aboutsummaryrefslogtreecommitdiff
path: root/files/ru/web/javascript/guide/modules
diff options
context:
space:
mode:
authorMaxim Postautov <54762420+mpstv@users.noreply.github.com>2021-07-15 19:33:00 +0300
committerGitHub <noreply@github.com>2021-07-15 19:33:00 +0300
commit4fbe5a0194ad7a21a5206d61845577f177b25217 (patch)
tree77a75c4b84e287ee208507c5e5c4f9b433fdb590 /files/ru/web/javascript/guide/modules
parent187d4eb1e4784a944d28e22371ea08f39b538b27 (diff)
downloadtranslated-content-4fbe5a0194ad7a21a5206d61845577f177b25217.tar.gz
translated-content-4fbe5a0194ad7a21a5206d61845577f177b25217.tar.bz2
translated-content-4fbe5a0194ad7a21a5206d61845577f177b25217.zip
clean up mozilla wiki links (#1539)
Diffstat (limited to 'files/ru/web/javascript/guide/modules')
-rw-r--r--files/ru/web/javascript/guide/modules/index.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/files/ru/web/javascript/guide/modules/index.html b/files/ru/web/javascript/guide/modules/index.html
index 2c524cb353..41001b32b3 100644
--- a/files/ru/web/javascript/guide/modules/index.html
+++ b/files/ru/web/javascript/guide/modules/index.html
@@ -82,7 +82,7 @@ modules/
<p>However, we decided to keep to using <code>.js</code>, at least for the moment. To get modules to work correctly in a browser, you need to make sure that your server is serving them with a <code>Content-Type</code> header that contains a JavaScript MIME type such as <code>text/javascript</code>. If you don't, you'll get a strict MIME type checking error along the lines of "The server responded with a non-JavaScript MIME type" and the browser won't run your JavaScript. Most servers already set the correct type for <code>.js</code> files, but not yet for <code>.mjs</code> files. Servers that already serve <code>.mjs</code> files correctly include <a href="https://pages.github.com/">GitHub Pages</a> and <code><a href="https://github.com/http-party/http-server#readme">http-server</a></code> for Node.js.</p>
-<p>This is OK if you are using such an environment already, or if you aren't but you know what you are doing and have access (i.e. you can configure your server to set the correct <code><a href="https://wiki.developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Type">Content-Type</a></code> for <code>.mjs</code> files). It could however cause confusion if you don't control the server you are serving files from, or are publishing files for public use, as we are here.</p>
+<p>This is OK if you are using such an environment already, or if you aren't but you know what you are doing and have access (i.e. you can configure your server to set the correct <code><a href="/en-US/docs/Web/HTTP/Headers/Content-Type">Content-Type</a></code> for <code>.mjs</code> files). It could however cause confusion if you don't control the server you are serving files from, or are publishing files for public use, as we are here.</p>
<p>For learning and portability purposes, we decided to keep to <code>.js</code>.</p>