I've been updating Foundation Sites for new projects as I create them. As such, I have a number of projects of different ages, all the way back to v4.x.
I'm currently trying to recompile sass on a v6.2.1 project using the latest Foundation CLI (v2.2.3 (I believe)), and it's failing.
I have run 'foundation update' in the project folder, which changed it to v6.2.4. This surprised me - why not 6.4.x - but perhaps it's smart enough to only update to the latest maintenance release.
With 6.2.1 and 6.2.4 I receive "Error: The `libsass` binding was not found in..." errors when I run 'foundation build' from the project folder. The sub of the error states "This usually happens because your node version has changed", so I changed the version of npm I'm running (using nvm), with the same error.
I honestly don't recall if I used Foundation CLI to install the project in question. I may have done it manually. For example, when I was developing it, I'd use 'npm run build', which is different than the current Foundation CLI build command - 'foundation build'.
I'm kinda stuck and have no idea how I'm supposed to keep up with current versions of Foundation Sites and Foundation CLI while allowing older sites to use older versions. For example, updating my v6.2.x site to 6.4.x could/will have drastic implications on the codebase.
How is the community managing older codebases? Are you updating every project codebase every time you update Foundation Sites and/or Foundation CLI?
Is Foundation CLI compatibile with older versions of Foundation Sites?
Can Foundation CLI be unistalled and older versions of it installed to work with older versions of Sites?
Thanks very much,