SCSS Not Compiling Because #676
Comments
|
Not sure if this helps, but I'm getting the following depreciation errors when I'm running "npm install": And a little later: |
|
I'm having the same problem, you're not on OS X are you by any chance. Interestingly I was able to install JointWP which is another foundation6 wordpress template |
|
@nitrokevin I am on OSX, I also don't have any trouble compiling straight Foundation 6, I haven't tried JointWP, in looking at the Docs, it seemed like I'd need to do quite a bit more work to get the customization I can get out of the box with FoundationPress. I went through and tried to update all the packages that it said were depreciated, but they were up-to-date, so I'm guessing the depreciated packages are in FoundationPress. I know just enough about NPM to be dangerous, so I could very well be doing something wrong... |
|
I think you are right, I was able to install an earlier version of foundationpress 6 a few weeks ago but then after downloading the version that had the fix for off canvas it no longer installed |
|
So, I've deleted and reinstalled several times, and I've noticed that I'm now not getting any of the bower_components generated when I run the build command. Again, I may be doing something wrong here, I just don't know where to start. |
|
I've tried commenting out the: font-awesome line in foundations.scss, and it breaks at the next import line which is for motion-ui. It's seeming to not be able to find any of the installed packages. CodeKit is saying that both font-awesome and motion-ui are installed, and I've found both of their folders and contents in assets/components. I continued to comment out the motion-ui import line, just to see if I could clear the error and work backwards, but it errored at the motion-ui additional includes, so I commented those out and I get this error: It's looking like it can't find any of the installed packages, so no matter what I comment out, it won't work. Any and all help would be appreciated. |
|
What steps did you take after cloning the repo? Did you run npm install? If so, did it automatically run |
|
@colin-marshall Thanks for replying, I'm following the Quickstart Guide on this GitHub repo, these are the exact commands I'm executing: I assume it ran the |
|
You can look in the in the log to see if it successfully runs |
|
@colin-marshall you're correct, it does indeed run, but it looks like it didn't create the bower_components folder. I ran |
|
In FoundationPress, |
|
@colin-marshall that's what I was thinking, but it looks like FoundationPress can't find them. They are installed correctly according to my compiler, but they aren't being found during the import. |
|
@indadam how is FoundationPress not finding them when your build task completes successfully according to your log you just posted? |
|
@colin-marshall no idea, that's why I posted the issue. Here's the compiling error I get when I try to compile the SCSS for the clone I posted above: |
|
How are you compiling the SCSS? The log clearly shows the SCSS gets successfully compiled after a |
|
@colin-marshall I'm using CodeKit (https://incident57.com/codekit/) |
|
There is your issue. The Gulp build system includes the proper import paths. If you just run |
|
@colin-marshall I guess I'm confused, is the current version of FoundationPress different than both Foundation 6 Sites and the previous version of FoundationPress? I've been using CodeKit for it and several other projects. It handles several compilings in addition to SCSS that I'd prefer not to lose. |
|
When FoundationPress switched to Gulp, the Sass import paths are set here: So unless there's a way to add those import paths in CodeKit, you're going to need to change all the imports in the SCSS to use the full path. For example: There is really no reason to use CodeKit though, since the FP build process with Gulp does everything CodeKit does, and possibly more. |
|
@colin-marshall ok, thanks for the help. |
|
I'm not using code kit myself I use npm watch, but after I run npm install npm build, when I go to the site it looks like no css is loaded, earlier builds of foundation press 6 worked fine |
|
Do you get errors in the console? Can you please be more specific about what you mean by "no css is loaded?" Do you mean the foundation.css file is empty? |
|
Is your node up to date? I had a similar problem, I downloaded the latest node, installed, and then it worked. |
|
I've tried again and now I'm getting this: [23:14:28] Using gulpfile /Volumes/Server Services Data/Library/Server/Web/Data/Sites/web.artisan-creative.co.uk/foundation6/wp-content/themes/FoundationPress/gulpfile.js
[23:14:29] Finished 'javascript' after 417 ms |
|
@nitrokevin does the |
|
Hi colin, no I don't have assets/components/foundation-sites /usr/local/lib/node_modules/bower/node_modules/mkdirp/index.js:89 |
|
Fix npm permissions: https://docs.npmjs.com/getting-started/fixing-npm-permissions Then |
|
I followed option 2 to fix the permissions but its still not working for me |
|
Ok I tried on a different Mac and it worked fine, I guess I need to uninstall npm and node and try fresh, thanks for your time |
|
No problem, I would recommend installing node/npm with homebrew. I stopped running into problems like the ones you are having when I did that. |
|
Hey colin, can I just as your advice relating to this. I have installed node on 2 other macs using home-brew as suggested and all works properly. So I removed node (and npm) from the mac I was having problems with and re-installed with home-brew, looked like it installed correctly, but when I try and npm run watch from this mac I get errors, no errors from the others. the error is [16:40:17] Starting 'copy'... Error: EPERM: operation not permitted, chmod '/Volumes/Server Services Data/Library/Server/Web/Data/Sites/web.artisan-creative.co.uk/cummins/wp-content/themes/FoundationPress/assets/javascript/vendor/motion-ui/README.md' npm ERR! Darwin 15.0.0 But I don't think it is a permission problem else it wouldn't work from the other computers? |
I think it's actually the opposite, a permissions problem would make sense why it would not work on one computer and would work on others, because permissions can differ between different computers. Did you use |
|
No I didn't use sudo, I installed foundationpress on our server and I am able to npm run watch from 2 computers to this same folder and it works, but when I try and do the same actually on the server it fails. Your reply gave me the idea of sudo npm run watch from the server, and it worked! So yeah you are right! It is permissions |
|
Nice! If I'm understanding your setup correctly, it might be because you used a different user account when you installed it to the server from the other computers, and that user account is different than what you are using when you are actually on the server? Thus the permissions are different and |
|
Just worth adding my five pence/cense. Updating your node (if you're a mac user) helped me.
|
|
I've had similar issues getting it to work with terminal, fixed by changing some paths. I noticed installing bower creates a folder called bower_components, yet the paths to these in gulpfile.js are Are these problems related to OSX El Capitan/bower or something? I'm new to GitHub/scss/bower and suspect I may be doing something wrong to have had these errors in the first place as the FoundationPress master files still seem to have what appear to be the wrong paths to me... I'm sure they're not though as surely they'd have been updated. Any help is most appreciated! Thanks! |
I'm getting the following compiling error when I try compiling the SCSS:
Font Awesome is correctly installed and looks great. I've re-cloned the theme, but it doesn't seem to make a difference.
Thoughts?
The text was updated successfully, but these errors were encountered: