Recently spun up a D7 site with Foundation as a base theme. While setting up a sub theme and Grunt as described in the documentation I ran in to binding errors when attempting to run Grunt as older versions of node-sass and grunt-sass are installed with the provided package.json file. I simply updated the version #s declared for each in the package.json file to the latest version of each and things are running fine.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | update_package_json-2804703-12082736.patch | 1.64 KB | spanners |
Comments
Comment #2
iamrentman commentedComment #3
iamrentman commentedComment #4
spanners commentedFollowing on from this, I found the same thing. And I found it when editing an existing website after I'd updated my Mac's node.js to version 7.x. Node modules were WAY out of date.
I'm to drop in the error message here, in case someone is Googling for a solution.
If you come across this, update your subtheme's package.json file with new dependencies. You can search for the latest versions on http://npm.im
Or if you want to try the working dependencies current at the time of my post, replace lines 5 through 13 of the package.json file of your ZURB Foundation subtheme with...
I can confirm that these work with the D7 Foundation 5 theme - have fixed multiple websites and tried it on a fresh install as well.
NOTE: If you're updating an existing Drupal 7 site with a ZURB Foundation theme, you might find a few issue with deprecated classes and functionality (eg. you can't @extend inside a @media query). Don't panic! Just work your way through the errors (or comment out the offending lines) and keep going until grunt runs correctly.
Comment #5
spanners commentedI've attempted rolling a patch together for updating to the node dependencies zurb_foundation. I pulled down a fresh copy of 7.x-5.0-rc6 and made a diff of the changes to the package.json and STARTER/package.json file.
Note that this is for trying to fix a fresh install of sites/all/theme/zurb_foundation - it won't work on an existing subtheme. I'm pretty new to the whole patch-rolling thing, so hopefully someone can help me create one for an existing subtheme (basically ignoring the "name" entry in the package.json file).
Comment #6
spanners commentedComment #7
hongpong commentedI think this can probably be committed to 7.x-5.x unless someone has an objection. If this is breaking installation it should go in.
Comment #8
kclarkson commentedI just spent a good amount of a day or so trying to figure this out where the errors were coming from when trying to update D7 Zurb Theme after I had updated node and some other stuff. Error's excluding deprecation have gone away thanks to @Spanners #4 suggestion.
Would like to see this added to dev!
Comment #9
apmsooner commentedPatch works.
Comment #11
hongpong commentedThank you Spanners, apmsooner, kclarkson, iamrentman for reporting this issue and testing the fix. Committed!