Add Local EventEmitter map extension

.editorconfig

@@ -0,0 +1,20 @@
+root = true
+
+[*]
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+indent_style = space
+indent_size = 4
+
+[*.{ts}]
+indent_style = space
+indent_size = 4
+
+[*.{js,json}]
+indent_style = space
+indent_size = 2
+
+[{.codeclimate.yml,.eslintignore,.eslintrc,.istanbul.yml,.publishrc,.travis.yml}]
+indent_style = space
+indent_size = 2

.gitignore

@@ -59,3 +59,17 @@ typings/
 
 # next.js build output
 .next
+
+# IntelliJ
+.idea
+
+# Project
+dist
+dist-test
+lib
+lib-test
+
+#os
+.DS_Store
+.AppleDouble
+.LSOverride

.istanbul.yml

@@ -0,0 +1,46 @@
+verbose: false
+instrumentation:
+  root: lib
+  extensions:
+    - .ts
+#   default-excludes: true
+#   excludes: []
+#   variable: __coverage__
+#   compact: true
+#   preserve-comments: false
+#   complete-copy: false
+#   save-baseline: false
+#   baseline-file: ./coverage/coverage-baseline.raw.json
+#   include-all-sources: false
+#   include-pid: false
+#   es-modules: true
+#   auto-wrap: true
+# reporting:
+#   print: summary
+#   reports:
+#     - lcov
+#   dir: ./coverage
+#   summarizer: pkg
+#   report-config: {}
+#   watermarks:
+#     statements: [50, 80]
+#     functions: [50, 80]
+#     branches: [50, 80]
+#     lines: [50, 80]
+# hooks:
+#   hook-run-in-context: false
+#   post-require-hook: null
+#   handle-sigint: false
+# check:
+#   global:
+#     statements: 0
+#     lines: 0
+#     branches: 0
+#     functions: 0
+#     excludes: []
+#     each:
+#       statements: 0
+#       lines: 0
+#       branches: 0
+#       functions: 0
+#       excludes: []

.npmignore

@@ -0,0 +1,31 @@
+/.idea
+/.nyc_output
+/.vscode
+/coverage
+/dist
+/dist-test
+/docs
+/lib-test
+/not-ported-extensions
+/src
+/test
+/transpiled-code
+/typings
+CODE_OF_CONDUCT.md
+CONTRIBUTING.md
+ISSUE_TEMPLATE.md
+PULL_REQUEST_TEMPLATE.md
+karma.conf.js
+tsconfig.json
+tsconfig.test.json
+tslint.json
+tslint.test.json
+webpack.config.js
+yarn.lock
+.editorconfig
+.gitignore
+.istanbul.yml
+.npmignore
+.prettierrc
+.publishrc
+.travis.yml

.prettierrc

@@ -0,0 +1,9 @@
+{
+    "printWidth": 140,
+    "tabWidth": 4,
+    "useTabs": false,
+    "semi": true,
+    "singleQuote": false,
+    "trailingComma": "none",
+    "bracketSpacing": true
+  }

.publishrc

@@ -0,0 +1,14 @@
+{
+  "validations": {
+    "vulnerableDependencies": true,
+    "uncommittedChanges": true,
+    "untrackedFiles": true,
+    "sensitiveData": true,
+    "branch": "master",
+    "gitTag": true
+  },
+  "confirm": true,
+  "publishTag": "latest --access public",
+  "prePublishScript": false,
+  "postPublishScript": false
+}

.travis.yml

@@ -0,0 +1,21 @@
+language: node_js
+node_js:
+  - stable
+env:
+  - CODECLIMATE_REPO_TOKEN=760f0ece2309fe413a1f3018f6c7ed17f5ddaefaf661670b795f507e91731eb4
+  - CODECLIMATE_API_HOST=https://codebeat.co/webhooks/code_coverage CODECLIMATE_REPO_TOKEN=aec5cdef-3f45-487e-bd68-6c07c2474f9d
+before_install:
+  - export CHROME_BIN=chromium-browser
+  - export DISPLAY=:99.0
+  - sh -e /etc/init.d/xvfb start
+  - yarn config set registry "https://registry.npmjs.org"
+  - yarn global add greenkeeper-lockfile@1
+  - yarn global add codeclimate-test-reporter
+before_script:
+  - greenkeeper-lockfile-update
+script:
+  - yarn run test
+after_script:
+  - greenkeeper-lockfile-upload
+after_success:
+  - codeclimate-test-reporter < coverage/lcov.info

.vscode/settings.json

@@ -0,0 +1,5 @@
+// Place your settings in this file to overwrite default and user settings.
+{
+  "typescript.tsdk": "node_modules/typescript/lib",
+  "tslint.configFile": "tslint.test.json",
+}

CHANGELOG.md

@@ -0,0 +1,7 @@
+# RobotlegsJS EventEmitter3 Changelog:
+
+## Robotlegs-EventEmitter3 0.0.1
+
+### v0.0.1
+
+- Extends `IEventMap` to support `EventEmitter3` events (see #1).

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 contact@robotlegsjs.io. 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,46 @@
+# Contributing to Robotlegs-EventEmitter3
+
+## Setup
+
+1 - Clone your fork of the repository:
+```
+$ git clone https://github.com/YOUR_USERNAME/RobotlegsJS.git
+```
+
+2 - Install npm dependencies using yarn:
+```
+$ yarn install
+```
+
+3 - Run start process
+```
+$ yarn start
+```
+
+4 - Run test process
+```
+$ yarn test
+```
+
+## Guidelines
+
+- Please try to [combine multiple commits before
+pushing](http://stackoverflow.com/questions/6934752/combining-multiple-commits-before-pushing-in-git).
+
+- Please use `TDD` when fixing bugs. This means that you should write a unit
+test that fails because it reproduces the issue, then fix the issue and finally run
+the test to ensure that the issue has been resolved. This helps us to prevent
+fixed bugs from happening again in the future.
+
+- Always format your code using `yarn run autoformat`.
+
+- Please keep the test coverage at 100%. Write additional unit test if
+necessary.
+
+-  Please create an issue before sending a PR if your commit is going to change the
+public interface of the package or it includes significant architecture
+changes.
+
+- Feel free to ask for help from other members of the RobotlegsJS team via the
+[gitter chat](https://gitter.im/RobotlegsJS/RobotlegsJS) or
+[github issues](https://github.com/RobotlegsJS/RobotlegsJS-EventEmitter3/issues).

ISSUE_TEMPLATE.md

@@ -0,0 +1,35 @@
+<!--- Provide a general summary of the issue in the Title above -->
+
+## Expected Behavior
+<!--- If you're describing a bug, tell us what should happen -->
+<!--- If you're suggesting a change/improvement, tell us how it should work -->
+
+## Current Behavior
+<!--- If describing a bug, tell us what happens instead of the expected behavior -->
+<!--- If suggesting a change/improvement, explain the difference from current behavior -->
+
+## Possible Solution
+<!--- Not obligatory, but suggest a fix/reason for the bug, -->
+<!--- or ideas how to implement the addition or change -->
+
+## Steps to Reproduce (for bugs)
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+4.
+
+## Context
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+<!--- Providing context helps us come up with a solution that is most useful in the real world -->
+
+## Your Environment
+<!--- Include as many relevant details about the environment you experienced the bug in -->
+* Version used:
+* Environment name and version (e.g. Chrome 39, node.js 5.4):
+* Operating System and version (desktop or mobile):
+* Link to your project:
+
+# Stack trace
+<!--- Include stack trace -->

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2018 RobotlegsJS
+Copyright (c) 2018-present, RobotlegsJS
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,43 @@
+<!--- Provide a general summary of your changes in the Title above -->
+
+## Description
+
+<!--- Describe your changes in detail -->
+
+## Related Issue
+
+<!--- This project only accepts pull requests related to open issues -->
+<!--- If suggesting a new feature or change, please discuss it in an issue first -->
+<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
+<!--- Please link to the issue here: -->
+
+## Motivation and Context
+
+<!--- Why is this change required? What problem does it solve? -->
+
+## How Has This Been Tested?
+
+<!--- Please describe in detail how you tested your changes. -->
+<!--- Include details of your testing environment, and the tests you ran to -->
+<!--- see how your change affects other areas of the code, etc. -->
+
+## Types of changes
+
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+
+- [ ] Updated docs / Refactor code / Added a tests case (non-breaking change)
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
+
+## Checklist:
+
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+
+- [ ] My code follows the code style of this project.
+- [ ] My change requires a change to the documentation.
+- [ ] I have updated the documentation accordingly.
+- [ ] I have read the **CONTRIBUTING** document.
+- [ ] I have added tests to cover my changes.
+- [ ] All new and existing tests passed.