Unexpected token import - first build #400

steveacalabro · 2017-03-28T20:51:24Z

Node version: 6.9.5

npm version: 3.10.10

Operating system: Windows 10

Command line used: Git Bash

Steps to reproduce:

Clone the project
Run npm install
Run npm run setup
Error appears

(function (exports, require, module, __filename, __dirname) { import { chalkSuccess } from './chalkConfig';
                                                              ^^^^^^

SyntaxError: Unexpected token import
    at Object.exports.runInThisContext (vm.js:76:16)
    at Module._compile (module.js:542:28)
    at loader (C:\Users\{project folder}\node_modules\babel-register\lib\node.js:144:5)
    at Object.require.extensions.(anonymous function) [as .js] (C:\Users\{project folder}\node_modules\babel-register\lib\node.js:154:7)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Function.Module.runMain (module.js:604:10)
    at C:\Users\{project folder}\node_modules\babel-cli\lib\_babel-node.js:159:24
    at Object.<anonymous> (C:\Users\{project folder}\node_modules\babel-cli\lib\_babel-node.js:160:7)```

The text was updated successfully, but these errors were encountered:

coryhouse · 2017-03-29T00:02:08Z

Please confirm that .babelrc is in your project root.

…

On Mar 28, 2017 3:51 PM, "Steve Calabro" ***@***.***> wrote: Node version: 6.9.5 npm version: 3.10.10 Operating system: Windows 10 Command line used: Git Bash Steps to reproduce: - Clone the project - Run npm install - Run npm run setup - Error appears (function (exports, require, module, __filename, __dirname) { import { chalkSuccess } from './chalkConfig'; ^^^^^^ SyntaxError: Unexpected token import at Object.exports.runInThisContext (vm.js:76:16) at Module._compile (module.js:542:28) at loader (C:\Users\{project folder}\node_modules\babel-register\lib\node.js:144:5) at Object.require.extensions.(anonymous function) [as .js] (C:\Users\{project folder}\node_modules\babel-register\lib\node.js:154:7) at Module.load (module.js:487:32) at tryModuleLoad (module.js:446:12) at Function.Module._load (module.js:438:3) at Function.Module.runMain (module.js:604:10) at C:\Users\{project folder}\node_modules\babel-cli\lib\_babel-node.js:159:24 at Object.<anonymous> (C:\Users\{project folder}\node_modules\babel-cli\lib\_babel-node.js:160:7)``` ? You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub < #400 >, or mute the thread < https://github.com/notifications/unsubscribe-auth/ABnFpeMP3Dl7DQ4Qo3Lec0ZpP5l1Mnxuks5rqXLOgaJpZM4MsLYA > .

steveacalabro · 2017-03-30T18:15:28Z

I confirmed that the file was there.

I found the reason why in case anyone else comes across this issue. It is specifically a problem with windows machines I believe. I tried the setup on my Ubuntu box and it works fine.

When working with windows you need to have the following installed npm install --save-dev cross-env.

The reason behind this is that the NODE_ENV var on my machine was set to production and I was unable to set it to development without that module. Once installed and the NODE_ENV=development command was run everything worked out ok.

coryhouse · 2017-03-30T18:17:31Z

Great to hear you got it solved Steve! And thanks for sharing your solution. Curious - Why did you have NODE_ENV set to production on your machine?

steveacalabro · 2017-03-30T18:26:00Z

I'm not entirely sure. I have a feeling it was with another project I was doing with React/webpack earlier this week

ICeZer0 · 2017-04-04T12:21:43Z

I am having the same issue. When I use the slingshot locally on my Mac it is fine. Once I upload it to Github I can't "npm start" without getting the error

/Users/ICe/GitHub/React.StocksApp/tools/startMessage.js:1 (function (exports, require, module, __filename, __dirname) { import { chalkSuccess } from './chalkConfig'; ^^^^^^ SyntaxError: Unexpected token import at Object.exports.runInThisContext (vm.js:76:16) at Module._compile (module.js:542:28) at loader (/Users/ICe/GitHub/React.StocksApp/node_modules/babel-cli/node_modules/babel-register/lib/node.js:144:5) at Object.require.extensions.(anonymous function) [as .js] (/Users/ICe/GitHub/React.StocksApp/node_modules/babel-cli/node_modules/babel-register/lib/node.js:154:7) at Module.load (module.js:487:32) at tryModuleLoad (module.js:446:12) at Function.Module._load (module.js:438:3) at Function.Module.runMain (module.js:604:10) at /Users/ICe/GitHub/React.StocksApp/node_modules/babel-cli/lib/_babel-node.js:159:24 at Object.<anonymous> (/Users/ICe/GitHub/React.StocksApp/node_modules/babel-cli/lib/_babel-node.js:160:7)

coryhouse · 2017-04-04T12:41:12Z

@iM-Durant7 When you say "Once I upload it to Github I can't "npm start" without getting the error", how are you running it when up once up on GitHub? Have you confirmed .babelrc is uploaded?

ICeZer0 · 2017-04-04T13:16:01Z

I created a repo in github and copied the files over from my local machine. After npm install, I used "Npm start -s". You can look at my current repo "React.StocksApp" it has the .babel and I ran a console "hello world" to verify that .babel was working.

coryhouse · 2017-04-04T13:40:51Z

@iM-Durant7 Your .babelrc doesn't match Slingshots: https://github.com/coryhouse/react-slingshot/blob/master/.babelrc

I just tried Slingshot's .babelrc on your project and it started fine.

ICeZer0 · 2017-04-05T00:21:59Z

oh wow, ok thanks! I think once I uninstalled the demo project it took my babel away and I was lost ??.

steveacalabro closed this as completed Mar 30, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unexpected token import - first build #400

Unexpected token import - first build #400

steveacalabro commented Mar 28, 2017

coryhouse commented Mar 29, 2017 via email

steveacalabro commented Mar 30, 2017

coryhouse commented Mar 30, 2017

steveacalabro commented Mar 30, 2017

ICeZer0 commented Apr 4, 2017

coryhouse commented Apr 4, 2017

ICeZer0 commented Apr 4, 2017

coryhouse commented Apr 4, 2017

ICeZer0 commented Apr 5, 2017 •

edited

Unexpected token import - first build #400

Unexpected token import - first build #400

Comments

steveacalabro commented Mar 28, 2017

coryhouse commented Mar 29, 2017 via email

steveacalabro commented Mar 30, 2017

coryhouse commented Mar 30, 2017

steveacalabro commented Mar 30, 2017

ICeZer0 commented Apr 4, 2017

coryhouse commented Apr 4, 2017

ICeZer0 commented Apr 4, 2017

coryhouse commented Apr 4, 2017

ICeZer0 commented Apr 5, 2017 • edited

ICeZer0 commented Apr 5, 2017 •

edited