Menu
I've been experimenting with new native ECMAScript module support that has recently been added to browsers. It's pleasant to finally be able import scripts directly and cleanly from JavaScript.
/example.html 🔍 <script type="module"> import {example} from '/example.js'; example(); </script> /example.js export function example() { document.body.appendChild(document.createTextNode("hello")); }; However, this only allows me to import modules that are defined by separate external JavaScript files. I usually prefer to inline some scripts used for the initial rendering, so their requests don't block the rest of the page. With a traditional informally-structured library, that might look like this:
/inline-traditional.html 🔍 <body> <script> var example = {}; example.example = function() { document.body.appendChild(document.createTextNode("hello")); }; </script> <script> example.example(); </script> However, naively inlining modules files obviously won't work, since it would remove the filename used to identify the module to other modules. HTTP/2 server push may be the canonical way to handle this situation, but it's still not an option in all environments.
Is it possible to perform an equivalent transformation with ECMAScript modules?
Is there any way for a <script type="module"> to import a module exported by another in the same document?
I imagine this could work by allowing the script to specify a file path, and behave as though it had already been downloaded or pushed from the path.
/inline-name.html 🔍 <script type="module" name="/example.js"> export function example() { document.body.appendChild(document.createTextNode("hello")); }; </script> <script type="module"> import {example} from '/example.js'; example(); </script> Or maybe by an entirely different reference scheme, such as is used for local SVG references:
/inline-id.html 🔍 <script type="module" id="example"> export function example() { document.body.appendChild(document.createTextNode("hello")); }; </script> <script type="module"> import {example} from '#example'; example(); </script> But neither of these hypotheticals actually work, and I haven't seen an alternative which does.
817
ECMAScript modules are the official standard format to package JavaScript code for reuse. Modules are defined using a variety of import and export statements.
Inline JavaScript can be achieved by using Script tag inside the body of the HTML, and instead of specifying the source(src=”…”) of the JavaScript file in the Script tag, we have to write all the JavaScript code inside the Script tag.
When a script tag is used in the HTML file, it is called inlining. This means no external JS file is used instead javascript is put into an HTML file. Modern code has moved from manual coding and customized structures to templates that provide a framework for effective code creation processes.
import from '#id' Exports/imports between inline scripts aren't natively supported, but it was a fun exercise to hack together an implementation for my documents. Code-golfed down to a small block, I use it like this:
<script type="module" data-info="https://stackoverflow.com/a/43834063">let l,e,t ='script',p=/(from\s+|import\s+)['"](#[\w\-]+)['"]/g,x='textContent',d=document, s,o;for(o of d.querySelectorAll(t+'[type=inline-module]'))l=d.createElement(t),o .id?l.id=o.id:0,l.type='module',l[x]=o[x].replace(p,(u,a,z)=>(e=d.querySelector( t+z+'[type=module][src]'))?a+`/* ${z} */'${e.src}'`:u),l.src=URL.createObjectURL (new Blob([l[x]],{type:'application/java'+t})),o.replaceWith(l)//inline</script> <script type="inline-module" id="utils"> let n = 1; export const log = message => { const output = document.createElement('pre'); output.textContent = `[${n++}] ${message}`; document.body.appendChild(output); }; </script> <script type="inline-module" id="dogs"> import {log} from '#utils'; log("Exporting dog names."); export const names = ["Kayla", "Bentley", "Gilligan"]; </script> <script type="inline-module"> import {log} from '#utils'; import {names as dogNames} from '#dogs'; log(`Imported dog names: ${dogNames.join(", ")}.`); </script>Instead of <script type="module">, we need to define our script elements using a custom type like <script type="inline-module">. This prevents the browser from trying to execute their contents itself, leaving them for us to handle. The script (full version below) finds all inline-module script elements in the document, and transforms them into regular script module elements with the behaviour we want.
Inline scripts can't be directly imported from each other, so we need to give the scripts importable URLs. We generate a blob: URL for each of them, containing their code, and set the src attribute to run from that URL instead of running inline. The blob: URLs acts like normal URLs from the server, so they can be imported from other modules. Each time we see a subsequent inline-module trying to import from '#example', where example is the ID of a inline-module we've transformed, we modify that import to import from the blob: URL instead. This maintains the one-time execution and reference deduplication that modules are supposed to have.
<script type="module" id="dogs" src="blob:https://example.com/9dc17f20-04ab-44cd-906e"> import {log} from /* #utils */ 'blob:https://example.com/88fd6f1e-fdf4-4920-9a3b'; log("Exporting dog names."); export const names = ["Kayla", "Bentley", "Gilligan"]; </script> The execution of module script elements is always deferred until after the document is parsed, so we don't need to worry about trying to support the way that traditional script elements can modify the document while it's still being parsed.
export {}; for (const original of document.querySelectorAll('script[type=inline-module]')) { const replacement = document.createElement('script'); // Preserve the ID so the element can be selected for import. if (original.id) { replacement.id = original.id; } replacement.type = 'module'; const transformedSource = original.textContent.replace( // Find anything that looks like an import from '#some-id'. /(from\s+|import\s+)['"](#[\w\-]+)['"]/g, (unmodified, action, selector) => { // If we can find a suitable script with that id... const refEl = document.querySelector('script[type=module][src]' + selector); return refEl ? // ..then update the import to use that script's src URL instead. `${action}/* ${selector} */ '${refEl.src}'` : unmodified; }); // Include the updated code in the src attribute as a blob URL that can be re-imported. replacement.src = URL.createObjectURL( new Blob([transformedSource], {type: 'application/javascript'})); // Insert the updated code inline, for debugging (it will be ignored). replacement.textContent = transformedSource; original.replaceWith(replacement); } Warnings: this simple implementation doesn't handle script elements added after the initial document has been parsed, or allow script elements to import from other script elements that occur after them in the document. If you have both module and inline-module script elements in a document, their relative execution order may not be correct. The source code transformation is performed using a crude regex that won't handle some edge cases such as periods in IDs.
113
This is possible with service workers.
Since a service worker should be installed before it will be able to process a page, this requires to have a separate page to initialize a worker to avoid chicken/egg problem - or a page can reloaded when a worker is ready.
Here's a demo that is supposed to be workable in modern browsers that support native ES modules and async..await (namely Chrome):
index.html
<html> <head> <script> (async () => { try { const swInstalled = await navigator.serviceWorker.getRegistration('./'); await navigator.serviceWorker.register('sw.js', { scope: './' }) if (!swInstalled) { location.reload(); } } catch (err) { console.error('Worker not registered', err); } })(); </script> </head> <body> World, <script type="module" data-name="./example.js"> export function example() { document.body.appendChild(document.createTextNode("hello")); }; </script> <script type="module"> import {example} from './example.js'; example(); </script> </body> </html> sw.js
self.addEventListener('fetch', e => { // parsed pages if (/^https:\/\/run.plnkr.co\/\w+\/$/.test(e.request.url)) { e.respondWith(parseResponse(e.request)); // module files } else if (cachedModules.has(e.request.url)) { const moduleBody = cachedModules.get(e.request.url); const response = new Response(moduleBody, { headers: new Headers({ 'Content-Type' : 'text/javascript' }) } ); e.respondWith(response); } else { e.respondWith(fetch(e.request)); } }); const cachedModules = new Map(); async function parseResponse(request) { const response = await fetch(request); if (!response.body) return response; const html = await response.text(); // HTML response can be modified further const moduleRegex = /<script type="module" data-name="([\w./]+)">([\s\S]*?)<\/script>/; const moduleScripts = html.match(new RegExp(moduleRegex.source, 'g')) .map(moduleScript => moduleScript.match(moduleRegex)); for (const [, moduleName, moduleBody] of moduleScripts) { const moduleUrl = new URL(moduleName, request.url).href; cachedModules.set(moduleUrl, moduleBody); } const parsedResponse = new Response(html, response); return parsedResponse; } Script bodies are being cached (native Cache can be used as well) and returned for respective module requests.
The approach is inferior to the application built and chunked with bundling tool like Webpack or Rollup in terms of performance, flexibility, solidity and browser support - especially if blocking concurrent requests are the primary concern.
Inline scripts increase bandwidth usage. This is naturally avoided when scripts are loaded once and cached by the browser.
Inline scripts aren't modular and contradict the concept of ECMAScript modules (unless they are generated from real modules by server-side template).
Service worker initialization should be performed on a separate page to avoid unnecessary requests.
The solution is limited to a single page and doesn't take <base> into account.
A regular expression is used for demonstration purposes only. When used like in the example above it enables the execution of arbitrary JavaScript code that is available on the page. A proven library like parse5 should be used instead (it will result in performance overhead, and still, there may be security concerns). Never use regular expressions to parse the DOM.
20
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
