Skip to content

Windows support? #2

@oksas

Description

@oksas

I was a little reluctant to post this because I don't really feel like I can give a lot of info on this, but I just downloaded Astrum on two of my Windows machines (both running 64-bit Windows 7) and while it seemed to install just fine with npm install astrum -g, running astrum init ./public/pattern-library causes the terminal to just hang, for as long as I'll let it, with no sort of errors or anything given. I've tried a few variations of the init command:

  • in an empty directory
  • in an existing project directory
  • with the public/pattern-library folders already made (and empty)
  • without the public/pattern-library folders pre-made
  • with the path specified absolutely (eg astrum init c:\web\astrum-sample)

Actually, all of the astrum commands seem to produce the same result :( Running astrum or just astrum init produces the same hung-terminal effect.

If there are any other details I can provide I would be happy to! I'm not sure if there's some way I can tell Node on my machine to give me some actual error messages? In any event, if there's anything else I can do, I'd be happy to help. If there's something I'm missing and this is a user-error, please let me know D: Astrum looks like an excellent tool and I'm really excited to try it out!

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions