Hi RobertT, I already tried using the sudo command in case it was due to permissions but the same error appears unfortunately. My node is currently set to 6.10.0 - does it need to be 4.x for this to work?
jaread83 I'd recommend NodeJS 4.x which is what I use, I've seen some odd quirks with 6.x so I'm not sure that's fully supported yet.
Generally I will keep all my code bases in a seperate partition of the HDD - I got around 20 repos that I work on so it makes sense to do this.
As an experiment, I just tried creating the lithium project in my home directory. That seemed to work! So that means the lithium SDK repo needs fixing up as it doesn't seem to like it when I create a project on a seperate drive.
Hi RobertT, thanks for your help so far. I managed to create the project in my home directory and am now playing about with it.
Trying to get my SASS compiler to work but my browser is blocking the localhost CSS being displayed. Something about mixed content so I suspect this is an issue with the localhost being served under http and the staging site being served under https. When trying to serve my localhost CSS with https it fails to load the file entirely.
How did you get around this?
This one is a pain, it either requires you to build a HTTPS service on your machine which points to the directory that the SASS is compiled from or you need to adjust browser settings to add an exception to allow mixed content.
We're not using HTTPS on our staging environment at the moment but I have played around with running a HTTPS server from my machine for testing, this is one of the areas that Lithium will need to address as more and more communities switch over to HTTPS default traffic.
For Chrome the following should work in terminal to allow mixed-content mode:
open /Applications/Google\ Chrome.app --args --allow-running-insecure-content
