Using JSCS and jscs-fixer for Atom.io
by YLD • April 15th, 2015 • 3min
In this post we’ll take a brief look at JSCS and take a peak at jscs-fixer, an Atom.io package that allows you to automatically apply JSCS code-style rules to your scripts.
If you don’t know JSCS and decide to visit it’s website, jscs.info, you are greeted with the following description:
JSCS is a code style linter for programmatically enforcing your style guide. You can configure JSCS for your project in detail using over 90 validation rules, including presets from popular style guides like jQuery, Airbnb, Google, and more.
I love using JSCS, mainly because it is a great way of making sure that all developers on a team are adhering to the same style guide and ensures that no-one gets to make their own choices regarding the code-style being used.
There are a couple of other tools that could be used in this process but they differ from JSCS, mainly:
- JSLint and JSHint, which both focus on ensuring best coding practices but don’t offer any way of enforcing a given code-style, and
- ESLint, which allows for people to implement their own style rules. A good example of this would be Feross’ standard module.
There’s also a set of preset rules from different companies/projects/teams, the likes of which include Google, Airbnb, the jQuery and Grunt projects, and even a Node.js style guide, that you can use and customise via a .jscsrc file that you include in your project root referencing a preset and your tweaks to it, or even your own set of rules.
As for my personal taste, I usually use it as a pre-commit hook, to ensure that no one commits and/or pushes code that doesn’t conform to the chosen code-style. It helps enforce cohesion with your team or contributors, even more in this last case where you can potentially have dozens of contributions from different developers that could wreak havoc in your project. I also use JSCS directly in my editor, as you will see next.
Being a JSCS user and after reading an article by Addy Osmani on JSCS’ new auto-formatting feature and seeing his examples using the SublimeText editor and the SublimeLinter-JSCS plugin, I felt a little left behind since I’m an Atom editor user.
Although I’m using the great linter and linter-jscs Atom packages, they don’t (yet) offer a way of auto-formatting your scripts, which you have to do by hand, even if those packages help you to identify your code-style violations directly in your editor’s workflow.
All things considered, I thought it would be cool if I developed an Atom package that would allow developers to format their scripts based on a project’s style guide. Making this package would be the proverbial killing of two birds with one stone. (Please keep in mind that no real birds were killed in the making of jscs-fixer).
Creating a package
First of all, the atom.io documentation pages are great regarding the editor’s customisation and the how-to’s for creating new themes or packages are also excellent.
I’ve followed the instructions on this page and as quickly as waiting on a new editor window to open, I had my first Atom package skeleton ready for me to hack on it.
My goal for this package was very simple: it would allow you to format (or fix) a file based on the rules defined on your .jscsrc file.
The simplest way to do it would be to run the jscs binary providing it with the — fix flag and the path to the file the user wants to fix.
To avoid dealing with the user having to configure the path to a system-wide jscs binary or developers having to add it as a local dependency on their project, the jscs-fixer package declares it as a dependency on it’s package.json file, thus allowing the binary to be invoked directly from the node_modules folder instead of having to figure out where it is on the user system.
The package can be invoked with one of the following options
- From Command Palette (⌘+⌂+P) invoke jscs Fixer: Fix
- Right-click on one of the selected files and choose Fix this file using jscs
- Use the keyboard shortcut — ctrl+⌂+J
I do intend, in the near future, to add a settings view to the package that would allow a user to customise some details like the location of their prefered JSCS installation (either system-wide or project based) or to define the location of a .jscsrc or a default preset to use as a fallback.
Of course, this package is open-source and the code can be found in its repository and the package page, so go ahead and install it and start fixing your scripts automatically from within your editor.
Written by Fábio Oliveira — Originally published on April 15, 2015 for YLD.
You may also like:
Written by YLD • April 15th, 2015
Share this article