Add your Codekit website folders to privacy in spotlight settings, and then remove them again.Check your drive for permissions issues, and then repair them if present (disk utility for Mac).Reboot computer (this wouldn’t be a techie how-to guide without this point, would it?).Some things I tried, that didn’t work (but may work for you?): not having to manually poll for changes in terminal). This is one of my favourite features of Compass, and I love the simplicity that CodeKit adds to the feature (i.e. I tried absolutely everything, and simply could not get it to work after hours of debugging. If you want to use gems/plugins with Codekit, you need to use your local version.After purchasing and upgrading from CodeKit 1 to CodeKit 2, I noticed that my SCSS files were not automatically compiling upon file change. Sorry if this is a bit long-winded but hey – it worked for me. I’m not sure whether the developer knows about this bug, but it’s been like that since I started using the app a few versions ago.
After you’ve done that and made your project then you can go change it back and use your local version. **Be aware though**, if you have Codekit pointing to _your_ version of Compass rather than it’s internal one, and you’d like to create a new Compass project using the app you **must** go into the preferences and tell it to use it’s internal compiler **then** create your project, otherwise the app will just make an alert noise without actually telling you what went wrong and your project wont get created, which is pretty shitty. Bourbon handles all of these and a shit load others perfectly and is included with the latest version of Codekit. While Compass is awesome, it’s not too great if you want to use things like **animation**, **user-select** or **HIDPI media queries**. Which is useful if you want to use the new animation mixins in that version of Compass, and you can switch between this and the internal compiler as you like.Īlternatively, I would _highly_ recommend using ( ) – it’s a Sass mixin library. I’d suggest having the latest pre-release version of Compass installed on your machine with: Codekit uses the latest stable release of whatever it is you’re using, in this case Compass. That worked for me – telling Codekit to drop it’s internal stuff and use yours. Only mentioning those because I use them a lot :) You can check which versions of things Codekit is using by opening the **About Codekit** window from the toolbar.ĭoing this also gives it access to any other gems/plugins you may have installed that you might wanna use with Compass as a like the ( ) or the Compass port of ( ).
I don’t think you need to restart the app after doing this but I do it anyway just to make sure.
You can see in the shit in that error you provided, that it couldn’t find the gem you want and it’s looking for it _inside_ the application itself – obviously it ain’t going to find it because it ain’t there.Īnyway, I fixed the issue you seem to have by going into the Codekit preferences (I’m using **version 1.3.5**), into the **Languages** tab, then selecting **Compass** and under the **Advanced Compiler Settings** I told it to use the Compass gem I have installed on my machine by navigating to it after hitting the **Use the Compass executable at this path:** option, rather than using the internal one.
COMPASS CODEKIT INSTALL
You don’t have to go into the command line and install Compass, Sass, LESS or _anything_ to start using Codekit, it brings it’s own to the party. If you’ve googled enough or seen a few questions on Stack Overflow, you’ve probably read that Codekit uses it’s internal version of whatever pre-processor you’re using, and doesn’t have any relationships with the gems installed on your machine. Not sure if you’ve resolved this yourself by now, but I had this same problem (and a few others with gems on my Mac) and I managed to fix it pretty easily.
0 kommentar(er)
