First, install the latest version of Node.js. It has the latest and greatest features. Second, add the “type”: “module” line in your package.json file. { “type”: “module” } Third, use the –experimental-modules flag when invoking nodejs: node –experimental-modules app.js You should be good to go! An alternative is to avoid adding the “type”: “module” line … Read more
From Node.js version 17.5.0 onward, importing a JSON file is possible using Import Assertions: import packageFile from “../../package.json” assert { type: “json” }; const { name, version } = packageFile; assert { type: “json” } is mandatory Destructuring such as { name, version } is not possible in the import declaration directly The contents of … Read more
For people trying to import path in a TypeScript file, and ending up here: Be sure to have node types installed: npm install –save-dev @types/node Import path symbol: import * as path from ‘path’; Note: @types/* are automatically included for compilation, providing you use typescript version 2.0 or above, and provided you don’t override the … Read more
Yes, it does, exactly one time. See http://www.ecma-international.org/ecma-262/6.0/#sec-abstract-module-records: Do nothing if this module has already been evaluated. Otherwise, transitively evaluate all module dependences of this module and then evaluate this module
Actually the error you got was because you need to explicitly state that you’re loading a module – only then the use of modules is allowed: <script src=”https://stackoverflow.com/questions/37624819/t1.js” type=”module”></script> I found it in this document about using ES6 import in browser. Recommended reading. Fully supported in those browser versions (and later; full list on caniuse.com): … Read more
For default exports you should use: import * as fs from ‘fs’; Or in case the module has named exports: import {fs} from ‘fs’; Example: //module1.js export function function1() { console.log(‘f1’) } export function function2() { console.log(‘f2’) } export default function1; And then: import defaultExport, { function1, function2 } from ‘./module1’ defaultExport(); // This calls function1 … Read more
import React, { Component, PropTypes } from ‘react’; This says: Import the default export from ‘react’ under the name React and import the named exports Component and PropTypes under the same names. This combines the two common syntaxes which you’ve probably seen import React from ‘react’; import { Component, PropTypes } from ‘react’; The first … Read more
If you use proposal-export-default-from Babel plugin (which is a part of stage-1 preset), you’ll be able to re-export default using the following code: export default from “./App.js” For more information see the ECMAScript proposal. Another way (without this plugin) is: export { default as App } from “./App.js” The above is a very common practice … Read more
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); });
There is no way to do this with a single import statement, it does not allow for invocations. So you wouldn’t call it directly, but you can basically do just the same what commonjs does with default exports: // module.js export default function(options) { return { // actual module } } // main.js import m … Read more