add node modules to repo

node_modules/electron-packager/.github/config.yml

@@ -0,0 +1,43 @@
+# Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
+
+# Comment to be posted to on first time issues
+newIssueWelcomeComment: |
+  👋 Thanks for opening your first issue here! If you have a question about using Electron Packager, read the [support docs](https://github.com/electron-userland/electron-packager/blob/master/SUPPORT.md). If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. Development and issue triage is community-driven, so please be patient and we will get back to you as soon as we can.
+
+  To help make it easier for us to investigate your issue, please follow the [contributing guidelines](https://github.com/electron-userland/electron-packager/blob/master/CONTRIBUTING.md#before-opening-bug-reportstechnical-issues).
+
+# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
+
+# Comment to be posted to on PRs from first time contributors in your repository
+newPRWelcomeComment: |
+  Thanks for opening a pull request!
+
+  Here are some highlighted action items that will help get it across the finish line, from the
+  [pull request guidelines](https://github.com/electron-userland/electron-packager/blob/master/CONTRIBUTING.md#filing-pull-requests):
+  - Follow the [JavaScript coding style](https://standardjs.com/).
+  - Run `npm run lint` locally to catch formatting errors earlier.
+  - Document any user-facing changes in `NEWS.md` and other docs.
+  - Include tests when adding/changing behavior.
+
+  Development and triage is community-driven, so please be patient and we will get back to you as soon as we can.
+
+# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
+
+# Comment to be posted to on pull requests merged by a first time user
+firstPRMergeComment: >
+  Thanks for your contribution! 🎉
+
+# Configuration for request-info - https://github.com/behaviorbot/request-info
+
+# *Required* Comment to reply with
+requestInfoReplyComment: >
+  Thanks for filing this issue/PR! It would be much appreciated if you could provide us with more information so we can effectively analyze the situation in context.
+
+# *OPTIONAL* default titles to check against for lack of descriptiveness
+# MUST BE ALL LOWERCASE
+requestInfoDefaultTitles:
+  - update readme.md
+  - updates
+
+# *OPTIONAL* Label to be added to Issues and Pull Requests with insufficient information given
+requestInfoLabelToAdd: needs info

node_modules/electron-packager/.github/issue_template.md

@@ -0,0 +1,33 @@
+<!--
+Thanks for filing an issue!
+If you have questions about usage, see <https://github.com/electron-userland/electron-packager/blob/master/SUPPORT.md>.
+Please check off all of the steps as they are completed by replacing [ ] with [x].
+-->
+
+* [ ] I have read the [contribution documentation](https://github.com/electron-userland/electron-packager/blob/master/CONTRIBUTING.md) for this project.
+* [ ] I agree to follow the [code of conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project follows, as appropriate.
+* [ ] I have searched the issue tracker for an issue that matches the one I want to file, without success.
+
+**Please describe your issue:**
+
+
+<!-- For bugs and questions, please answer these questions to the best of your ability. -->
+
+**Console output when you run electron-packager with the environment variable `DEBUG=electron-packager`. Please include the stack trace if one exists.**
+
+```
+Put the console output here
+```
+
+**What command line arguments are you passing? Alternatively, if you are using the API, what
+parameters are you passing to the `packager()` function?**
+
+```
+Put the arguments or parameters here
+```
+
+**Please provide either a failing minimal testcase (with a link to the code) or detailed steps to
+reproduce your problem. Using [electron-quick-start](https://github.com/electron/electron-quick-start)
+is a good starting point.**
+
+

node_modules/electron-packager/.github/no-response.yml

@@ -0,0 +1,14 @@
+# Configuration for probot-no-response - https://github.com/probot/no-response
+
+# Number of days of inactivity before an Issue is closed for lack of response
+daysUntilClose: 14
+
+# Label requiring a response
+responseRequiredLabel: needs info
+
+# Comment to post when closing an Issue for lack of response. Set to `false` to disable
+closeComment: >
+  Since the original issue reporter has not responded to the request for additional
+  information in about two weeks, it's assumed that they either found the
+  answer in another manner or decided not to pursue this issue. If this is incorrect,
+  they can respond with answers to the questions posed, and this issue can be reopened.

node_modules/electron-packager/.github/pull_request_template.md

@@ -0,0 +1,13 @@
+<!--
+Thanks for filing a pull request!
+Please check off all of the steps as they are completed by replacing [ ] with [x].
+-->
+
+* [ ] I have read the [contribution documentation](https://github.com/electron-userland/electron-packager/blob/master/CONTRIBUTING.md) for this project.
+* [ ] I agree to follow the [code of conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project follows, as appropriate.
+* [ ] The changes are appropriately documented (if applicable).
+* [ ] The changes have sufficient test coverage (if applicable).
+* [ ] The testsuite passes successfully on my local machine (if applicable).
+
+**Summarize your changes:**
+