Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Cory Simmons
    @corysimmons
    @kaizokuace No. Jeet is mostly legacy now. I'd suggest migrating to something like Lost or postcss-ant.
    Daniel Mee
    @danielmee
    @corysimmons so I shouldn't use Jeep in a new project? It was just updated wasn't it? I'll check out Lost et al but it's a shame as I really thought Jeet worked well. Hope the others are as easy to use.
    Cory Simmons
    @corysimmons
    @danielmee A lot of those updates were just cleaning it up/making it more stable.
    If Jeet is working really well for you, I wouldn't waste time/efficiency learning something new just because someone told you it's better.
    Don't fall into that trap.
    Lost is really easy to use and really stable. It's very similar to Jeet except it uses calc for fixed gutters without needing to add context when you nest. Basically .grid > .nested-grid { columns(1/4 1/2) } turns into .grid > .nested-grid { lost-column: 1/4 }
    And there is still the concept of cycling, but Lost will try to do it automatically (as determined by the denominator -- although you can specify it).
    postcss-ant is more flexible than pretty much anything out there. It's very similar to Grid Layout with its sizing capabilities, but works in IE9. It's stable, but it's a work in progress. If you decide to use it on a project, I'd be glad to fix any little bugs you might run into instantly, as well as hand-hold.
    Daniel Mee
    @danielmee
    Thanks @corysimmons - I've only just started using these things but coming from a designer background I'm reliant on whatever works with CodeKit; Jeet is baked in (and the developer said they'll be supporting 7) so that's easy. Having said that tho, I'm always open to checking out other alternatives, if the same simplicity is there as Jeet then I'll be interested in postcss-ant for sure. Thanks for your generosity and help!
    Cory Simmons
    @corysimmons
    If you're going to take frontend development seriously, you need to get comfortable with the command line.
    And how to use CLI-friendly npm packages.
    Otherwise you'll always be dependent on a GUI integrating features you may really want.
    So for Lost and postcss-ant, you'd do something like npm i postcss-cli postcss-ant
    Then node_modules/.bin/postcss --watch --use postcss-ant -o output.css input.css
    But I really understand the simplicity of using something that JustWorks™. I'd just suggest once you get to the point where you feel like your hands are tied, commit to learning the command line -- you won't regret it.
    And you're welcome. =)
    Hasen Ahmad
    @kaizokuace
    yea for me the issue isn't whether jeet is better or something. Im working on the webpack build process and it would be very nice and simple if I can run all my stylus plugins thru postcss. Im currently using both stylus with it's plugins (jeet, nib and rupture) and postcss for other stuff like autoprefixer. Its hard when you are in an active project and need to keep something like jeet around.
    Cory Simmons
    @corysimmons
    I see that point, but tbh, I prefer running those things separately anyway.
    PostCSS' preprocessor-like offerings aren't as stable as real preprocessors, and I <3 preprocessors.
    For instance, PreCSS has lots of little bugs and isn't maintained anymore. Whereas Sass/Stylus are fairly bulletproof.
    So I've had great success with node-sass -> css -> postcss -> css
    Hasen Ahmad
    @kaizokuace
    hmm that is a good point
    tarikmiljkovic
    @tarikmiljkovic
    Hi, would someone help me to install the jeet?
    when I compile my stylus fil (.styl), I allways get error
    because of the following coe
    code*
    @import 'node_modules/jeet/jeet'
    how can I know what is the right path
    I have my website on Desktop
    Cory Simmons
    @corysimmons
    @tarikmiljkovic What error do you get?
    Are you following these instructions? https://github.com/mojotech/jeet/blob/master/docs/stylus.md
    tarikmiljkovic
    @tarikmiljkovic
    Bildschirmfoto 2017-01-23 um 20.43.13.png
    is that okay?
    Cory Simmons
    @corysimmons
    @tarikmiljkovic You need a package.json file
    echo '{}' > package.json
    Cory Simmons
    @corysimmons
    Done maintaining. Removed myself. Bye.
    Guillermo Latorre
    @Superwillyfoc_twitter
    Hi, I have a website I built some months ago with CodeKit 2 and Jeet (I guess it was version 6). Now I have to make some changes, CodeKit is upgraded to version 3 and it comes with Jeet 7 included. So now the compilation process fails. I've read the Jeet migration guide on GitHub but I don't know how to solve the problem, so... could you please help me?
    I am using stylus and the compilation error reported by CodeKit is a "parse error" in my main.styl file, where I define the gutter size like:
    $jeet: ( gutter: 0.38 );
    I've tried writing "$gutter" instead of "gutter" and moving that line before and after the @import "jeet" line, but it does not work
    Josh Beyer
    @Joshbeyer
    Ok, so this $uncycle thing. Its killing me. I am trying to learn jeet, and its beautiful, and wonderful, and perfect, but... I can't get stacking to work... When I lower the width of the screen, things should begin to stack. It's not working and Im so upset lol
    If anyone even gets on this channel anymore let me know..
    physicalgorithm
    @physicalgorithm

    Hey, I'm newbie with Jeet, I think the documentation of usage Jeet isn't enough. I didn't understand even how to make columns. I just type ''col(1/3)'' for my menu's anchor tag, when I tried on mobile screen, It didn't change.

    And I didn't understand what is ''edit()'' Jeet API doesn't tells.

    Daniel Mee
    @danielmee
    Hello @physicalgorithm - unfortunately support for Jeet has been discontinued and the developer is recommending Lost or postcss-ant. See the history of this thread for more info. However, to your actual question, Jeet does work but the documentation did lead me astray sometimes. I haven't used Jeet in ages but one of the gotchas I remember was realising the documentation was written for Stylus not Sass. So 'col(1/2)' needs to be written '@include col(1/2);'
    I don't remember seeing edit() and I can't see it in the website API docs or a quick skim through the GitHub version https://github.com/mojotech/jeet/blob/master/docs/api.md
    physicalgorithm
    @physicalgorithm
    What you suggesting me? Should I quit Jeet.gs and move on with another framework? @danielmee
    Daniel Mee
    @danielmee
    I've used it successfully in projects and I really liked it's simplicity but it's no longer being maintained. Are you able to read the previous posts in this thread? Scroll up to Cory Simmons comment starting Dec 14 2016 and read from there.
    physicalgorithm
    @physicalgorithm
    Oh I got know, If it's maintained anymore I should check out others. I'll look for postCSS thanks for your help @danielmee
    Dave Nielsen
    @dhniels
    has anyone used jeet successfully with a jekyll site?