refactor: apply webpack-defaults

Author: michael-ciniawsky

.babelrc

@@ -0,0 +1,35 @@
+{
+  "presets": [
+    [
+      "env",
+      {
+        "useBuiltIns": true,
+        "targets": {
+          "node": "4.3"
+        },
+        "exclude": [
+          "transform-async-to-generator",
+          "transform-regenerator"
+        ]
+      }
+    ]
+  ],
+  "plugins": [
+    [
+      "transform-object-rest-spread",
+      {
+        "useBuiltIns": true
+      }
+    ]
+  ],
+  "env": {
+    "test": {
+      "presets": [
+        "env"
+      ],
+      "plugins": [
+        "transform-object-rest-spread"
+      ]
+    }
+  }
+}

.editorconfig

@@ -0,0 +1,13 @@
+# editorconfig.org
+
+[*]
+charset = utf-8
+indent_style = space
+indent_size = 2
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[.md]
+insert_final_newline = false
+trim_trailing_whitespace = false

.eslintignore

@@ -0,0 +1,2 @@
+/node_modules
+/dist

.eslintrc

@@ -0,0 +1,3 @@
+{
+  "extends": "webpack"
+}

.eslintrc.yml

@@ -1,3 +1,5 @@
 yarn.lock -diff
 * text=auto
 bin/* eol=lf
+
+package-lock.json -diff

.gitattributes

@@ -1,15 +1,7 @@
-<!-- Before creating an issue please make sure you are using the latest version of css-loader. -->
+<!--
+1. Check the version of package you are using. If it's not the newest version, update and try again (see changelog while updating!).
+2. If the issue is still there, write a minimal project showing the problem and expected output.
+3. Link to the project and mention Node version and OS in your report.
 
-**Do you want to request a *feature* or report a *bug*?**
-<!-- Please ask questions on StackOverflow or the webpack Gitter (https://gitter.im/webpack/webpack). Questions will be closed. -->
-
-**What is the current behavior?**
-
-**If the current behavior is a bug, please provide the steps to reproduce.**
-<!-- A great way to do this is to provide your configuration via a GitHub gist. -->
-
-**What is the expected behavior?**
-
-**If this is a feature request, what is motivation or use case for changing the behavior?**
-
-**Please mention other relevant information such as your webpack version, Node.js version and Operating System.**
+**IMPORTANT! You should use [Stack Overflow](https://stackoverflow.com/) for support related questions.**
+-->

.github/ISSUE_TEMPLATE.md

@@ -1,18 +1,5 @@
-<!-- Thanks for submitting a pull request! Please provide enough information so that others can review your pull request. -->
-
-**What kind of change does this PR introduce?**
-<!-- E.g. a bugfix, feature, refactoring, build related change, etc… -->
-
-**Did you add tests for your changes?**
-
-**If relevant, did you update the README?**
-
-**Summary**
-
-<!-- Explain the **motivation** for making this change. What existing problem does the pull request solve? -->
-<!-- Try to link to an open issue for more information. -->
-
-**Does this PR introduce a breaking change?**
-<!-- If this PR introduces a breaking change, please describe the impact and a migration path for existing applications. -->
-
-**Other information**
+<!--
+1. [Read and sign the CLA](https://cla.js.foundation/webpack/webpack.js.org). This needs to be done only once. PRs that haven't signed it won't be accepted.
+2. Check out the [development guide](https://webpack.js.org/development/) for the API and development guidelines.
+3. Read through the PR diff carefully as sometimes this can reveal issues. The work will be reviewed, but this can save some effort.
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,3 +1,20 @@
 node_modules
 coverage
 npm-debug.log
+
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+.eslintcache
+/coverage
+/dist
+/local
+/reports
+/node_modules
+.DS_Store
+Thumbs.db
+.idea
+.vscode
+*.sublime-project
+*.sublime-workspace

.gitignore

@@ -0,0 +1 @@
+package-lock=false