Updated with latest Mix

Author: devanandb

.appveyor.yml

@@ -1,32 +1,28 @@
 # Test against all supported versions of Node.js on windows
 environment:
-  matrix:
-    - nodejs_version: "6"
-    - nodejs_version: "7"
-    - nodejs_version: "8"
-    - nodejs_version: "9"
+    matrix:
+        - nodejs_version: '8'
+        - nodejs_version: '9'
+        - nodejs_version: '10'
 
 cache:
- - node_modules
- - "%LOCALAPPDATA%\\Yarn"
+    - node_modules
+    - '%APPDATA%\npm-cache'
 
 # Install scripts. (runs after repo cloning)
 install:
-  # Get the version of Node.js
-  - ps: Install-Product node $env:nodejs_version
-  # install modules – uses yarn to avoid the following case
-  # npm 3.10.10, used in node 6 environment doesn't respect package.lock and thus installs other versions of packages
-  # than later npm releases. This causes hashes to be different and thus it causes tests to fail in the
-  # node 6 environment
-  - yarn
+    # Get the version of Node.js
+    - ps: Install-Product node $env:nodejs_version
+    - npm install --global npm@latest
+    - npm ci
 
 # Post-install test scripts.
 test_script:
-  # Output useful info for debugging.
-  - node --version
-  - yarn --version
-  # run tests
-  - yarn test
+    # Output useful info for debugging.
+    - node --version
+    - npm --version
+    # run tests
+    - npm test
 
 # Don't actually build.
 build: off

.eslintignore

@@ -0,0 +1,27 @@
+{
+    "parserOptions": {
+        "ecmaVersion": 6,
+        "sourceType": "module"
+    },
+    "env": {
+        "node": true
+    },
+    "rules": {
+        "no-const-assign": "error",
+        "newline-before-return": "error",
+        "semi": "error",
+        "no-unreachable": "error",
+        "no-extra-semi": "error",
+        "no-unexpected-multiline": "error",
+        "comma-dangle": [
+            "error",
+            {
+                "arrays": "never",
+                "objects": "never",
+                "imports": "never",
+                "exports": "never",
+                "functions": "never"
+            }
+        ]
+    }
+}

.eslintrc

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

.gitattributes

@@ -1,4 +1,8 @@
-.nyc_output
-coverage
 node_modules/
-npm-debug.log
+notes.md
+coverage
+.nyc_output
+.idea/
+*.log
+package-lock.json
+yarn.lock

.gitignore

@@ -0,0 +1,5 @@
+{
+    "hooks": {
+        "pre-commit": "pretty-quick --staged"
+    }
+}

.huskyrc

@@ -0,0 +1 @@
+.nyc_output

.prettierignore

@@ -0,0 +1,6 @@
+{
+    "endOfLine": "lf",
+    "singleQuote": true,
+    "tabWidth": 4,
+    "semi": true
+}

.prettierrc

@@ -2,16 +2,20 @@ language: node_js
 
 # Test linux and osx
 os:
-  - linux
-  - osx
+    - linux
+    - osx
 
 # Test against all supported versions of Node.js
 node_js:
-  - "6"
-  - "7"
-  - "8"
-  - "9"
+    - '8'
+    - '10'
+    - '12'
+    - '13'
+
+# Run ESLint after npm test
+script:
+    - npm run eslint
 
 cache:
-  directories:
-    - "node_modules"
+    directories:
+        - 'node_modules'

.travis.yml

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2018 Devanand
+Copyright (c) 2020 Devanand
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

CODE_OF_CONDUCT.md

@@ -1,21 +1,13 @@
 # Autoloading
 
-```js
-mix.autoload({
-   jquery: ['$', 'window.jQuery']
-});
-```
-
-Webpack offers the necessary facilities to make a module available as a variable in every other module required by Webpack. If you're working with a particular plugin or library that depends upon a global variable, such as jQuery, `mix.autoload()` may prove useful to you.
-
-> In fact, because jQuery is such a frequent example, Webpack Mix ships with jQuery autoloading out of the box. Should you need to disable this, you may pass an empty object to `mix.autoload({})`.
+Webpack offers the necessary facilities to make a module available as a variable in every other module required by webpack. If you're working with a particular plugin or library that depends upon a global variable, such as jQuery, `mix.autoload()` may prove useful to you.
 
 Consider the following example:
 
 ```js
 mix.autoload({
-   jquery: ['$', 'window.jQuery']
+    jquery: ['$', 'window.jQuery']
 });
 ```
 
-This snippet specifies that Webpack should prepend `var $ = require('jquery')` to every location that it encounters either the global `$` identifier, or `window.jQuery`. Nifty!
+This snippet specifies that webpack should prepend `var $ = require('jquery')` to every location that it encounters either the global `$` identifier, or `window.jQuery`. Nifty!

LICENSE

@@ -1,28 +1,26 @@
 # Basic Example
 
-Webpack Mix is a clean layer on top of Webpack to make the 80% use case laughably simple to execute. Most would agree that, though incredibly powerful, Webpack ships with a steep learning curve. But what if you didn't have to worry about that?
+Webpack Mix is a clean layer on top of webpack to make the 80% use case laughably simple to execute. Most would agree that, though incredibly powerful, webpack ships with a steep learning curve. But what if you didn't have to worry about that?
 
 Have a look at a basic `webpack.mix.js` file. Let's imagine that we only desire JavaScript \(ES2015 with modules\), and Sass compilation:
 
 ```js
-let mix = require('webpack-mix').mix;
+let mix = require('webpack-mix');
 
-mix.sass('src/app.sass', 'dist')
-   .js('src/app.js', 'dist');
+mix.sass('src/app.sass', 'dist').js('src/app.js', 'dist');
 ```
 
 Done. Simple, right?
 
-1. Compile the Sass file, `./src/app.sass`, to `./dist/app.sass`
-2. Bundle all JavaScript \(and any required modules\) at `./src/app.js` to `./dist/bundle.js`.
+1. Compile the Sass file, `./src/app.sass`, to `./dist/app.css`
+2. Bundle all JavaScript \(and any required modules\) at `./src/app.js` to `./dist/app.js`.
 
-With this configuration in place, we may trigger Webpack from the command line: `node_modules/.bin/webpack`.
+With this configuration in place, we may trigger webpack from the command line: `node_modules/.bin/webpack`.
 
-During development, it's unnecessary to minify the output, however, this will be performed automatically when you trigger Webpack within a production environment: `export NODE_ENV=production webpack`.
+During development, it's unnecessary to minify the output, however, this will be performed automatically when you trigger webpack within a production environment: `export NODE_ENV=production webpack`.
 
 ### Less?
 
-But what if you prefer Less compilation instead? No problem. Just swap `mix.sass()` with `mix.less()`, and you're done! 
-
-You'll find that most common Webpack tasks become a cinch with Webpack Mix. 
+But what if you prefer Less compilation instead? No problem. Just swap `mix.sass()` with `mix.less()`, and you're done!
 
+You'll find that most common webpack tasks become a cinch with Webpack Mix.

_config.yml

@@ -14,13 +14,11 @@ mix.browserSync('my-domain.test');
 // https://browsersync.io/docs/options/
 mix.browserSync({
     proxy: 'my-domain.test'
-})
+});
 ```
 
 You may pass either a string (proxy) or object (BrowserSync settings) to this method. The domain name you declare as your proxy is vital. This will proxy output from webpack Dev Server through BrowserSync.
 
 Other options can be seen in the [Browsersync Documentation](https://browsersync.io/docs/options/).
 
 Now, boot up the dev server (`npm run watch`), and you're all set go!
-
-

docs/autoloading.md

@@ -7,7 +7,7 @@ mix.minify('src');
 mix.minify(['src']);
 ```
 
-If used properly, Webpack Mix and Webpack should take care of all the necessary module bundling and minification for you. However, you may have some legacy code or vendor libraries that need to be concatenated and minified. Not a problem.
+If used properly, Webpack Mix and webpack should take care of all the necessary module bundling and minification for you. However, you may have some legacy code or vendor libraries that need to be concatenated and minified. Not a problem.
 
 ### Combine Files
 
@@ -38,11 +38,8 @@ mix.minify(['this/one.js', 'and/this/one.js']);
 
 There are a few things worth noting here:
 
-1. This method will overwrite the existing file.
+1. This method will create a companion `*.min.ext` file. So minifying `app.js` will generate `app.min.js`.
 2. Once again, the minification will only take place during a production build. \(`export NODE_ENV=production`\).
 3. There is no need to call `mix.combine(['one.js', 'two.js'], 'merged.js').minify('merged.js');`Just stick with the single `mix.combine()` call. It'll take care of both.
 
 > **Important**: Please note that minification is only available for CSS and JavaScript files. The minifier will not understand any other provided file type.
-
-
-

docs/basic-example.md

@@ -13,5 +13,4 @@ From time to time, you'll want to copy one or more files, as part of your build
 mix.copy('node_modules/vendor/acme.txt', 'public/js/acme.txt');
 ```
 
-Upon compilation, the "acme" directory will be moved to `public/js/acme.txt`, accordingly. A common use case for this is when you wish to move a set of fonts, installed through NPM, to your public directory.
-
+Upon compilation, the "acme" file will be copied to `public/js/acme.txt`, accordingly. A common use case for this is when you wish to move a set of fonts, installed through NPM, to your public directory.