fix bug and add run utils

Author: swyxio

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,39 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+    - OS: [e.g. iOS]
+    - Browser [e.g. chrome, safari]
+    - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+    - Device: [e.g. iPhone6]
+    - OS: [e.g. iOS8.1]
+    - Browser [e.g. stock browser, safari]
+    - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.
+        

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,21 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
+        

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -0,0 +1,24 @@
+* **Please check if the PR fulfills these requirements**
+- [ ] The commit message follows our guidelines
+- [ ] Tests for the changes have been added (for bug fixes / features)
+- [ ] Docs have been added / updated (for bug fixes / features)
+
+
+* **What kind of change does this PR introduce?** (Bug fix, feature, docs update, ...)
+
+
+
+* **What is the current behavior?** (You can also link to an open issue here)
+
+
+
+* **What is the new behavior (if this is a feature change)?**
+
+
+
+* **Does this PR introduce a breaking change?** (What changes might users need to make in their application due to this PR?)
+
+
+
+* **Other information**:
+        

.gitignore

@@ -0,0 +1,107 @@
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+lerna-debug.log*
+
+# Diagnostic reports (https://nodejs.org/api/report.html)
+report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+*.lcov
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (https://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+jspm_packages/
+
+# Snowpack dependency directory (https://snowpack.dev/)
+web_modules/
+
+# TypeScript cache
+*.tsbuildinfo
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Microbundle cache
+.rpt2_cache/
+.rts2_cache_cjs/
+.rts2_cache_es/
+.rts2_cache_umd/
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variables file
+.env
+.env.test
+
+# parcel-bundler cache (https://parceljs.org/)
+.cache
+
+# Next.js build output
+.next
+
+# Nuxt.js build / generate output
+.nuxt
+dist
+
+# Gatsby files
+.cache/
+# Comment in the public line in if your project uses Gatsby and not Next.js
+# https://nextjs.org/blog/next-9-1#public-directory-support
+# public
+
+# vuepress build output
+.vuepress/dist
+
+# Serverless directories
+.serverless/
+
+# FuseBox cache
+.fusebox/
+
+# DynamoDB Local files
+.dynamodb/
+
+# TernJS port file
+.tern-port
+
+# Stores VSCode versions used for testing VSCode extensions
+.vscode-test

CODE_OF_CONDUCT.md

@@ -0,0 +1,47 @@
+# 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. 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,15 @@
+## Contributing
+
+First fork this project.  
+
+* git clone <your-forked-repo>
+* npm install
+
+* git checkout -b my-fix
+
+#### fix some code...
+
+* git commit -m "added this feature"
+* git push origin my-fix
+
+Lastly, open a pull request on Github.

README.md

@@ -0,0 +1,75 @@
+# Notes 
+
+may need the project to locally install `axe-core`, the resolution is
+[a little weird](https://github.com/dequelabs/axe-cli/blob/819eaf299affdcb9e8e9ec76b843e231778612c1/lib/utils.js)
+
+this may be a duplicate of https://github.com/netlify/build/pull/294
+
+# netlify-plugin-fetch-feeds
+
+Run axe-cli and fail build if accessibility failures are found.
+
+
+> NOTICE: This is an experimental feature. Subject to lots of change.
+
+
+## Overview
+
+Run axe-cli and fail build if accessibility failures are found.
+
+## Demonstration
+
+See this plugin being used in this simplified demo site:
+
+## Usage
+
+### Prerequisites
+
+- npm and node
+- @Netlify/build (later this will be included in the Netlify CLI)
+- A free [Netlify account](https://netlify.com)
+- Opt-in to Netlify Build Plugin feature support (Not yet publicly available, sorry)
+
+
+### Including this plugin in a project
+
+This plugin can be included via npm. Install it as a dependency for your project like so:
+
+```
+npm install --save netlify-plugin-axe
+```
+
+### Configuration
+
+This plugin will fetch the specified feeds and stash their data prior to the execution of the `build` command you have specified in your Netlify configuration. The desired feeds can be specified in the `netlify.toml` config file. For simpler configuration syntax, I recommend using yaml rather than toml by instead including a `netlify.yml` file.
+
+To use plugins, a `plugins` array should be specified in your `netlify.yml`. Each plugin can then be specified with its parameters like so:
+
+```yaml
+plugins:
+  - netlify-plugin-axe:
+    # type: ./path-to-plugin-file | npm-module-name
+    type: netlify-plugin-fetch-feeds
+    config:
+      site: mycoolsite.netlify.com # your Netlify site url
+      # https://github.com/dequelabs/axe-cli#running-specific-rules
+      axeFlags: --tags wcag2a
+```
+
+
+### Execution in Netlify
+
+Once installed and configured, the plugin will automatically run in the Netlify CI during its specified Netlify Build lifecycle event.
+
+### Executing locally
+
+To test the execution of the Netlify Build lifecycle locally, first ensure that netlify-build is installed:
+
+```bash
+# Ensure that you have the netlify build command available
+# (in future this will be provided via the CLI)
+npm install @netlify/build -g
+
+# In the project working directory, run the build as netlify would with the build bot
+netlify-build
+```

index.js

@@ -0,0 +1,37 @@
+const {
+  cwd,
+  env: { SITE }
+} = require('process');
+
+const execa = require('execa');
+const makeDir = require('make-dir');
+
+function netlifyPlugin(conf) {
+  return {
+    name: 'netlify-plugin-axe',
+    async onPostBuild({
+      pluginConfig: { site, axeFlags },
+      constants: { CACHE_DIR },
+      utils: { run }
+    }) {
+      const resultsDir = `${CACHE_DIR}/axe-results`;
+      await makeDir(resultsDir);
+
+      const resultsPath = `${resultsDir}/result.json`
+        .replace(cwd(), '')
+        .replace(/^\//, '');
+
+      await run.command(
+        `./node_modules/.bin/axe ${site} ${axeFlags} --save ${resultsPath}`
+      );
+
+      let results = require(resultsPath);
+      if (results && results[0]) {
+        results = results[0].violations;
+      }
+      console.log({ violations: results, len: results.length });
+    }
+  };
+}
+
+module.exports = netlifyPlugin;