It supports things like semi-colon insertion, case correction, missing curly braces, and removes debugger statements. Sindre said Addy Osmani wrote an article about it, where he points out some important things that fixmyjs can get wrong:
As mentioned earlier, the current version of the module uses Escodegen, which rewrites your source and doesn't take into account original styling information (i.e it will strip it). This makes it easier for the author to support complex new rules as they operate with an AST rather than relying on less reliable approaches like string replacement.
You can avoid this by using the legacy option.
If you use Atom, then you can install Sindre's Atom plugin for fixmyjs. It uses legacy by default, and can be run on a whole file or a selection.
Several people picked Chrome, probably because the development tools have progressed so much over the last year or so. It's increasingly common to see people testing design ideas or puzzling over CSS quirks by editing HTML and CSS in the inspector. I've recently started using the device emulation tab a lot for responsive designs as well.
In this example, -e is used to supply a JSON file that has configuration options for Postman's environment. Newman's readme has more examples and documentation.
selenium-test-runner (GitHub: tkambler / selenium-runner, License: MIT) by Tim Ambler is a library for writing Selenium tests in a blocking style. It uses node-fibers so you can avoid promises and chained expressions.
ncc, or node-crome-canvas, (GitHub: indus / ncc, License: MIT, npm: ncc) by Stefan Keim, uses the Chrome remote debugging protocol to build a bridge to the native HTMlCanvasElement and its 2d-Context. That means you can send drawing operations from the server to Chrome.
Here's an example:
var ncc = require('ncc')
var canvas = ncc();
canvas.width = canvas.height = 256;
var ctx = canvas.getContext('2d');
ctx.fillStyle = 'slateGray';
ctx.fillRect(28, 28, 200, 200)();
The Chrome Store itself is a pile of rubbish apps with very few exceptions.
If you're into client-side web development to any extent, you've probably heard of Facebook's React library. I was working on a Chrome extension, and decided to see how well React fit in to the development I was doing.
He also uses Browserify as well, which I'm interested in because I tried using RequireJS for sharing code between Chrome extensions and Firefox add-ons, and I struggled to get it to work in Firefox. My Firefox add-ons are using the Jetpack SDK rather than the old XUL way.
We wanted to get data from the current web page and then use it to populate a form that appears in a new window.
It was easy to create a context menu item that triggered an event, but sending data based on the current page to the new window wasn't obvious.
You might find this useful if you're just getting into Chrome extensions and want more concrete examples than what Google provides.
Dynatable (GitHub: JangoSteve / jquery-dynatable, License: AGPL or commercial) by Steve Schwartz is a library for displaying JSON data as friendly and efficient HTML tables. It provides a framework for searching, sorting, and filtering data. It uses jQuery, and can be invoked with $.dynatableSetup.
Dynatable can convert plain HTML tables into JSON. The properties for the JSON can be camelCase, but other styles are supported, including dashed and underscore. This is set with the table.defaultColumnIdStyle option.
JSON can also be fetched from a server. In this case you can use the dataset option:
It expects a corresponding skeleton table node, with thead and tbody.
The documentation is thorough and includes examples for each of these things, and the other features provided by the library.
Nobody's sent me a jQuery gallery for a while. nanoGALLERY (GitHub: Kris-B / nanoGALLERY, License: CC BY-NC 3.0) by Christophe Brisbois supports Flickr and Google+, and supports responsive layouts. You can get a gallery going with a Google account like this:
It comes with CSS, but you can theme it. It displays a gallery navigator using folders, so it could scale up quite well to a large collection.
Documentation for the main options and expected markup can be found in the project's readme file.
jQuery Audit (GitHub: zertosh / jquery-audit, License: MIT) by Andres Suarez is a Chrome Developer Tools extension for auditing jQuery. It adds a sidebar (under Elements) that includes details of delegated events and internal data.
The documentation has explanations of the main features, and instructions on how to use the extension properly. For example, you can dig into bound functions for event handlers which can be bound differently based on the library.
By incorporating amdclean.js into the build process, there is no need for Require or Almond.
So, you get great code cleanliness with AMD, reduced file sizes, improved code readability, and easy integration with other developers who may not use AMD.
Greg notes that it also supports Grunt, so it should be easy to drop into your existing projects.