Adding error event emitter

.babelrc

@@ -1,18 +1,3 @@
 {
-  "presets": ["es2015", "stage-0", "react"],
-  "env": {
-    "development": {
-      "plugins": [
-        "transform-class-properties",
-        ["react-transform", {
-          "transforms": [{
-            "transform": "react-transform-hmr",
-            "imports": ["react"],
-            "locals": ["module"]
-          }]
-        }],
-        "add-react-displayname"
-      ]
-    }
-  }
+  "presets": ["./.babelrc.js"]
 }

.babelrc.js

@@ -0,0 +1,41 @@
+var NODE_ENV = process.env.NODE_ENV;
+var MODULES = process.env.MODULES;
+
+var modules = MODULES === "false" || NODE_ENV === "test" ? "commonjs" : false;
+
+var config = {
+  presets: [
+    [
+      "env",
+      {
+        loose: true,
+        modules: modules,
+        forceAllTransforms: NODE_ENV === "production"
+      }
+    ],
+    "stage-0",
+    "react"
+  ],
+  plugins: []
+};
+
+if (NODE_ENV === "development") {
+  config.plugins = config.plugins.concat([
+    "transform-class-properties",
+    [
+      "react-transform",
+      {
+        transforms: [
+          {
+            transform: "react-transform-hmr",
+            imports: ["react"],
+            locals: ["module"]
+          }
+        ]
+      }
+    ],
+    "add-react-displayname"
+  ]);
+}
+
+module.exports = config;

.eslintrc

@@ -1,40 +1,31 @@
 {
   "env": {
     "browser": true,
-    "es6": true,
+    "es6": true
   },
 
   "plugins": [
     "react"
   ],
 
-  "extends": "standard",
-
   "parserOptions": {
     "ecmaVersion": 6,
     "sourceType": "module",
     "ecmaFeatures": {
-      "jsx": true,
-    },
+      "jsx": true
+    }
   },
 
   "parser": "babel-eslint",
 
   "rules": {
-    "jsx-quotes": [2, "prefer-double"],
-    "no-irregular-whitespace": 0,
     "react/display-name": 2,
     "react/forbid-prop-types": 0,
     "react/jsx-boolean-value": 2,
-    "react/jsx-closing-bracket-location": [2, 'after-props'],
-    "react/jsx-curly-spacing": [2, "never"],
-    "react/jsx-indent-props": 2,
     "react/jsx-key": 2,
-    "react/jsx-max-props-per-line": [2, { "maximum": 4 }],
     "react/jsx-no-duplicate-props": 2,
     "react/jsx-no-literals": 0,
     "react/jsx-no-undef": 2,
-    "react/jsx-pascal-case": 2,
     "react/jsx-sort-props": 0,
     "react/jsx-uses-react": 2,
     "react/jsx-uses-vars": 2,
@@ -52,6 +43,5 @@
     "react/react-in-jsx-scope": 2,
     "react/self-closing-comp": 2,
     "react/sort-comp": 2,
-    "react/wrap-multilines": 0,
   }
 }

.flowconfig

@@ -0,0 +1,11 @@
+[ignore]
+
+[include]
+
+[libs]
+
+[lints]
+
+[options]
+
+[strict]

.gitignore

@@ -1,10 +1,12 @@
 node_modules
 .sass-cache
 npm-debug.log
+.DS_Store
 .idea
 .vscode
-dist
-lib
+;dist
+;lib
+;es
 tmp
 coverage
 docs-site/bundle.js

.travis.yml

@@ -1,23 +1,20 @@
-sudo: false
 language: node_js
 node_js:
   - "6"
-env:
-  - CXX=g++-4.8
-addons:
-  apt:
-    sources:
-      - ubuntu-toolchain-r-test
-    packages:
-      - g++-4.8
 before_install:
-  - npm install -g grunt-cli
+  - npm i -g npm@latest
+
+  # Needed for Karma test runner
   - export DISPLAY=:99.0
   - sh -e /etc/init.d/xvfb start
+# install:
+#   - yarn install
 script:
+  - yarn lint
   - yarn test
 after_success:
   - yarn run codecov
 notifications:
   slack:
     secure: kAmrLltV0ZLuhl6rKk26fDLGuoCch6AYaObRQje4UZlxVQjR2467k430vOZLqv39Mr3U5XmYl6VLcCGmBr3tjM/9c1zjoXnRT8MRy4eIYaUr/thXeh2FlfHKOk8rXnNOoRZ1kBsCzCDFCNDYZZA4jya8S5ITcQyGyYcOqBWVy1w=
+cache: yarn

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,21 @@
+# How to contribute
+
+Thanks for taking your time to read this. We're thrilled you're reading this because we the help from the community to keep improving this project.
+
+## Testing
+
+We have a handful of Cucumber features, but most of our testbed consists of RSpec examples. Please write RSpec examples for new code you create.
+
+## Submitting changes
+
+Please send a [GitHub Pull Request](https://github.com/Hacker0x01/react-datepicker/pull/new/master) with a clear list of what you've done (read more about [pull requests](http://help.github.com/pull-requests/)). When you send a pull request, we will love you forever if you include a test to cover your changed. We can always use more test coverage.
+Always write a clear log message for your commits. One-line messages are fine for small changes, but bigger changes should look like this:
+$ git commit -m "A summary of the commit > > A paragraph describing what changed and its impact."
+
+## Coding conventions
+
+Start reading our code, and you'll get the hang of it. We optimize for readability:
+
+* We use prettier for code styling. Don't worry about tabs vs spaces, or how to indent your code.
+* We use ESlint for all other coding standards. We try to be consistent and helpful.
+* This is open source software. Consider the people who will read your code, and make it look nice for them. It's sort of like driving a car: Perhaps you love doing donuts when you're alone, but with passengers, the goal is to make the ride as smooth as possible.

ISSUE_TEMPLATE.md

@@ -0,0 +1,5 @@
+### Expected behavior
+
+### Actual behavior
+
+### Steps to reprodcue

LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2016 HackerOne Inc and individual contributers
+Copyright (c) 2017 HackerOne Inc and individual contributors
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal