Reputation: 4384
I'm trying to run node.js backend server. I've received error unexpected reserved word
on import in Node.js file.
The lines in file core.module.js
is:
'use strict';
import lodashMixins from './lodashMixins.js'
... other imports and configurations ...
I launch simple command: node core.module.js
It's not uncommon error, but usually it happens with other libraries. I haven't seen solution for Node.js. How should I fix this? I'm using Windows Server.
Edit: I've find out that it's ES6, but how could I launch it? It looks like backend for the application, but I have no idea what command should I use to launch it without errors.
Upvotes: 59
Views: 114199
Reputation: 59
In my case the problem was that I was using await
inside a forEach block in and AWS Lamba using Javascript
describeSnapshotResponse.Snapshots
.map(currentSanpshot => currentSanpshot.SnapshotId)
.forEach(currentSanpshotId) => {
console.log("About to delete snapshot:", currentSanpshotId);
const deleteSnapshotCommand = new EC2.DeleteSnapshotCommand({
SnapshotId: currentSanpshotId
});
const deleteSnapshotResponse = await ec2Client.send(deleteSnapshotCommand);
console.log("Delete snapshot:", currentSanpshotId);
});
Uaing async modifier on the block did the trick as show in Using async/await with a forEach loop in Yilmaz response
describeSnapshotResponse.Snapshots
.map(currentSanpshot => currentSanpshot.SnapshotId)
.forEach(async (currentSanpshotId) => {
console.log("About to delete snapshot:", currentSanpshotId);
const deleteSnapshotCommand = new EC2.DeleteSnapshotCommand({
SnapshotId: currentSanpshotId
});
const deleteSnapshotResponse = await ec2Client.send(deleteSnapshotCommand);
console.log("Delete snapshot:", currentSanpshotId);
});
Upvotes: -1
Reputation: 4730
This may not be the official answer, but I stumbled here after searching around for the 'unexpected reserved word'. After poking around, I discovered my problem was that, in fact, I just needed to run an npm install
after having updated my branch from origin / rebasing. Hope this helps someone else who is furiously reverting their code trying to figure out what they broke! :)
Upvotes: 0
Reputation: 2367
I ran into this issue as I manually install any of these tools outside of Visual Studio. But Visual Studio ships with multiple open source command line tools that are used in modern web development workflows. Here’s how you can tell Visual Studio to use the same version that you have manually installed
Go to Tools –> Options –> Projects and Solutions –> External Web Tools
or
Upvotes: 2
Reputation: 46351
The import
keyword is part of the modules feature in ECMAScript 2015, along with export
and a few other specifications.
It is currently not implemented natively in NodeJS, even on the lastest version (v0.12.7), nor is it supported in the ES2015 "friendlier" fork iojs.
You will need to use a transpiler to get that to work.
[edit] it's still unsupported in the latest version (v5.8) despite the existence of an --harmony_modules
flag, which does nothing. Your best run is to use babel, as explained here and here
Upvotes: 36
Reputation: 4006
import
is a part of ECMAScript 2015 (ES6) standard
and as Amit
above mentioned it is not currently implemented natively in Nodejs.
So you can use transpiler like babel
to run your es6
script
npm install babel
An example based on this answer
app.js
import {helloworld,printName} from './es6'
helloworld();
printName("John");
es6.js
module.exports = {
helloworld: function() { console.log('hello world!'); },
printName: function(name) { console.log(name); }
}
And using require hook
in start.js
require("babel/register");
var app = require("./app.js");
And start your app as
node start.js
EDIT
The above answer was base on babel v5.8.23
. For babel >= v6
Use require hook
in start.js as
require('babel-core/register');
require("./app.js");
Also, transformations are not enabled by default. So you will need to install a preset
. In this case use es2015
npm install babel-preset-es2015
And use it in a .babelrc
file in root folder
{
"presets": ["es2015"]
}
Upvotes: 54