Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't run on windows 8.1 #21

Closed
doodledood opened this issue Apr 16, 2015 · 15 comments · Fixed by #24
Closed

Can't run on windows 8.1 #21

doodledood opened this issue Apr 16, 2015 · 15 comments · Fixed by #24
Assignees

Comments

@doodledood
Copy link
Contributor

When I try to run 'npm run dev' I get the following error:
'DEBUG' is not recognized as an internal or external command

@doodledood doodledood changed the title Can Can't run on windows 8.1 Apr 16, 2015
@iam4x
Copy link
Owner

iam4x commented Apr 16, 2015

It seems to be windows specific https://github.com/visionmedia/debug#windows-note

For now as workaround you can change your package.json at script key, the dev one, and remove DEBUG=.... at the beginning.

I'll will install a windows VM tomorrow (1am here), can you link me some tools how to have a CLI / NPM and git on windows to debug this issue?

Thank's!

@iam4x iam4x added the bug label Apr 16, 2015
@iam4x iam4x added this to the 0.3.0 milestone Apr 16, 2015
@iam4x iam4x self-assigned this Apr 16, 2015
@doodledood
Copy link
Contributor Author

Sure, first of all download and install:

Npm should come with the latest release of node.
From there open "cmd.exe" and proceed normally.

Thanks for your efforts.

@doodledood
Copy link
Contributor Author

By the way,
'npm install' also fails when trying to build webpack-dev-server.
There is a some issue with it on windows.
This solves it

I tried removing 'DEV' from package.json but I still can't get rid of
'Error: libsass bindings not found. Try reinstalling node-sass?'
even tough I followed the advice outlined in README.md

@iam4x
Copy link
Owner

iam4x commented Apr 17, 2015

For node-sass I had to do:

  • Install python27, add python to your env path (http://stackoverflow.com/a/6318188)
  • Install VS Express 2013 for building with node-gyp
  • $ npm cache clear
  • $ npm install node-sass

And then $ npm run build worked.

@doodledood
Copy link
Contributor Author

Did you manage to run everything on windows?

@iam4x
Copy link
Owner

iam4x commented Apr 17, 2015

There's an issue with koa-proxy for loading assets on dev I need to check that.

But NODE_ENV=production node server/index.js after npm run build is working correctly

@iam4x
Copy link
Owner

iam4x commented Apr 17, 2015

Everything is good after removing a rule of jscs about the end line and removing DEBUG=dev,koa at the beginning of the command line for launching the npm run dev

I will change validation of end line with https://help.github.com/articles/dealing-with-line-endings/#re-normalizing-a-repository

screen shot 2015-04-17 at 18 55 11 2

@iam4x
Copy link
Owner

iam4x commented Apr 17, 2015

Just noticed it's windows 7, I don't know if it changes a lot for iojs to run on windows 8

@iam4x iam4x mentioned this issue Apr 17, 2015
@doodledood
Copy link
Contributor Author

Okay, I checked out the branch and weird stuff are happening:

  • With iojs (v0.17.1) I still get 'libsass bindings not found. Try reinstalling node-sass?', no matter what I try.
  • With node (v0.12.2) I get 'SyntaxError: Unexpected token ILLEGAL' - which I suspect has something to do with jscs and babel...

@iam4x
Copy link
Owner

iam4x commented Apr 17, 2015

Can you npm install node-sass? Without errors?

And no it won't work with 0.12

@doodledood
Copy link
Contributor Author

Yes I can.
But the problem is that 'npm run build' returns some errors of 'Module didn't self register' for node-sass anyways and babel-core.
I have tried to clone the repo to another folder, removing node and iojs completely and reinstalling iojs, removing npm cache and installing updated dependecies but non seem to work ><

@iam4x
Copy link
Owner

iam4x commented Apr 17, 2015

Okey let me download windows 8!

@doodledood
Copy link
Contributor Author

@iam4x let me know if it works as if it does, it might be that my system is polluted somehow...

@iam4x
Copy link
Owner

iam4x commented Apr 17, 2015

No luck with windows 8.1 :( Same issue... You should report issue into babel and node-sass.

@iam4x iam4x removed this from the 0.3.0 milestone Apr 17, 2015
@iam4x iam4x added the wontfix label Apr 17, 2015
@doodledood
Copy link
Contributor Author

sass/node-sass#870

@iam4x iam4x closed this as completed in #24 Apr 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants