Generate "jscs-browser.js" only during publishing

Fixes #466

Author: markelog

MAINTAIN.md

@@ -76,12 +76,11 @@ Preparing for a new version
    4. new options.
    5. bug fixes.
    6. infrastructure or docs changes.
-3. Update browser-version: `npm run-script browserify`.
-4. Commit under message: `Prepare for version x.x.x`.
-5. Set a new version and tag: `npm version x.x.x`.
-6. Push changes and tags: `git push && git push --tags`.
-7. Temporarily remove (but do not commit) the notice in README.md about the docs being the "development version".
-8. Ask @mdevils to publish new package for specified tag, or use `npm publish` if you have privileges.
-9. Add back the "development version" notice to the README.md file.
-10. Tweet or otherwise promote the fact that a new version has been released with a link to the changelog and npm download page.
-11. Done!
+3. Commit under message: `Prepare for version x.x.x`.
+4. Set a new version and tag: `npm version x.x.x`.
+5. Push changes and tags: `git push && git push --tags`.
+6. Temporarily remove (but do not commit) the notice in README.md about the docs being the "development version".
+7. Ask @mdevils to publish new package for specified tag, or use `npm publish` if you have privileges.
+8. Add back the "development version" notice to the README.md file.
+9. Tweet or otherwise promote the fact that a new version has been released with a link to the changelog and npm download page.
+10. Done!