Revamp the API and configuration to allow for more modular rules to be added

.babelrc

@@ -0,0 +1,10 @@
+{
+  "presets": [
+    "es2015",
+    "stage-0",
+    "react"
+  ],
+  "plugins": [
+    "transform-runtime"
+  ]
+}

.eslintignore

@@ -0,0 +1,2 @@
+lib/
+webpack.config.js

.eslintrc

@@ -0,0 +1,54 @@
+{
+    "env": {
+        "browser": true,
+        "node": true,
+        "es6": true,
+        "mocha": true
+    },
+    "parserOptions": {
+        "ecmaVersion": 2017,
+        "sourceType": "module",
+        "ecmaFeatures": {
+            "jsx": true,
+            "modules": true
+        }
+    },
+    "extends": [
+        "airbnb"
+    ],
+    "plugins": [
+        "babel",
+        "mocha",
+        "react"
+    ],
+    "rules": {
+        "babel/new-cap": 1,
+        "comma-dangle": ["error", "never"],
+        "complexity": ["warn", { "max": 7 }],
+        "generator-star-spacing": 1,
+        "id-length": ["error", { "exceptions": ["_", "x", "y", "z", "i", "e", "t"] }],
+        "import/no-named-as-default": 0, // connected/test-only components
+        "import/no-extraneous-dependencies": ["error", {"devDependencies": true}], // tests
+        "indent": ["error", 4, {"SwitchCase": 2}],
+        "max-len": [1, 120, 2, {"ignoreComments": true}],
+        "no-await-in-loop": 1,
+        "no-param-reassign": ["error", { "props": false }],
+        "no-plusplus": ["error", { "allowForLoopAfterthoughts": true }],
+        "no-underscore-dangle": "off",
+        "no-use-before-define": [2, "nofunc"],
+        "no-unused-vars": "warn",
+        "object-shorthand": 1,
+        "quotes": [2, "single"],
+        "react/forbid-prop-types": [1, { "forbid": ["any"] }], // used in conjunction with the transform-react-remove-prop-types babel plugin
+        "react/jsx-filename-extension": [1, { "extensions": [".js", ".jsx"]  }],
+        "react/jsx-indent": ["error", 4],
+        "react/jsx-indent-props": ["error", 4],
+        "react/jsx-uses-react": 2,
+        "react/jsx-uses-vars": 2,
+        "react/no-find-dom-node": "warn", // TODO: change this to error and fix findings
+        "react/prop-types": 0, // not currently working for stateless components: https://github.com/yannickcr/eslint-plugin-react/issues/803
+        "react/react-in-jsx-scope": 2,
+        "strict": [2, "never"],
+        "vars-on-top": "error"
+    }
+}

.gitignore

@@ -1,2 +1,4 @@
-dist
+dist/
+lib/
 node_modules/
+npm-debug.log

.npmignore

@@ -1,6 +1,4 @@
-CONTRIBUTING.md
-bower.json
-lib
+*.log
+test
 karma.conf.js
-scripts
 webpack.config.js

.travis.yml

@@ -1,6 +1,17 @@
 language: node_js
+
 node_js:
-  - "0.10"
+  - "stable"
+  - "8"
+  - "7"
+  - "6"
+  - "4"
+
 before_script:
   - export DISPLAY=:99.0
-  - sh -e /etc/init.d/xvfb start
+  - sh -e /etc/init.d/xvfb start
+
+cache: yarn
+
+matrix:
+  fast_finish: true

CHANGELOG.md

@@ -1,7 +1,32 @@
-v0.3.3 - Fri, 15 Apr 2016 19:32:24 GMT
+0.3.6 - Thu, 12 Oct 2017 12:50:02 GMT
+-------------------------------------
+
+- [b8f4e58](../../commit/b8f4e58) Update ReactDOM for react v16 compatibility
+
+
+v0.3.5 - Tue, 30 May 2017 14:23:58 GMT
+-----------------------------------------
+
+- [a7eb16f](../../commit/a7eb16f) Fixed #16 inappropriately referencing this in a context where this is actually undefined.
+
+
+v0.3.4 - Sun, 30 Apr 2017 20:48:28 GMT
 --------------------------------------
 
-- 
+- [e41ba68](../../commit/e41ba68) Fixed #11 from being too strict testing for use-onblur-not-onchange.  Now it should pass if onChange is used in addition to onBlur.
+- [3173a1d](../../commit/3173a1d) Fixed #10 where if a tagName is being checked for reserved in the DOM object but does not exist in the DOM object an exception was being thrown
+- [d0401be](../../commit/d0401be) 1. Updated eslint and plugin versions 2. Added the AirBnB eslint config to inherit 3. Fixed all linter findings
+
+
+v0.3.3 - Mon, 3 Apr 2017 23:01:39 GMT
+--------------------------------------
+
+- [d85328e](../../commit/d85328e) Added some more scripts for helping with the version and publish process and added descriptions of the scripts in the CONTRIBUTING.md
+- [2ffa8ac](../../commit/2ffa8ac) Added a CONTRIBUTING page and linked to it from the README.
+- [c715c45](../../commit/c715c45) Updated urls to point to this repo instead of the forked from repo
+- [fa32346](../../commit/fa32346) Added the bundle script to the prepublish script so that the webpack bundle gets included in the npm package.  Also disabled the release script and removed the rf-release package as this does not seem to be tagging or publishing to npm properly.
+- [8bff3fe](../../commit/8bff3fe) Added/removed dirs and files from npmignore
+- [be6f51e](../../commit/be6f51e) Adding some tags! Added <svg> and <path>
 
 
 v0.3.2 - Tue, 15 Mar 2016 00:16:50 GMT

CONTRIBUTING.md

@@ -1,44 +1,118 @@
-### Tests
+# Contributing to react-a11y
 
-All commits that fix bugs or add features need a test.
+## Setting up the workspace
 
-`<blink>` Do not merge code without tests.`</blink>`
+Before you can submit a Pull Request you'll need to do the following:
 
-### Commit Subjects for Public API Changes
+1. Fork the repository on GitHub
 
-If your patch **changes the API or fixes a bug** please use one of the
-following prefixes in your commit subject:
+2. Clone your fork
 
-- `[fixed] ...`
-- `[changed] ...`
-- `[added] ...`
-- `[removed] ...`
+```bash
+git clone https://github.com/<your_username>/react-a11y.git
+cd react-a11y
+```
 
-That ensures the subject line of your commit makes it into the
-auto-generated changelog. Do not use these tags if your change doesn't
-fix a bug and doesn't change the public API.
+3. Install for development
 
-Commits with changed, added, or removed, should probably be reviewed by
-another collaborator.
+```bash
+npm install
+```
 
-#### When using `[changed]` or `[removed]`...
+## Workflow
 
-Please include an upgrade path with example code in the commit message.
-If it doesn't make sense to do this, then it doesn't make sense to use
-`[changed]` or `[removed]` :)
+Lint the code:
 
-### Docs
+```bash
+npm run lint
+```
 
-Please update the docs with any API changes, the code and docs should
-always be in sync.
+Run the tests:
 
-### Development
+```bash
+npm run mocha // run tests using mocha only
+npm run karma // run tests using karma only
+npm run test  // run tests using both mocha and karma
+```
 
-- `npm test` will fire up a karma test runner and watch for changes
+Build the code:
 
-### Build
+```bash
+npm run build
+```
 
-Please do not include the output of `scripts/build` in your commits, we
-only do this when we release. (Also, you probably don't need to build
-anyway unless you are fixing something around our global build.)
+## Making changes
 
+1. Checkout a new branch and name it accordingly to what you intend to do
+
+```bash
+git checkout -b <branch_name>
+```
+
+2. Make your intended changes, being sure to run the tests and lint the code.
+
+## Submitting a Pull Request
+
+1. Commit your changes (please make commits small and commit messages descriptive):
+
+```bash
+    git commit -m "..."
+```
+
+2. Push to _your_ github repo:
+```bash
+git push origin <branch_name>
+```
+
+3. Go to the GitHub page and click "New Pull request".
+4. Write a good description of the change.
+
+After sending a pull request, other developers will review and discuss your change. Please address all the comments. Once everything is all right, one of the maintainers will merge your changes in.
+
+## Publishing (for maintainers)
+_These steps are for maintainers only and can be disregarded by contributors._
+
+For publishing use the following workflow:
+
+1. Make sure all code changes for this new version have already been committed.
+
+2. Update the CHANGELOG.md by using the following command, double check the content and save (don't commit):
+```bash
+npm run changelog -- -t <the upcoming version>
+```
+where `<the upcoming version>` refers to the version number that you are preparing to publish
+
+3. Update the version and publish.  This is done by running _one_ of the following scripts:
+
+```bash
+npm version:patch  # for a patch version update i.e. v1.0.0 -> v1.0.1
+npm version:minor  # for a minor version update i.e. v1.0.0 -> v1.1.0
+npm version:major  # for a major version update i.e. v.1.0.0 -> v2.0.0
+```
+
+### The publishing scripts
+After running one of the above `version:*` scripts the following things will take place in this order:
+
+1. the `preversion` script will run which does the following:
+
+    1. The tests will be run and the entire process will halt if they do not all pass
+
+    2. A check will be performed to validate that the `CHANGELOG.md` has been updated and it is the only uncommitted change in the repo.  If this check fails the process will be halted.
+
+2. the selected `version:*` script will run which does the following: 
+
+    1. The version in `package.json` will be incremented as requested (patch, minor, major).  _Because the `--no-git-tag-version` flag is specified this script will not yet include tagging and committing in the github repo._
+
+3. the `postversion` script will be run which does the following:
+
+    1. A `git commit` will be made including only the `package.json` and `CHANGELOG.md` files.  It will include a commit comment in the format of: "Version $npm_package_version"
+
+    2. Performs a `git tag` in the format of "v$npm_package_version"
+
+    3. Performs a `git push` and `git push --tags`
+
+    4. Runs `npm publish`
+
+
+## Additional Resources
+* [GitHub pull request help](https://help.github.com/categories/collaborating-with-issues-and-pull-requests/)