Initial commit

.editorconfig

@@ -0,0 +1,10 @@
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+max_line_length = 80
+trim_trailing_whitespace = true
+insert_final_newline = true

.eslintrc.yml

@@ -0,0 +1,13 @@
+plugins: [node, prettier]
+env:
+  node: true
+  es6: true
+parserOptions:
+  ecmaVersion: 2021
+  sourceType: module
+extends:
+  - plugin:import/errors
+  - plugin:import/warnings
+  - eslint:recommended
+  - plugin:node/recommended
+  - prettier

.gitattributes

@@ -0,0 +1 @@
+* text=auto eol=lf

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @netlify/workflow

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,57 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: 'Please replace with a clear and descriptive title'
+labels: bug
+assignees: ''
+---
+
+Thanks for reporting this bug!
+
+If this is related to a typo or the documentation being unclear, please click on
+the relevant page's `Edit` button (pencil icon) and suggest a correction
+instead.
+
+Please search other issues to make sure this bug has not already been reported.
+
+Then fill in the sections below.
+
+**Describe the bug**
+
+A clear and concise description of what the bug is.
+
+**Steps to reproduce**
+
+Step-by-step instructions on how to reproduce the behavior.
+
+Example:
+
+1. Type the following command: [...]
+2. etc.
+
+**Expected behavior**
+
+A clear and concise description of what you expected to happen.
+
+**Configuration**
+
+Command line options and/or configuration file, if any.
+
+**Environment**
+
+Enter the following command in a terminal and copy/paste its output:
+
+```bash
+npx envinfo --system --binaries --browsers --npmPackages netlify-plugin-{{name}}
+```
+
+**Screenshots**
+
+If applicable, add screenshots to help explain your problem.
+
+**Can you submit a pull request?**
+
+Yes/No.
+
+Pull requests are welcome! If you would like to help us fix this bug, please
+check our [contributions guidelines](../blob/master/CONTRIBUTING.md).

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,30 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: 'Please replace with a clear and descriptive title'
+labels: enhancement
+assignees: ''
+---
+
+Thanks for suggesting a new feature!
+
+Please fill in the sections below.
+
+**Which problem is this feature request solving?**
+
+Example: I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+
+Example: This could be fixed by [...]
+
+**Describe alternatives you've considered**
+
+Example: Another solution would be [...]
+
+**Can you submit a pull request?**
+
+Yes/No.
+
+Pull requests are welcome! If you would like to help us add this feature, please
+check our [contributions guidelines](../blob/master/CONTRIBUTING.md).

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,24 @@
+🎉 Thanks for submitting a pull request! 🎉
+
+#### Summary
+
+Fixes #<replace_with_issue_number>
+
+<!--
+Explain the **motivation** for making this change. What existing problem does the pull request solve and how?
+-->
+
+---
+
+For us to review and ship your PR efficiently, please perform the following steps:
+
+- [ ] Open a [bug/issue](https://github.com/netlify/build-plugin-template/issues/new/choose) before writing your code 🧑‍💻. This
+      ensures we can discuss the changes and get feedback from everyone that should be involved. If you\`re fixing a
+      typo or something that\`s on fire 🔥 (e.g. incident related), you can skip this step.
+- [ ] Read the [contribution guidelines](../CONTRIBUTING.md) 📖. This ensures your code follows our style guide and
+      passes our tests.
+- [ ] Update or add tests (if any source code was changed or added) 🧪
+- [ ] Update or add documentation (if features were changed or added) 📝
+- [ ] Make sure the status checks below are successful ✅
+
+**A picture of a cute animal (not mandatory, but encouraged)**

.github/pull_request_template.md

@@ -0,0 +1,34 @@
+🎉 Thanks for sending this pull request! 🎉
+
+Please make sure the title is clear and descriptive.
+
+If you are fixing a typo or documentation, please skip these instructions.
+
+Otherwise please fill in the sections below.
+
+**Which problem is this pull request solving?**
+
+Example: I'm always frustrated when [...]
+
+**List other issues or pull requests related to this problem**
+
+Example: This fixes #5012
+
+**Describe the solution you've chosen**
+
+Example: I've fixed this by [...]
+
+**Describe alternatives you've considered**
+
+Example: Another solution would be [...]
+
+**Checklist**
+
+Please add a `x` inside each checkbox:
+
+- [ ] I have read the [contribution guidelines](../blob/master/CONTRIBUTING.md).
+- [ ] I have added tests (we are enforcing 100% test coverage).
+- [ ] I have added documentation in the `README.md`, the `docs` directory (if
+      any) and the `examples` directory (if any).
+- [ ] The status checks are successful (continuous integration). Those can be
+      seen below.

.gitignore

@@ -0,0 +1,13 @@
+*~
+*.swp
+npm-debug.log
+node_modules
+/core
+.eslintcache
+.npmrc
+.yarn-error.log
+.nyc_output
+!.github/
+/coverage
+/build
+.netlify

.prettierrc.yml

@@ -0,0 +1,6 @@
+semi: false
+singleQuote: true
+printWidth: 80
+endOfLine: lf
+proseWrap: always
+trailingComma: all

CODE_OF_CONDUCT.md

@@ -0,0 +1,82 @@
+# Code of Conduct
+
+This text is available in
+[many other languages](https://www.contributor-covenant.org/translations).
+
+## 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, sex characteristics, gender identity and
+expression, level of experience, education, socio-economic status, 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}}.
+
+All complaints will be reviewed and investigated and will result in a response
+that is deemed necessary and 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
+https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,75 @@
+# Contributions
+
+🎉 Thanks for considering contributing to this project! 🎉
+
+These guidelines will help you send a pull request.
+
+If you're submitting an issue instead, please skip this document.
+
+If your pull request is related to a typo or the documentation being unclear,
+please click on the relevant page's `Edit` button (pencil icon) and directly
+suggest a correction instead.
+
+This project was made with ❤️. The simplest way to give back is by starring and
+sharing it online.
+
+Everyone is welcome regardless of personal background. We enforce a
+[Code of conduct](CODE_OF_CONDUCT.md) in order to promote a positive and
+inclusive environment.
+
+# Development process
+
+First fork and clone the repository. If you're not sure how to do this, please
+watch
+[these videos](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github).
+
+Run:
+
+```bash
+npm install
+```
+
+Make sure everything is correctly setup with:
+
+```bash
+npm test
+```
+
+# Development tasks
+
+The following development tasks are available. Please check the
+[`package.json`](/package.json) `scripts` property for more information.
+
+```bash
+npm run build
+```
+
+Runs a Netlify Build locally with the current plugin. This can be used for
+debugging and manual tests.
+
+The local Build configuration file is [`netlify.toml`](/netlify.toml) and can be
+modified.
+
+```bash
+npm run ava
+```
+
+Runs [unit tests](/test/index.js).
+
+```bash
+npm run lint
+```
+
+Lints and prettifies source files.
+
+```bash
+npm test
+```
+
+Runs both unit tests and linting.
+
+```bash
+npm run release
+```
+
+Publishes this plugin to `npm`.

LICENSE.md

@@ -0,0 +1,20 @@
+MIT License
+
+Copyright (c) {{year}} {{author}}
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.