JSCS v2.3.1 Release Notes

  • ๐Ÿš€ A bunch of bug fixes in this release!

    The Future

    ๐Ÿš€ We are probably going to start 3.0 for the next release (mainly integrating CST into JSCS). If you want to know more about CST check out the previous changelog.

    ๐Ÿš€ Our current plan is to move our 3.0/cst branch to master and then create a 2.x branch to continue to release bug fixes / contributer PRs. The core team will be mainly focused on tackling issues on our 3.0 roadmap (which we are still planning). We would love to hear your feedback on what you think should be in 3.0 and beyond!

    ๐Ÿ› Bug fixes

    // Allow MemberExpressions: require('a').b.c;
    var fs = require('fs');
    var Emitter = require('events').EventEmitter;
    
    // this should be allowed
    var f = {
        "name": 1,
        "x": 2
    };
    
    // Should output:
    // Param unusedParam is not used at input
    var a = function(unusedParam) {}
    
    // check all keys
    var x = {
      bar: 1,
      foo: $(".foo") // error here
    };
    
    // Don't error with this
    const [beep, boop] = meep;
    var $s = $("#id")
    
    • ๐Ÿ”ง CLI - "auto-configure" argument should always be at the end (Oleg Gaidarenko)
    // correct autoconfigure args
    jscs --autoconfigure ./files/here
    
    • ๐Ÿ“œ js-file - make parser not confuse token types (Oleg Gaidarenko)
    // Fixes issues with keywords like with
    class A {
      catch() {}
    }
    

    Again, a big thanks to everything using [JSCS](jscs.info)! Definitely continue to report any bugs and new ideas! We always appreciate any help/PRs!

    We'll probably be moving more of the new rule/option issues to orphaned which just means that they are on hold but anyone can still PR it or reopen it later. Remember to tweet at us at @jscs_dev and chat with us on our gitter room!

    hzoo