Node-sass: Issue running on Windows

Created on 28 Apr 2017  路  7Comments  路  Source: sass/node-sass

Installed node-sass globally and get an error while running. Details further below.

OS: Windows 8
Node Version: 7.9.0

Console Output:

位 node-sass --include-path scss assets/scss/main.scss assets/css/main.css
C:\Users\dean\AppData\Roaming\npm\node_modules\node-sass\node_modules\scss-tokenizer\lib\entry.js:1
(function (exports, require, module, __filename, __dirname) { import Input from './input';
                                                              ^^^^^^
SyntaxError: Unexpected token import
    at createScript (vm.js:53:10)
    at Object.runInThisContext (vm.js:95:10)
    at Module._compile (module.js:543:28)
    at Module._extensions..js (module.js:580:10)
    at Object.require.extensions.(anonymous function) [as .js] (C:\Users\dean\AppData\Roaming\npm\node_modules\node-sass\node_modules\babel-core\lib\api\register\node.js:214:7)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)

Most helpful comment

Thanks all for the reports. I've unpublished [email protected] until I can look into it. Clear your node_modules and npm install to pull down the previous working version.

All 7 comments

I have the same issue and it's driving me nuts!
Somehow this appeared today, everything worked fine yesterday. Now I can't build my sass files.

@HitomiTenshi Exactly the same for me. Haven't had that yesterday and now it's like 馃帀 .

Yes, I have the same.
sass-graph just published a new version 2.2.0 (23 hours ago) which contains a new dependency: scss-tokenizer.

I created a issue on the other github: https://github.com/xzyfer/sass-graph/issues/76

Maybe node-sass should keep the dependency of sass-graph to 2.1.2. So ~2.1.2 instead of ^2.1.2

@floviolleau Thanks. Thought that there's some 3rd or 4th part involved in this issue. Gonna take an old yarn.lock file of another project. Thank god we have yarn nowadays.

I use npm :(

Thanks all for the reports. I've unpublished [email protected] until I can look into it. Clear your node_modules and npm install to pull down the previous working version.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

nagyfej picture nagyfej  路  3Comments

YepFury picture YepFury  路  4Comments

bgolubovic picture bgolubovic  路  3Comments

pulkitnandan picture pulkitnandan  路  4Comments

cjo2118 picture cjo2118  路  3Comments