Not with the import statement. import and export are defined in such a way that they are statically analyzable, so they cannot depend on runtime information. You are looking for the loader API (polyfill), but I’m a bit unclear about the status of the specification: System.import(‘./utils/’ + variableName).then(function(m) { console.log(m); });
defaultMember already is an alias – it doesn’t need to be the name of the exported function/thing. Just do import alias from ‘my-module’; Alternatively you can do import {default as alias} from ‘my-module’; but that’s rather esoteric.
TL;DR: It does not matter. import * as … from ‘ramda’; import { … } from ‘ramda’; will both by default always bring in the complete Ramda module with all its dependencies. All code inside the module would be run, and which syntax was used to reference the exported bindings doesn’t matter. Whether you use … Read more
Hacking Together Our Own 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”> … Read more
In ES6, imports are live read-only views on exported-values. As a result, when you do import a from “somemodule”;, you cannot assign to a no matter how you declare a in the module. However, since imported variables are live views, they do change according to the “raw” exported variable in exports. Consider the following code … Read more
Each module has its own scope. They are not sharing the global scope like “normal” scripts do. That means hello is only accessible inside the main.js module/file itself. If you explicitly want to create a global variable, you can achieve that by creating a property on the global object, window: function hello() { console.log(mod()); } … Read more
2018 Update: The module loader spec is now a part of the ES Spec – what you are describing is allowed and possible with <script type=”module”> in browsers and with a custom –loader with Node.js as well as with Deno if you’re into that. The module loader spec and the import/export syntax are separate. So … Read more
Many modern browsers now support ES6 modules. As long as you import your scripts (including the entrypoint to your application) using <script type=”module” src=”https://stackoverflow.com/questions/41722621/…”> it will work. Take a look at caniuse.com for more details: https://caniuse.com/#feat=es6-module
import {Link} from ‘react-router’; imports a named export from react-router, i.e. something like export const Link = 42; import Router from ‘react-router’; const {Link} = Router; pulls out the property Link from the default export, assuming it is an object, e.g. export default { Link: 42 }; (the default export is actually nothing but a … Read more
The extension is part of the filename. You have to put it in. As proof of this, please try the following: rename file to drawImage.test edit index.js to contain ‘./drawImage.test’ Reload, and you’ll see the extension js or test will be completely arbitrary, as long as you specify it in the export. Obviously, after the … Read more