I’m happy to announce that version 0.7.0 of CSS Lint is now available on the web site, via GitHub, and through npm. This release focused very heavily on two things: documentation and stabilization.

For documentation, we’ve moved everything over onto a wiki, which allows us to quickly and easily update the documentation and more as we go. All prior documentation on the site as well as in the source code repository has been moved to the wiki. As part of the move, there is a long (and growing) Developer Guide to help you get started with contributing to the project.

Other notable changes in this release:

  • Improvements to the build tool now allow you to run JSHint via one command on the entire codebase as well as run unit tests on the command line. See the Developer Guide for more information.
  • Mahonnaise pointed out a problem with the parser API design that prevented easy addition of rules on the fly. That issue has been fixed.
  • Brent Lintner both suggested and implemented a --quiet option for the command line interfaces.
  • I noticed an issue with the Node.js CLI where output couldn’t be captured on the command line. In the process of investigating, I discovered it to be a bug in Node.js and implemented a workaround. Unfortunately, that workaround cause another issue, reported by Grepsey, that led to another fix.
  • I updated the CSS parser to handle IE filters correctly and also to fix incorrect comment parsing as reported by andywhyisit.
  • Eric Wendelin continued his excellent work on the CLI by changing the API to accept and output relative paths by default instead of absolute paths. This does mean the output formats have changed slightly, but we think there shouldn’t be any issues related to that.

Thanks once again to all of the great feedback and contributions we’ve been receiving from the growing CSS Lint community.

Disclaimer: Any viewpoints and opinions expressed in this article are those of Nicholas C. Zakas and do not, in any way, reflect those of my employer, my colleagues, Wrox Publishing, O'Reilly Publishing, or anyone else. I speak only for myself, not for them.

Both comments and pings are currently closed.