chore(general): General housekeeping and file removal

removing old JS files from the previous implementation, added yarn, cleaned up package deps a little

Author: ScriptedAlchemy

README.md

@@ -23,11 +23,6 @@
 > **HEADLINES (May 2018): Now Independently supports Webpack 4:** 
 Yep that's right. The universal family is now fully Webpack 4. Thank you to all our users for your loyalty and patience! If you love Universal, then you are gonna fall head over heels when we bring out the main course! 
 
-
-> **UPDATE (July 7th):** [babel-plugin-dual-import](https://github.com/faceyspacey/babel-plugin-dual-import) is now required to asynchronously import both css + js. *Much Faster Builds!* You likely want to read [its intro article](https://medium.com/@faceyspacey/webpacks-import-will-soon-fetch-js-css-here-s-how-you-do-it-today-4eb5b4929852).
-
-> **UPDATE (July 26th):** [babel-plugin-universal-import](https://github.com/faceyspacey/babel-plugin-universal-import) is what to use if you're using *React Universal Component*. 
-
 So... why did we rebuild `extract-css-chunks`? What does it offer? 
 
 Its got all the goodness of `mini-css-extract-plugin` but with 2 gleaming, sought after benefits. 
@@ -47,6 +42,16 @@ Additionally, if you are already a user of the universal family -- we will be wa
 
 The functionality is still available to you via chunk flushing, and it can come in super handy when needing to easily resolve style assets as urls that might need to be passed to a third party.
 
+
+#BETA TESTING WEBPACK 4
+
+If you want to test this alpha branch, which is currently not published to the NPM registry. 
+
+Add the following to your package.json file, then `npm i`
+
+    "extract-css-chunks-webpack-plugin": "git+ssh://[email protected]/zackljackson/extract-css-chunks-webpack-plugin.git#webpack-4",
+
+
 ##Webpack 4 Standalone Installation:
 
 If you are just looking for something that works like `mini-css-extract-plugin` but with HMR. Then look no further
@@ -55,6 +60,7 @@ NOTE: We have aligned out loader implementation to be the same as `mini-css-extr
 
 **If you already use `mini-css-extract-plugin`, then you can just change the `require` statement - its that easy**
 
+
 ```
 yarn add --dev extract-css-chunks-webpack-plugin
 ```

jest.config.js

@@ -10,3 +10,4 @@ module.exports = {
     '<rootDir>/test/js',
   ],
 };
+

package-lock.json

@@ -18,9 +18,6 @@
     "lint": "eslint --cache --fix src test",
     "prebuild": "npm run clean",
     "prepublish": "npm run build",
-    "release": "standard-version",
-    "release:ci": "conventional-github-releaser -p angular",
-    "release:validate": "commitlint --from=$(git describe --tags --abbrev=0) --to=$(git rev-parse HEAD)",
     "security": "nsp check",
     "test": "jest",
     "test:watch": "jest --watch",
@@ -34,13 +31,12 @@
     "cm": "git-cz",
     "semantic-release": "semantic-release pre && npm publish && semantic-release post",
     "travis": "npm run cover -- --report lcovonly",
-    "prepack": "npm i && rm -rf ./node_modules"
+    "prepack": "npm i yarn && yarn && rm -rf ./node_modules"
   },
   "peerDependencies": {
     "webpack": "^4.4.0"
   },
   "dependencies": {
-    "@webpack-contrib/schema-utils": "^1.0.0-beta.0",
     "loader-utils": "^1.1.0",
     "lodash": "^4.17.5",
     "normalize-url": "^1.9.1",