Updated today and new project is failing in a few spots

[Blumed]

running: nvm - node 4.2.1 jekyll - 3.3.1 jekyllized - 3.3.6 OS - mac - Sierra

I want to point out I have 2 of your builds running perfectly fine on other projects, but today a fresh install is breaking in a few spots.

1. Yet another issue with node-sass. Seems like everyone has issues with node-sass. Gulp-sass needs to update from @2.1.1 to @3.13. Build won't enable the next layer of errors until I change this and run npm install yet again.

2. Now I get errors about jekyll-paginate, and jekyll-gist. Adding them to the _config.yml like gems: [jekyll-paginate, jekyll-gist]

3. Now everything runs and my output stops at[23:41:33] Finished 'jekyll:dev' after 1.1 s and then it just sits. No errors. No warnings. I have been putting console logs in different sections and nothing seems to be outputting anything interesting.

Any ideas? I'm at a loss.

P.s. I also want to thank you. I have learned a lot about jekyll and gulp from your code. I built a few jekyll/gulp builds myself and by doing so I learned to appreciate how you set up your build environment.

[Blumed]

Here is my repo that won't build. https://github.com/Blumed/deviceinfo

[sondr3]

Hey, I'll take a look as soon as I can. Might not be until Monday when I've finished my exam :)

[sondr3]

Sorry, I completely forgot to get back to you! I couldn't find any issues locally when I tested it two weeks ago but now that I've updated Node I can't even get it to run gulp due to some incompatibilities with the latest version of Node, so I'll have to look into it. 😅 Did you solve it yourself. I'm so sorry for not getting back to you in due time.

[Blumed]

Hey man, Thanks for getting back to me. No worries 👍

I have not solved it yet. You will be the first to know if I do.

[Blumed]

Just did a fresh install again and ran the following. I am on node 4.2.6, gulp 3.3.8 and updated gulp-sass and node-sass. Deleted the node_modules folder and ran npm install again. Everything downloaded perfectly on the first go this time. Yay! progress

-Next I get warning about jekyll-paginate. It was not in my gem file when I downloaded it. I added it and ran bundle plus added gems: [jekyll-paginate] to _config.yml

-Next error! Since v3.0, permalinks for pages in subfolders must be relative to the site source directory, not the parent directory. Check http://jekyllrb.com/docs/upgrading/ for more info. In _config.yml I changed relative_permalinks to false.

-Next error! Liquid Exception: Liquid syntax error (line 49): Unknown tag 'gist' in /Users/Master/Sites/jekyllized/src/_drafts/2014-03-01-example-content.md

I added gems: [jekyll-paginate, jekyll-gist] to the _config.yml and jekyll-gist to the gemfile and ran bundle.

BOOOOOOM! it works :)

So there seems to be some items missing for me. node-sass, gulp-sass, jekyll-paginate, jekyll-gist. Did you not run into all of this?

[Blumed]

here is what my files looked like when I downloaded them. gemfile:

source "http://rubygems.org"

gem 'jekyll'
gem 'redcarpet'
gem 'classifier-reborn'
gem 'fast-stemmer'
gem 'jekyll-paginate'
gem 'jekyll-gist'

_config.yml:

# Title, decription, tagline and URL for your site
# Can be used in your theme by calling 'site.title' and so on
title: 
description: 
tagline: 
url: localhost:4000

# Used so Jekyll outputs the site correctly so Gulp can do what it wants
source: src
destination: serve

# Same as the title etc for your site but can instead be
# called by using 'site.author.name' and so on
author:
  name: 
  email: 
  bio: 
  twitter: 

# general setting for Jekyll
googleAnalytics: UA-XXXXX-X

# _config.build.yml overwrites these options when you run `gulp build`
# Enables future posts (posts with dates in the future) and drafts
future: true
show_drafts: true
# Disables the more accurate related posts for faster generating of the site
lsi: false
# Only make the last 10 posts so generating isn't slow
limit_posts: 10

# Permalink structure and pagination options
relative_permalinks: true
permalink: pretty
paginate: 10
paginate_path: 'page:num'
excerpt_separator: '<!--more-->'

# Markdown library
markdown: redcarpet
# Markdown library options
redcarpet:
  extensions: ['no_intra_emphasis', 'tables', 'fenced_code_blocks', 'autolink', 'smart',
              'strikethrough', 'superscript', 'underline', 'highlight', 'footnotes']
highlighter: true

[Blumed]

Do think this an issue with needing to purge the old version of your generator before I download your updated version? I updated your package using the yo update. The output of the two files look exactly like how they did in your previous versions.

[sondr3]

No idea, none of this looks correct to me and is not the intended output. I'll look into it tomorrow.

[Blumed]

Did a fresh install on my new work computer. Exact same issues.

[sondr3]

Your config file looks nothing like the one that's supposed to be created, are you sure you're not doing something weird? It's supposed to look like this, not whatever yours look like. You're actually overwriting the files when updating, right?

[Blumed]

On my work computer, I installed your generator for the first time. So.... ??? I am not 100% sure if they are overwriting. I assume when I update your package -g it is. I have run the update yo way and the npm update generator-jekyll -g both give me a broken install.

[sondr3]

When you run the generator again in the directory you want to update it'll ask you whether you want to overwrite the files, which you should do because it'll update it. Otherwise you end up with old settings that are incompatible with the latest version.

[Blumed]

I am spinning up a new folder each time. I am not updating in a pre existing folder.

[Blumed]

my work computer that I tried this morning didn't have yo or your generator on it when I installed it.

[Blumed]

Would you like to screenshare?

[sondr3]

You are actually not running the latest version, I think it might be with how your version of Node and NPM interprets versions, because the latest version should be 1.0.0-rc.7, not 0.7.4 (which you are using, and it's really old). If you want to update to the actual latest version you could run npm install -g generator-jekyllized@1.0.0-rc.7 to install the latest version. Although you'll still have to update gulp-sass manually.

[Blumed]

interesting. Okay, switched to a 4.2.6 using nvm. Added the gulp-cli, yo, your generator. Everything installed perfectly. You have a .tmp/src directory in this installation?

[Blumed]

I can fix the pathing, but the first load is showing up "Cannot GET /"

[Blumed]

I didn't have to update gulp-sass by the way.

[sondr3]

Yep, you could also look at the top of the gulpfile and you should see what version of the generator was used to generate the setup. And the error with Cannot GET / usually means there's a problem with Jekyll, which is always fun. Try to do bundle clean --force and bundle install and see if that fixes the problem. The error with gulp-sass might only be with my version of Node then, nice to know.

[Blumed]

nah, that one is my bad. New computer. I didn't set up my gem installs.

[Blumed]

styles are not loading tho. I am figuring it out tho 👍

[Blumed]

Looks like they should be injected? reading the commented out sections?

[sondr3]

Yeah, when running gulp command it'll look for your assets and automatically inject them, or at least, it should do that.

[Blumed]

Dude, I'm solid. I really like what you're doing with gulp task breakouts. Babel is awesome. Post mortem - I needed to use a specific revision like "npm install -g generator-jekyllized@1.0.0-rc.7" instead of "npm install -g generator-jekyllized".

[Blumed]

Thanks for all your help!

[sondr3]

No problem at all! Happy it worked out in the end. Just a bit strange that it didn't install the latest pre-release version automatically, it does so on my computer. But oh well 😃