export keyword is introduced in ecmascript5:

var myFunc1 = function() { console.log('hello'); };   
export.myFunc1 = myFunc1;

If I run above code in firefox console it gives error:

SyntaxError: missing declaration after 'export' keyword  
export.myFunc1 = myFunc1;

I don't understand what I need to declare.

Am I using it in the wrong way?

Any advice would be nice!

export keyword is introduced in ecmascript5:

var myFunc1 = function() { console.log('hello'); };   
export.myFunc1 = myFunc1;

If I run above code in firefox console it gives error:

SyntaxError: missing declaration after 'export' keyword  
export.myFunc1 = myFunc1;

I don't understand what I need to declare.

Am I using it in the wrong way?

Any advice would be nice!

• javascript
• node.js
• ecmascript-5

Share Improve this question Follow edited May 9, 2015 at 14:57 Mast 1,90455 gold badges3333 silver badges4848 bronze badges asked May 9, 2015 at 14:38 vijayvijay 11.1k1212 gold badges6666 silver badges8181 bronze badges 2

• 1 What did you expect that code to do? Where did you learn that the export keyword is used that way? The w3schools page you link to only says that it's reserved in ES5, nothing else. – JJJ Commented May 9, 2015 at 14:43
• 1: i expect to know what that keyword does in javascript and how to use it in any way also kept nodejs exports with s keyword in mind and tried the above code in browser – vijay Commented May 9, 2015 at 15:12

Add a ment  | 

2 Answers 2

Sorted by: Reset to default 5

The syntax for ES6 export looks like this:

//------ lib.js ------
export const sqrt = Math.sqrt;
export function square(x) {
    return x * x;
}
export function diag(x, y) {
    return sqrt(square(x) + square(y));
}

//------ main.js ------
import { square, diag } from 'lib';
console.log(square(11)); // 121
console.log(diag(4, 3)); // 5

Note that this is different from the CommonJS modules.export syntax used in Node.js.

Node js uses exports to expose functionality in modules to their implementers

defined here. https://nodejs/api/modules.html#modules_module_exports

Is this what you're trying to do?