Jekyll Page Built Failure: File to import not found or unreadable about bourbon

[tysongach]

Hi @HP-Nunes!

How did you install Bourbon? I don’t see the Bourbon gem listed in the Gemfile, or in your source directories as static files.

[HP-Nunes]

@tysongach I made a mistake when copying my Gemfile (edited in prompt); I do have Bourbon installed, the gems themselves are installed in my root directory.

I used bundler to install the gems.

~/gems$ tree
.
├── bin
│   ├── bourbon
│   ├── bundle
│   ├── bundler
│   ├── commonmarker
│   ├── gemoji
│   ├── github-pages
│   ├── jekyll
│   ├── kramdown
│   ├── listen
│   ├── nokogiri
│   ├── rake
│   ├── rougify
│   ├── safe_yaml
│   ├── sass
│   ├── sass-convert
│   ├── scss
│   └── thor
├── build_info
├── cache
│   ├── activesupport-4.2.9.gem
│   ├── addressable-2.5.2.gem
│   ├── bourbon-4.3.4.gem
│   ├── bundler-1.16.6.gem
│   ├── coffee-script-2.4.1.gem
│   ├── coffee-script-source-1.11.1.gem
│   ├── colorator-1.1.0.gem
│   ├── commonmarker-0.17.13.gem
│   ├── concurrent-ruby-1.0.5.gem
│   ├── ethon-0.11.0.gem
│   ├── execjs-2.7.0.gem
│   ├── faraday-0.15.3.gem
│   ├── ffi-1.9.25.gem
│   ├── forwardable-extended-2.6.0.gem
│   ├── gemoji-3.0.0.gem
│   ├── github-pages-179.gem
│   ├── github-pages-health-check-1.4.0.gem
│   ├── html-pipeline-2.8.4.gem
│   ├── i18n-0.9.5.gem
│   ├── jekyll-3.6.2.gem
│   ├── jekyll-avatar-0.5.0.gem
│   ├── jekyll-coffeescript-1.1.1.gem
│   ├── jekyll-commonmark-1.2.0.gem
│   ├── jekyll-commonmark-ghpages-0.1.5.gem
│   ├── jekyll-compose-0.8.0.gem
│   ├── jekyll-default-layout-0.1.4.gem
│   ├── jekyll-feed-0.9.3.gem
│   ├── jekyll-gist-1.5.0.gem
│   ├── jekyll-github-metadata-2.9.4.gem
│   ├── jekyll-mentions-1.3.0.gem
│   ├── jekyll-optional-front-matter-0.3.0.gem
│   ├── jekyll-paginate-1.1.0.gem
│   ├── jekyll-paginate-v2-2.0.0.gem
│   ├── jekyll-readme-index-0.2.0.gem
│   ├── jekyll-redirect-from-0.13.0.gem
│   ├── jekyll-relative-links-0.5.3.gem
│   ├── jekyll-remote-theme-0.2.3.gem
│   ├── jekyll-sass-converter-1.5.2.gem
│   ├── jekyll-seo-tag-2.4.0.gem
│   ├── jekyll-sitemap-1.2.0.gem
│   ├── jekyll-swiss-0.4.0.gem
│   ├── jekyll-theme-architect-0.1.0.gem
│   ├── jekyll-theme-cayman-0.1.0.gem
│   ├── jekyll-theme-dinky-0.1.0.gem
│   ├── jekyll-theme-hacker-0.1.0.gem
│   ├── jekyll-theme-leap-day-0.1.0.gem
│   ├── jekyll-theme-merlot-0.1.0.gem
│   ├── jekyll-theme-midnight-0.1.0.gem
│   ├── jekyll-theme-minimal-0.1.0.gem
│   ├── jekyll-theme-modernist-0.1.0.gem
│   ├── jekyll-theme-primer-0.5.2.gem
│   ├── jekyll-theme-slate-0.1.0.gem
│   ├── jekyll-theme-tactile-0.1.0.gem
│   ├── jekyll-theme-time-machine-0.1.0.gem
│   ├── jekyll-titles-from-headings-0.5.1.gem
│   ├── jekyll-watch-1.5.1.gem
│   ├── jemoji-0.9.0.gem
│   ├── kramdown-1.16.2.gem
│   ├── liquid-4.0.0.gem
│   ├── listen-3.1.5.gem
│   ├── mercenary-0.3.6.gem
│   ├── minima-2.4.0.gem
│   ├── mini_portile2-2.3.0.gem
│   ├── minitest-5.11.3.gem
│   ├── multi_json-1.13.1.gem
│   ├── multipart-post-2.0.0.gem
│   ├── net-dns-0.8.0.gem
│   ├── nokogiri-1.8.5.gem
│   ├── octokit-4.13.0.gem
│   ├── pathutil-0.16.1.gem
│   ├── public_suffix-2.0.5.gem
│   ├── pygments.rb-1.2.1.gem
│   ├── rake-10.5.0.gem
│   ├── rb-fsevent-0.10.3.gem
│   ├── rb-inotify-0.9.10.gem
│   ├── rouge-2.2.1.gem
│   ├── ruby_dep-1.5.0.gem
│   ├── ruby-enum-0.7.2.gem
│   ├── rubyzip-1.2.2.gem
│   ├── safe_yaml-1.0.4.gem
│   ├── sass-3.6.0.gem
│   ├── sass-listen-4.0.0.gem
│   ├── sawyer-0.8.1.gem
│   ├── terminal-table-1.8.0.gem
│   ├── thor-0.20.0.gem
│   ├── thread_safe-0.3.6.gem
│   ├── typhoeus-1.3.0.gem
│   ├── tzinfo-1.2.5.gem
│   └── unicode-display_width-1.4.0.gem
(...)

[tysongach]

Oh, gotcha, thanks for clarifying.

I’m not sure you’ll be able to use Bourbon as a gem, through Jekyll’s plugin system and deploy to GitHub Pages. According to their docs, only a whitelist of plugins works when used in conjunction with GitHub Pages:

Plugins on GitHub Pages

GitHub Pages is powered by Jekyll. All Pages sites are generated using the --safe option to disable plugins (with the exception of some whitelisted plugins) for security reasons. Unfortunately, this means your plugins won’t work if you’re deploying to GitHub Pages.

You can still use GitHub Pages to publish your site, but you’ll need to convert the site locally and push the generated static files to your GitHub repository instead of the Jekyll source files.

[HP-Nunes]

@tysongach thanks for the reply. I'm having difficulty interpreting the following:

You can still use GitHub Pages to publish your site, but you’ll need to convert the site locally and push the generated static files to your GitHub repository instead of the Jekyll source files.

Does that mean I need to push the gem files from my root directory to jekyll's?

[tysongach]

I believe it means running jekyll build and publishing the built site files.

[tysongach]

I’m going to close this, as it appears to be an issue with Jekyll, not Bourbon.