If the repo has its own guidelines and they conflict, the more specific one wins.
If a guideline would conflict with common sense, follow common sense.
Consider adding yourself to the contributors list in package.json if you like.
Keep them sorted alphabetically please.
However, to avoid diff noise, it would be a good idea to make one entry stay at the bottom at all times.
If the current maintainer (probably me) is in that list, let's keep their item at bottom.
Also please add an empty line above that so I can use the "select remainder of paragraph" command for easy sort.
When my files start with jslint directives and I haven't configured a linter, they're meant for jslint --edition=2013-08-26.
(I mostly understand why the later jslint editions – or rather, the concepts behind the new rules and defaults – are superior, but I'm not yet able to accept that insight.)
Feel free to add "lint": "jslint --edition=2013-08-26 '**/*.js{,on}'", to the npm scripts. I'm usually too lazy because in my shell it's just three letters to invoke a proprietary unified lint tool that lints even more stuff.
If you wonder about my package.json's npm vs. BOM = Unexpected token field, see here.
cool, thanks! Here are my default guidelines:
package.jsonif you like.jslint --edition=2013-08-26."lint": "jslint --edition=2013-08-26 '**/*.js{,on}'",to the npm scripts. I'm usually too lazy because in my shell it's just three letters to invoke a proprietary unified lint tool that lints even more stuff.package.json'snpm vs. BOM = Unexpected tokenfield, see here.