Cannot Clone the repository and install with npm #510
Comments
|
I have seen that there are some who have had problems with |
|
Thanks for your quick reply Fredrik. BTW I am running OSX Yosemite if that helps. Regards, Ryan Archer
|
|
Hmm. It shouldn't really be necessary to run |
|
@stefanjudis : Is there a possibility that you may have some insight into why I thought maybe you could help, since you helped us to remove global dependencies and introduce postinstall scritps initially. #274 |
|
Can you please provide your node and npm version? There shouldn't be any case to run it with |
|
I've got same issue on Debian. |
|
Then same here - can you please provide node and npm versions and maybe the logfile? |
|
Node v0.12.7 I get this info: Here's log. |
|
But that's a different error. I assume ja what should I say. Working fine here. https://gist.github.com/stefanjudis/c22f0128e62cb5f1946a Can you please confirm that you're got And also that the execution srcipts are included in |
|
node: v4.1.2 Within the node_modules folder within the 'FoundationPress' installed folder I can see the 'grunt' and 'bower' folders. All I can seen in the node_modules/.bin folder is a grunt shortcut. I have attached a screenshot of my dir. |
|
Here's full log for |
|
@bpinet @coolwebs Can you please try the same with the latest npm Honestly I've got no idea what's going on. Everybody running So the problem is not actually the postinstall - but rather that the installation is not working properly. |
|
I've used this commend to update npm Now I have 3.3.6. I got this warning, but it looks like it worked just fine. |
no need for that ( it works though ;) )... when you once have Can you maybe check the 2.4.17 version? So that we can figure out, if they fixed it in one of the fix-releases in |
|
@stefanjudis - are you sure that npm version is right. My most up to date version was v2.14.4. |
|
Fu... Sorry to hear that. :( https://github.com/npm/npm/releases points out that v2.14.7 is the latest stable I assume you can install it over it with this thingy? As I'm responsible for your fuck up - let me know if I can help via skype, hangout or anything. :( Note: i'm jumping between npm version all the time and never had problems with that... |
|
Thanks for following up with me @stefanjudis - lets just say this isn't the first time I've had issues with node. Mucking around with ionic and phonegap CLI forced me to do clean uninstall/reinstall several times. I don't want to get node via the installer again so I completely cleaned out the junk and did it with Homebrew (not before having to repair Homebrew as well!) So yeah now I have node v0.10.28 and npm v3.3.8, so it seems I've done a jump like @bpinet (maybe he used brew as well). So I got much further this time but still ran into errors and still could not successfully run npm build to get the SASS files to write css - good news is that I found a log file this time which I have attached. Scratch that, cannot attach a log file or a txt file in GITHUB, so here is a link to it http://coolwebs.com.au/npm-debug.txt |
|
Ok, so I got tired of doing it on a mac so I have it a go on my work PC which is still running the version of node and npm that i stated earlier. One thing I noticed is that the instructions on the .MD file state to run However, I can't run the I have attached a screenshot from CMD |
|
Man I'm through with trying to compile sass, @olefredrik - do you have a version of FoundationPress that just uses CSS and not SASS? I can reverse engineer it into SASS later and use Compass to do all the compiling/watching. The CLI way keeps telling me that it has issues with Bower and Grunt and keeps blaming your package. I just want to get the theme into a WP installation so I can have a play with it. I'm hoping for a time in the future that browsers will just read SASS files instead of CSS but that's probably quite some time away... |
|
I had hoped that we could find out what was the core of the problem here. I'm not getting any of the errors that you get, so that makes it all a bit more difficult to troubleshoot. This is essentially a starter-theme which is heavily based on a workflow using Sass and Grunt. So if you just want to hack on the CSS, I would recommend that you take a look at JointsWP, which offers a package for both Sass and CSS. Out of curiosity, you can test if you're able to run Sass on JointsWP? |
|
Yes Fredrik, I did come across JointsWP today and i sent Stefan an email asking how much different it was from FoundationPress. I'm not sure what's going on. Makes me feel like doing a complete reset of my macbook and anything i have ever installed through terminal. |
|
I give up. I've switched to 2.5.0 and it didn't work. After going back to 3.3.6 it does not work anymore. Same error every time. |
|
I just found out about FoundationPress and wanted to start using it today. I didn't came any further, as I am still struggling to get it up and running. I have tried upgrading/reinstalling node, using sudo and anything I thought would make some sense, but to no avail. It looks like I'm having the same issue @coolwebs stated earlier. It seems that line 4 of foundation.scss is causing the error, as it is trying to compile the scss using a non-existing reference to I hope this is of any help. OS used is Mac OS X 10.11.1 (El Capitan), node and npm versions are found in log below. And the debug-log from the last line above: |
|
so you're running ? And the initial I assume that you don't have @olefredrik I have still no idea what's going on. :( I'm so sorry about that. I just tried the same setup - node https://gist.github.com/stefanjudis/b957405858aab427aeac |
|
I can not understand what's causing these errors, since it runs smoothly on my machine. OSX El Capitan, Node v.4.1.1, NPM v.2.14.4. Basically, I believe that it is still a good idea to drop global dependencies. But if people experience showstopper errors on installation, it' maybe a relevant question whether we should roll back to global installation of bower. What do you think, @stefanjudis ? |
|
Honestly i'm fine with rolling back - I don't like it though. But the fact that I was not able to reproduce the problem at all ( and I tried really several node&npm combinations ), makes it impossible to debug or solve. :( Also there should be an npm issue filed about it. |
|
@stefanjudis Correct, However, file I'm running the latest version of OS X El Capitan (10.11.1). I just have tried again, and indeed exact the same errors occur when I try to run |
|
I have two macbooks, both running OSX El Capitan. I've installed Node v4.2.1 and npm 2.14.7 on both machines. With a fresh clone of FoundationPress, I experience no issues at all with |
|
@Didel : Is it right that you don't have a components/foundation/ directory in your cloned folder, after |
|
@olefredrik @stefanjudis Weird. This morning I decided to remove the entire FoundationPress folder and start all over again. After a The previous time I cloned the project I got all different kinds of errors, so I did all kinds of things in a desperate try to fix the problem. For example, I updated and upgraded all the npm packages and npm and node itself. I happend to have quite an old version of node (0.12) and apparently lots of things have changed since then, so I installed my current node version. So effectively I first cloned the project and try to install and build it, then updated and upgraded everything, while apparently doing the other way around is the right way to go. Maybe this won't happen to users who have a relatively fresh install of node and/or npm, and only affects users who could have outdated copies of any of the above? Could it help to include update/upgrade instructions in the installation manual? And could it help to require a minimal node-version? I remember to have read somewhere that as of node 3.4 (or 3.2, I don't remember exactly) something has changed which fixes a lot of things... Just dropping my thoughts on the problem, I'm glad I can start working on the theme today 😄 |
|
@Didel : Woho! I'm happy it worked out, finally! It's a good idea to include the required minimal node version in the readme. I removed it from the quickstart because I was not 100% sure which version is required. But I'll run a manual test with nvm and check that. |
|
@coolwebs : Are you still experiencing |
|
A wild guess is that a lot of the weird, hard-to-reproduce problems are cause by old versions of FoundationPress used with the new way of doing things. FoundationPress really isn't upgradeable at all (unless you carefully do it manually) and neither is the workflow, since so much have changed. That could be a problem if you have various FoundationPress-based sites based on different checkouts of the code over the last year(s). It does not help that node, npm, lib-sass etc have had their own compatibility issues as well, on top of everything else. |
|
@olefredrik, In all honesty I have not been playing with it lately. I had a website to build and decided to get up and running with JointsWP and just use CSS overrides agains the core Foundation CSS. From what I can see, Foundation based themes are quite robust and really made me appreciate how commercial themes (like from ThemeForest) can just needlessly way down a Wordpress website with tonnes of features that you never use and a ‘glut’ of code to process on every page load. I will revisit FoundationPress at a later time I hope. Can you tell me in what key ways that it differs from JointsWP?
Ryan Archer | Web Designer & Developer |
|
@coolwebs : 👍 To be honest, I haven't used JointsWP myself. But I guess it's pretty much the same, with a few variations in workflow and build settings (grunt vs gulp etc). They are both built on Foundation 5, so the available components will be the same for both. @Aetles : It is true that is's not necessarily straight forward to upgrade a FoundationPress installation. The idea is to start with the latest version when starting a new project, and take it from there. Have tried to make it easier to see what's new by introducing a changelog and release archive. Earlier versions will always be downloadable under releases. So you're free to choose whether you will jump on the latest version, or use an earlier version. Or use a JointsWP or another theme, for that matter. |
Having issues getting GRUNT to comile the FoundationPress files. I have latest versions of node and npm installed and I was able to clone this GIT repo on my computer but as soon as I try running the "npm install" command on the downloaded directory - I come across heaps of errors that tell me that there is nothing wrong with the npm command but rather an issue with a problem with the foundationpress package. Is there something that I am missing here? Is the package still OK?
Is there any other method of compiling SASS files into CSS?
Thanks
The text was updated successfully, but these errors were encountered: