It seems to not work as expected with the mismatch in rubyversions (your gemfile is lower in version). Grunt seems to be running but i get this (and I see no changes after flushing all caches). I have to use grunt -force (advice from grunt). I did all the installs of composer, bundler, Node js, NPM and grunt. I am on the latest 8 dev version of your theme and trying out to make changes in the UIkit.
I have this running right now and it's significantly faster, so I think this is well worth the change, even if life is a little harder because including Compass is not so strait forward.īackwards compatibility: No changes required, this only affects new sub-themes. After many iterations and setups i've resorted to a Gruntfile that will work for everyone, launch the Express Webserver with Livereload using Grunt or launch it the from command line. Adding LiveReload to the mix is even more tedious.
#LIVERELOAD GRUNT INSTALL#
I have tried with the compass-importer and the existing compass-mixins packages on Github, however they are woefully out of date with mixins missing or simply not done correctly = unusable in a real production.įrom a themer perspective there is just one change - instead of running "bundle install" you run "bower install" (bower is easy to install, npm install -g bower"). Launching a NodeJS webserver using express from Grunt has been an elusive topic for some time. I will most likely add this to Github and add it to bower.json etc. I still have to decide what to do about compass, locally I am running a bespoke version of compass-mixins (my own based on compass alpha19). make the necessary changes to partials, mainly paths.make the necessary changes to our Gruntfile.js file, especially for the new globbing for layout forms.
Add grunt packages: grunt-sass, grunt-sass-globbing.Remove grunt packages: grunt-contrib-compass.Even cooler, when you change a CSS file or an image, the browser is updated instantly without reloading the page. As soon as you save a file, it is preprocessed as needed, and the browser is refreshed. Removing the Gem file, no long rely on Ruby + the gems (ruby, sass-globbing, sass, susy, modular scale etc). What does LiveReload do LiveReload monitors changes in the file system.Ruby SASS + Gems were doing the job OK and compilations times were acceptable - not so today, Ruby SASS is far too slow and we need the performance of Libsass to make building themes a fast experience. Two years ago when the theme was first being envisioned I did not see we would have over 60 UIKit partials and more than 100 layout partials.
0 kommentar(er)
