The power of webpack, distilled for the rest of us.

Last update: Jul 1, 2022

Laravel Mix

Node NPM NPM NPM

Introduction

Laravel Mix thumbnail

Laravel Mix provides a clean, fluent API for defining basic webpack build steps for your applications. Mix supports several common CSS and JavaScript pre-processors.

If you've ever been confused about how to get started with module bundling and asset compilation, you will love Laravel Mix!

Documentation

You may review the initial documentation here.

License

Laravel Mix is open-sourced software licensed under the MIT license.

GitHub

https://github.com/JeffreyWay/laravel-mix
Comments
  • 1. Unexpected character '@' after upgrade from v0.5.3 to v0.5.9

    Upgrading from v0.5.3 to v0.5.9 causes the following errors:

    Module parse failed: ...resources\assets\sass\portal.scss Unexpected character '@' (1:0) You may need an appropriate loader to handle this file type. | @font-face { | font-family: 'Open Sans'; | font-style: normal;

    Switching back to v0.5.3 or v0.5.7 without any other config changes everything is ok...

    Reviewed by rn1ee at 2017-01-27 10:18
  • 2. Laravel Mix npm run dev error

    • Laravel Mix Version: 1.4.2 (npm list --depth=0)
    • Node Version (node -v): v8.2.1
    • NPM Version (npm -v): 5.3.0
    • OS: Debian 8

    Description:

    When I'm running the command npm run dev, I'm getting the following output with an error:

    [email protected]:/var/www/webinterface# npm run dev
    
    > @ dev /var/www/webinterface
    > npm run development
    
    
    > @ development /var/www/webinterface
    > cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
    
    events.js:182
          throw er; // Unhandled 'error' event
          ^
    
    Error: spawn node_modules/webpack/bin/webpack.js ENOENT
        at exports._errnoException (util.js:1024:11)
        at Process.ChildProcess._handle.onexit (internal/child_process.js:192:19)
        at onErrorNT (internal/child_process.js:374:16)
        at _combinedTickCallback (internal/process/next_tick.js:138:11)
        at process._tickCallback (internal/process/next_tick.js:180:9)
        at Function.Module.runMain (module.js:607:11)
        at startup (bootstrap_node.js:158:16)
        at bootstrap_node.js:575:3
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! @ development: `cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the @ development script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /root/.npm/_logs/2017-07-29T07_18_17_185Z-debug.log
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! @ dev: `npm run development`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the @ dev script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /root/.npm/_logs/2017-07-29T07_18_17_205Z-debug.log
    

    Steps To Reproduce:

    Clean Laravel Installation ( composer create-project laravel/laravel webinterface)

    1. run: composer install
    2. run: npm install
    3. run: npm run dev
    Reviewed by HerrTxbias at 2017-07-29 07:23
  • 3. [ON HOLD] Support for webpack 4

    This is currently blocked by an issue with webpack 4 regarding CSS chunk splitting.

    All but one test currently pass.


    I've gathered some data on which plugins have releases (beta or otherwise) that work with webpack 4. Any help here would be 👌

    Working Loaders / Plugins

    • babel-loader (7.1.3)
    • css-loader (0.28.10)
    • less-loader (4.0.6)
    • resolve-url-loader (2.3.0)
    • sass-loader (6.0.7)
    • sass-resources-loader (1.3.3)
    • stylus-loader (3.0.2)
    • ts-loader (4.0.0)
    • friendly-errors-webpack-plugin (1.7.0)
    • webpack-chunk-hash (0.6.0)

    Likely Working Loaders / Plugins

    These have not been updated but appear to work

    • coffee-loader

    Unknown

    • html-loader
    • img-loader
    • postcss-loader
    Reviewed by thecrypticace at 2018-02-25 13:22
  • 4. Cannot find module cross-env

    • Laravel Mix Version: 0.8.7
    • Node Version (node -v): 7.6.0
    • NPM Version (npm -v): 4.3.0
    • OS: MacOS

    Description:

    I am using Spark (latest version) but when I compiled css and js by using npm run dev then I got an error:

    Cannot find module '/PATH/node_modules/cross-env/bin/cross-env.js'
        at Function.Module._resolveFilename (module.js:470:15)
        at Function.Module._load (module.js:418:25)
        at Module.runMain (module.js:605:10)
        at run (bootstrap_node.js:422:7)
        at startup (bootstrap_node.js:143:9)
        at bootstrap_node.js:537:3
    
    npm ERR! Linux 3.19.0-25-generic
    npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "dev"
    npm ERR! node v7.6.0
    npm ERR! npm  v4.3.0
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! @ dev: `node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
    npm ERR! Exit status 1
    npm ERR! 
    npm ERR! Failed at the @ dev script 'node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js'.
    npm ERR! Make sure you have the latest version of node.js and npm installed.
    npm ERR! If you do, this is most likely a problem with the  package,
    npm ERR! not with npm itself.
    npm ERR! Tell the author that this fails on your system:
    npm ERR!     node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
    npm ERR! You can get information on how to open an issue for this project with:
    npm ERR!     npm bugs 
    npm ERR! Or if that isn't available, you can get their info via:
    npm ERR!     npm owner ls 
    npm ERR! There is likely additional logging output above.
    
    npm ERR! Please include the following file with any support request:
    npm ERR!     /home/vagrant/.npm/_logs/2017-02-26T08_26_31_924Z-debug.log
    

    I tried to update npm, node, laravel-mix and remove all modules in node_modules and re-install but I still got that error.

    Reviewed by phuclh at 2017-02-26 08:43
  • 5. Please test the Laravel Mix 4 Beta

    Hey, everyone. I just pushed the first beta release of Laravel Mix 4. This is the big one that catches us up to webpack 4, Babel 7, and vue-loader 15. This comes with a whole host of improvements.

    For the next week or so, I'd like as many people as possible to try it out. We had to rewrite a lot of code as part of this update, and even though all our tests are passing, you never know...

    You can install the beta release of Mix, like so:

    npm install [email protected]
    

    Upgrade Notes

    • If upgrading from Mix 2.*, and your project includes Babel plugins that are not provided by Mix out of the box, you'll need to update them. Review the Mix 3.0 release notes for more information. Don't worry, it's a quick update.
    • For optimization/minification, we've switched from uglify-js to terser. If your project was overriding any of our default uglify config, you'll need to update it to terser (very similar API).

    Gotchas

    As part of our webpack update, to require() a module or Vue SFC with the CommonJS approach, you'll now need to append .default, like so:

    Before

    Vue.component('example-component', require('./components/ExampleComponent.vue'));
    

    After

    Vue.component('example-component', require('./components/ExampleComponent.vue').default);
    

    Alternatively, you can/should switch to ES modules.

    import ExampleComponent from './components/ExampleComponent.vue';
    
    Vue.component('example-component', ExampleComponent);
    

    With this in mind, the default Laravel app resources/assets/js/app.js boilerplate code will need to be updated accordingly. One of us will take care of that once Mix 4.0 is out of beta.

    Please share any issues you come across in this thread, and we'll address them as quickly as possible.

    Reviewed by JeffreyWay at 2018-11-30 17:21
  • 6. Mix does not delete old versioned files when a new one is generated

    • Laravel Mix Version: 0.11.4
    • Node Version: v6.10.0
    • NPM Version: 3.10.10
    • OS: Windows 7 Ultimate 64x

    Description:

    When I'm using the version() function, it doesn't matter if I'm running in production mode or not, the old versioned files are not been deleted (BTW this is not a Laravel project) oij8jp6 1

    Steps To Reproduce:

    Put this setting in the webpack.mix.js 30d441f4-3aba-11e7-8472-4e598bca6e04 1

    Reviewed by DannyFeliz at 2017-05-17 08:43
  • 7. BrowserSync: Sass compilation causing whole page reload

    • Laravel Mix Version: 1.4.2 (github:jeffreyway/laravel-mix#5aad0dfde5349e284e0876388a6f307547f7c002)
    • Node Version (node -v): 8.2.1
    • NPM Version (npm -v): 5.3.0
    • OS: macOS Sierra 10.12.6

    Description:

    When using browserSync, css changes are injected however the page is also reloaded due to the fact that the JS bundle is re-emitted even when the only file that changed was a sass file.

    Steps To Reproduce:

    webpack.mix.js:

    mix
    	.js('resources/assets/js/main.js', 'public/assets/js/bundle.js')
    	.extract(['jquery', 'babel-polyfill'])
    	.autoload({
    		jquery: ['$', 'jQuery', 'window.jQuery']
    	})
    	.sass('resources/assets/sass/style.scss', 'public/assets/css')
    	.disableNotifications()
    	.options({
    			processCssUrls: false
    	})
    	.sourceMaps()
    	.browserSync({
    		proxy: process.env.APP_URL,
            files: [
                'app/**/*.php',
                'resources/views/**/*.php',
                'public/assets/js/**/*.js',
                'public/assets/css/**/*.css'
            ]
        })
    

    Run npm run watch, site is served at localhost:3000, save a sass file and watch the browser refresh rather than just inject the changes.

    Reviewed by SethTompkins at 2017-07-26 17:50
  • 8. Versioning no longer Load Balancer friendly

    Hi

    Upgraded from 0.10 today to 1.2.2 due to some issues I was having on our live servers, and have realised it has created another issue, now with the versioning.

    Let's say you have 2...n servers, that all individually update their code, and run npm run production, they are all set up so they share a session state so, for the most part, it doesn't matter which server they hit.

    In the pre 1.0 versioning you might get a code update that for a short period of time creates an inconsistent state: The browser gets told by server 1 /css/app.5ee7141a759a5fb7377a.css is current, due to true Load Balancing it might try getting it from server 2 which hasn't quite finished npm run production yet. It gets a 404, no big deal, the browser requests that file next time and either manages to get it from a different server, or the other one had finished processing it.

    Post 1.0, this creates a larger issue: The browser gets told by server 1 /css/app..css?id=5ee7141a759a5fb7377a is current, if server 2 hasn't finished compiling yet, it might serve that client the old CSS code, the browser will cache this old code for days/weeks/months.

    If we throw a CDN in the mix (something that I'm planning on doing), this creates an even larger issue, because it is possible in that small window, that it caches the old code (even though cachebusting on the new ID), and will serve that to many browsers. CDN even means that any Load Balancer stickiness (for browsers) is completely off the table as well.

    It would be great to have the old versioning back (even as an option),
    I realise the query string keeps things a bit tidier, but it does mean in multi-server setups there's no guarantee that the file version being served is actually the right version - having the file existing/not existing is really the only guarantee here.

    Thanks

    Ben

    Reviewed by bbluemel at 2017-07-19 21:04
  • 9. .extract() leads to empty .css files

    • Laravel Mix Version: [email protected] (npm list --depth=0)
    • Node Version (node -v): v10.10.0
    • NPM Version (npm -v): 6.5.0
    • OS:

    Description:

    css files are empty (0 bytes), with no error, whenever a js file has been processed before.

    mix
      .js('resources/front/visitors/visitors.js', 'public/js')
      .sass('resources/front/visitors/sass/visitors.scss', 'public/css')
      .extract([....])
    

    leads to a 0 bytes css file whenever

    mix
      .js('resources/front/visitors/visitors.js', 'public/js')
      .sass('resources/front/visitors/sass/visitors.scss', 'public/css')
    

    creates the wanted css.

    Steps To Reproduce:

    Running npm run dev or npm run prod. Specifying the array of libs you want to extract (.extract([...])) or letting Mix do the guessing job (.extract()) does not change the problem.

    Output in the first case:

     DONE  Compiled successfully in 11268ms
                         Asset      Size                                         Chunks             Chunk Names
    /css/semantic-visitors.css   0 bytes                     /js/manifest, /js/visitors  [emitted]  /js/manifest, /js/visitors
             /css/visitors.css   0 bytes                     /js/manifest, /js/visitors  [emitted]  /js/manifest, /js/visitors
               /js/manifest.js  9.08 KiB                                   /js/manifest  [emitted]  /js/manifest
                 /js/vendor.js  2.14 MiB                                     /js/vendor  [emitted]  /js/vendor
               /js/visitors.js  1.28 MiB                                   /js/visitors  [emitted]  /js/visitors
    

    and in the second case:

     DONE  Compiled successfully in 11111ms
                         Asset        Size                                         Chunks             Chunk Names
    /css/semantic-visitors.css     653 KiB                                   /js/visitors  [emitted]  /js/visitors
             /css/visitors.css    14.5 KiB                                   /js/visitors  [emitted]  /js/visitors
               /js/visitors.js    2.93 MiB                                   /js/visitors  [emitted]  /js/visitors
    
    Reviewed by rderimay at 2019-01-04 09:08
  • 10. Dependencies not found error references my own files

    • Laravel Mix Version: +-- [email protected]
    • Node Version: v8.1.3
    • NPM Version: 5.2.0
    • OS: Windows 10

    npm list --depth=0 does give me an error though (even when manually installing webpack):

    `-- [email protected]
    
    npm ERR! peer dep missing: [email protected]^2.2.0, required by [email protected]
    

    Complete list:

    +-- [email protected]
    +-- [email protected]
    +-- [email protected]
    +-- [email protected]
    +-- [email protected]
    +-- [email protected]
    +-- [email protected]
    +-- [email protected]
    +-- [email protected]
    +-- [email protected]
    +-- [email protected]
    +-- [email protected]
    +-- [email protected]
    +-- [email protected]
    `-- [email protected]
    
    npm ERR! peer dep missing: [email protected]^2.2.0, required by [email protected]
    

    Description:

    Since updating laravel-mix and npm I receive the following error:

    These dependencies were not found:
    
    * C:\Projects\project-name\resources\assets\js\cms\cms.js in multi ./resources/assets/js/cms/cms.js ./resources/assets/sass/cms/cms.scss ./resources/assets/sass/website/style.scss
    * C:\Projects\project-name\resources\assets\js\website\website.js in multi ./resources/assets/js/website/website.js
    * C:\Projects\project-name\resources\assets\sass\cms\cms.scss in multi ./resources/assets/js/cms/cms.js ./resources/assets/sass/cms/cms.scss ./resources/assets/sass/website/style.scss
    * C:\Projects\project-name\resources\assets\sass\website\style.scss in multi ./resources/assets/js/cms/cms.js ./resources/assets/sass/cms/cms.scss ./resources/assets/sass/website/style.scss
    
    To install them, you can run: npm install --save C:\Projects\project-name\resources\assets\js\cms\cms.js C:\Projects\project-name\resources\assets\js\website\website.js C:\Projects\project-name\resources\assets\sass\cms\cms.scss C:\Projects\project-name\resources\assets\sass\website\style.scss
    

    So I tried reverting the update back but the error does not go away. When I empty to files to // the error still occurs. Only when removing the mix entries the error goes away.

    My webpack.mix.js file:

    const {mix} = require('laravel-mix');
    
    mix.disableNotifications();
    
    mix.options({
        processCssUrls: false
    });
    
    mix.js('resources/assets/js/cms/cms.js', 'public/build/js/cms.js')
        .js('resources/assets/js/website/website.js', 'public/build/js/website.js')
        .sass('resources/assets/sass/cms/cms.scss', 'public/build/css/cms.css')
        .sass('resources/assets/sass/website/style.scss', 'public/build/css/website.css');
    
    if (mix.inProduction()) {
        mix.version();
    }
    

    The following scripts gives me that error:

    npm run dev
    
    npm run prod
    
    npm run watch
    

    My package.json:

    {
    	"private": true,
    	"scripts": {
    		"dev": "npm run development",
    		"development": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
    		"watch": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
    		"watch-poll": "npm run watch -- --watch-poll",
    		"hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js",
    		"prod": "npm run production",
    		"production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"
    	},
    	"devDependencies": {
    		"cross-env": "^5.0.1",
    		"laravel-mix": "^1.1.1",
    		"webpack": "2.2.0"
    	},
    	"dependencies": {
    		"axios": "^0.15.2",
    		"bootstrap-sass": "^3.3.7",
    		"cropperjs": "^1.0.0-beta.2",
    		"flatpickr": "^2.3.7",
    		"jquery": "^3.1.0",
    		"jquery-mousewheel": "^3.1.13",
    		"lodash": "^4.16.2",
    		"malihu-custom-scrollbar-plugin": "^3.1.5",
    		"nouislider": "^9.2.0",
    		"owl.carousel": "^2.2.0",
    		"tinymce": "^4.6.4",
    		"vue": "^2.0.1"
    	},
    	"eslintConfig": {
    		"extends": "eslint:recommended",
    		"parserOptions": {
    			"ecmaVersion": 6,
    			"sourceType": "module"
    		},
    		"env": {
    			"browser": true,
    			"node": true
    		},
    		"globals": {
    			"_": true,
    			"axios": true
    		}
    	}
    }
    
    Reviewed by Hendriksie at 2017-07-11 11:50
  • 11. Help Requested From Windows Users

    Hey, everyone. I could use some help from Windows users. If you have the time, would you mind doing:

    laravel new example
    npm install
    npm run dev
    

    Did you get an error related to "node_modules not being an external command", or anything along those lines? If so, can you try running a variant of this command?

    node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
    

    This ends up being more complicated, because Yarn has this weird thing where it doesn't symlink bin installs to node_modules/.bin. So, if you install Mix with NPM, no problem. But if you do it through Yarn, the NPM script can't find webpack or webpack-dev-server.

    So we updated the NPM script to specify the full path to these executable, but now some Windows users are having issues, and I'm not quite sure what the root of it is.

    Any help would be appreciated! :)

    Reviewed by JeffreyWay at 2017-01-25 18:10
  • 12. Npm install not working.

    Node v16.14 Npm v8.5

    npm install laravel-mix
    npm WARN deprecated [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
    npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
    npm ERR! code E404
    npm ERR! 404 Not Found - GET https://registry.npmjs.org/@types/eslint/-/eslint-8.4.4.tgz - Not found
    npm ERR! 404
    npm ERR! 404  '@types/[email protected]://registry.npmjs.org/@types/eslint/-/eslint-8.4.4.tgz' is not in this registry.
    npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
    npm ERR! 404
    npm ERR! 404 Note that you can also install from a
    npm ERR! 404 tarball, folder, http url, or git url.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     C:\Users\info\AppData\Local\npm-cache\_logs\2022-06-30T19_52_23_005Z-debug-0.log
    
    Reviewed by brazilsunshine at 2022-06-30 19:59
  • 13. TailwindCSS: Cannot read properties of undefined (reading 'config')

    • Laravel Mix Version: 6.0.49
    • Node Version (node -v): 16.14.2
    • Yarn Version (yarn -v): 1.22.19
    • OS: Windows

    Description:

    When trying to pass a custom configuration file to Tailwind, the following error is displayed in the console: Cannot read properties of undefined (reading 'config')

    Steps To Reproduce:

    • Create a custom Tailwind configuration file (for example: tailwind-app.config.js)
    • Add the following snippet to webpack.mix.js: .postCss("resources/css/app.css", "public/css", [require("tailwindcss")("tailwind-mail.config.js")])
    Reviewed by scajal at 2022-06-29 22:05
  • 14. Dynamic imports do not get bundled, if referenced statically in another Vue component

    • Laravel Mix Version: tried it with 6.0.43 & 6.0.49
    • Node Version (node -v): v16.13.0
    • NPM Version (npm -v): 8.1.0
    • OS: MacOS Monterey 12.0.1

    Description:

    In our Vue-app, when globally using dynamic imports such as:

    Vue.component('order-progress', resolve => {
    	import(/* webpackChunkName: 'order-progress' */ './components/account/orders/OrderProgress.vue')
    		.then(component => resolve(component.default));
    });
    

    everything works just fine, provided we only reference the component globally. If however, someone happens to reference the same component statically such as import OrderProgress from '.../same-path-as-above', the dynamic module ends up not getting bundled at all. This does of course not break our application, as long as everyone remembers to check whether a component was registered dynamically, before importing it statically. However, if someone forgets it (which happened to us), it breaks, which also does not come to our attention until we build the app anew (with HMR the error does not show at first).

    If we statically import a component globally, we experience no problems at all if we later on reference the same component statically somewhere down the component tree. The problem is only to be seen with dynamic imports.

    So my question: is this the expected behavior for some reason?

    Reviewed by tomosterlund at 2022-06-27 14:26
  • 15. Fixed `babel` directory issues

    This PR fixed babel directory issues which were caused due to not setting the path if publicPath is not false and available.

    Fixed #3231 and #3106

    Type of change

    • This change requires a documentation update

    Tests

    • All are passing except tests for this feature
    • Have to update combine.js and Mix.js
    Reviewed by iamarpitpatidar at 2022-06-26 23:21
  • 16. Bump jpeg-js from 0.4.3 to 0.4.4

    Bumps jpeg-js from 0.4.3 to 0.4.4.

    Release notes

    Sourced from jpeg-js's releases.

    v0.4.4

    v0.4.4 (2022-06-07)

    • feat: add comment tag encoding (#87) (13e1ffa), closes #87
    • fix: validate sampling factors (#106) (9ccd35f), closes #106
    • fix(decoder): rethrow a more helpful error if Buffer is undefined (#93) (b58cc11), closes #93
    • chore(ci): migrate to github actions (#86) (417e8e2), closes #86
    • chore(deps): bump y18n from 4.0.0 to 4.0.3 (#98) (2c90858), closes #98
    • chore(deps): bump ws from 7.2.3 to 7.4.6 (#91) (fd73289), closes #91
    • chore(deps): bump hosted-git-info from 2.8.8 to 2.8.9 (#90) (9449a8b), closes #90
    • chore(deps): bump lodash from 4.17.15 to 4.17.21 (#89) (ffdc4a4), closes #89
    Commits
    • 9ccd35f fix: validate sampling factors (#106)
    • b58cc11 fix(decoder): rethrow a more helpful error if Buffer is undefined (#93)
    • 2c90858 chore(deps): bump y18n from 4.0.0 to 4.0.3 (#98)
    • fd73289 chore(deps): bump ws from 7.2.3 to 7.4.6 (#91)
    • 9449a8b chore(deps): bump hosted-git-info from 2.8.8 to 2.8.9 (#90)
    • ffdc4a4 chore(deps): bump lodash from 4.17.15 to 4.17.21 (#89)
    • 13e1ffa feat: add comment tag encoding (#87)
    • 417e8e2 chore(ci): migrate to github actions (#86)
    • See full diff in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    Reviewed by dependabot[bot] at 2022-06-17 03:35
The power of webpack, distilled for the rest of us.
The power of webpack, distilled for the rest of us.

Introduction Laravel Mix provides a clean, fluent API for defining basic webpack build steps for your applications. Mix supports several common CSS an

Jul 1, 2022
The power of webpack, distilled for the rest of us.
The power of webpack, distilled for the rest of us.

Introduction Laravel Mix provides a clean, fluent API for defining basic webpack build steps for your applications. Mix supports several common CSS an

Jul 1, 2022
A REST API that should power the Agile Monkeys CRM Service

This is a simple REST API that purposes to power the Agile Monkeys CRM service

Jul 31, 2021
A simple but powerful API for processing & compiling assets built around Webpack

Webpack Encore: A Simple & Powerful Webpack API Webpack Encore is a simpler way to integrate Webpack into your application. It wraps Webpack, giving y

Jun 24, 2022
Manifest is a ProcessWire module that bridges between Twig and Webpack.

Manifest is a ProcessWire module that bridges between Twig and Webpack.

Jul 26, 2021
A full-featured Webpack + vue-loader setup with hot reload, linting, testing & css extraction.

#Vue-Cli Template for Larvel + Webpack + Hotreload (HMR) I had a really tough time getting my workflow rocking between Laravel and VueJS projects. I f

Sep 11, 2020
Laravel React Webpack Starter Kit
 Laravel React Webpack Starter Kit

About Laravel Laravel React Webpack Starter Kit This starter kit is designed to get you up and running with with react.js with Laravel, built on top o

Sep 4, 2020
Simple handler system used to power clients and servers in PHP (this project is no longer used in Guzzle 6+)

RingPHP Provides a simple API and specification that abstracts away the details of HTTP into a single PHP function. RingPHP be used to power HTTP clie

Jun 29, 2022
A Laravel Fractal package for building API responses, giving you the power of Fractal with Laravel's elegancy.
A Laravel Fractal package for building API responses, giving you the power of Fractal with Laravel's elegancy.

Laravel Responder is a package for building API responses, integrating Fractal into Laravel and Lumen. It can transform your data using transformers,

Jun 22, 2022
HLedger is cross-platform accounting software for both power users and folks new to accounting
HLedger is cross-platform accounting software for both power users and folks new to accounting

HLedger Plain Text Accounting on Nextcloud HLedger is cross-platform accounting software for both power users and folks new to accounting. It's good f

Jan 20, 2022
The 1Password Connect PHP SDK provides your PHP applications access to the 1Password Connect API hosted on your infrastructure and leverage the power of 1Password Secrets Automation

1Password Connect PHP SDK The 1Password Connect PHP SDK provides your PHP applications access to the 1Password Connect API hosted on your infrastructu

Jun 22, 2022
Bringing the power of GraphQL to BuddyPress.

WPGraphQL BuddyPress Bringing the power of GraphQL to BuddyPress. Docs (soon) • Join Slack System Requirements PHP >= 7.1 WP >= 4.9 WPGraphQL >= lates

Jun 6, 2022
Donation Platform for WooCommerce unleashes the power of WooCommerce for your online fundraising, crowdfunding & crowdsponsoring

=== Donation Platform for WooCommerce === Contributors: flinnn Tags: donation, donations, crowdfunding, fundraising, woocommerce Requires at least: 5.

May 20, 2022
An attempt at a usable, generic VPS panel for providers and power users.

An attempt at a usable, generic VPS panel for providers and power users. Key goals are to be clean, easy to use, and support Proxmox as well as other providers (Libvirt via Go API, etc) using one simple interface.

Nov 5, 2021
GraphQL implementation with power of Laravel

Laravel GraphQL Use Facebook GraphQL with Laravel 5.2 >=. It is based on the PHP implementation here. You can find more information about GraphQL in t

Mar 9, 2022
A simple library to increase the power of your environment variables.
A simple library to increase the power of your environment variables.

Environment A simple library (with all methods covered by php unit tests) to increase the power of your environment variables, contribute with this pr

Feb 8, 2022
Unleash the expressive power of the natural language in your Laravel application.

jrmajor/laravel-fluent Unleash the expressive power of the natural language in your Laravel application. Read the Fluent Syntax Guide in order to lear

Jan 6, 2022
This project demonstrates the power of soketi's WebSocket functionality in Laravel.

Laravel + soketi = <3 This project demonstrates the power of soketi's WebSocket functionality in Laravel. Installing the project The server requires:

Jun 9, 2022
Scout Extended: The Full Power of Algolia in Laravel
Scout Extended: The Full Power of Algolia in Laravel

Documentation • Community Forum • Stack Overflow • Report a bug • FAQ • Support To dig right in, visit the Scout Extended documentation. Scout Extende

Jun 10, 2022
Give the power of Twig to Laravel

Allows you to use Twig seamlessly in Laravel. Requirements TwigBridge >= 0.13 supports Twig 3. If you need Twig 1/2 support, use the 0.12 versions. In

Jan 30, 2022