Extending Mix
The very component-based system that Mix uses behind the scenes to build its API is also accessible to you - whether to extend Mix for your own personal projects, or to distribute as a package to the rest of the world.
Build a Simple Plugin
// webpack.mix.js;
let mix = require('laravel-mix');
mix.extend('foo', function(webpackConfig, ...args) {
// The webpack configuration object.
console.log(webpackConfig);
// All arguments passed to mix.foo();
console.log(args); // ['some-foo']
});
// Trigger your new plugin.
mix.foo('some-value');
In the example above, notice how mix.extend()
accepts two parameters:
- The name that should be used when triggering your component.
- A callback function or class that registers and organizes the necessary webpack logic. Behind the scenes, Mix will call this function after the underlying webpack configuration object has been constructed. This will give you a chance to insert or override any necessary webpack-specific settings.
Component Classes
While a simple callback function may be useful for quick extensions, in most scenarios, you'll likely want to build a full component class, like so:
// foo.js
let mix = require('laravel-mix');
class FooPlugin {
register(val) {
console.log('mix.foo() was called with ' + val);
}
webpackConfig(config) {
//
}
}
mix.extend('foo', new FooPlugin());
// webpack.mix.js
let mix = require('laravel-mix');
require('./foo');
mix.foo('bar'); // "mix.foo() was called with bar"
When preparing Mix extensions, you'll typically need to trigger a handful of instructions. For instance:
- Install these dependencies.
- Add this rule/loader to the webpack config.
- Include this webpack plugin.
- Override this part of the webpack configuration entirely.
- Add this config to Babel.
- etc.
Any of these operations are a cinch with Mix's component system.
The Component Interface
- name: What should be used as the method name, when calling the component. (Defaults to camelCased version of the component class name.)
- dependencies: List all npm dependencies that should be installed by Mix.
- register: When your component is called, all user parameters will instantly be passed to this method.
- boot: Boot the component. This method is triggered after the user's webpack.mix.js file has fully loaded.
- webpackEntry: Append to Mix's webpack entry object.
- webpackRules: Rules to be merged with the underlying webpack rules.
- webpackPlugins: Plugins to be merged with the underlying webpack plugins array.
- webpackConfig: Override the underlying webpack configuration.
- babelConfig: Additional Babel configuration that should be merged with Mix's defaults.
Below is a dummy component that will give you a better idea of how you'll construct your own components. For more examples, refer to the very components that Mix uses behind the scenes.
class Example {
/**
* The optional name to be used when called by Mix.
* Defaults to the class name, lowercased.
*
* Ex: mix.example();
*
* @return {String|Array}
*/
name() {
// Example:
// return 'example';
// return ['example', 'alias'];
}
/**
* All npm dependencies that should be installed by Mix.
*
* @return {Array}
*/
dependencies() {
// Example:
// return ['typeScript', 'ts'];
}
/**
* Register the component.
*
* When your component is called, all user parameters
* will be passed to this method.
*
* Ex: register(src, output) {}
* Ex: mix.yourPlugin('src/path', 'output/path');
*
* @param {*} ...params
* @return {void}
*
*/
register() {
// Example:
// this.config = { proxy: arg };
}
/**
* Boot the component. This method is triggered after the
* user's webpack.mix.js file has processed.
*/
boot() {
// Example:
// if (Config.options.foo) {}
}
/**
* Append to the underlying webpack entry object.
*
* @param {Entry} entry
* @return {void}
*/
webpackEntry(entry) {
// Example:
// entry.add('foo', 'bar');
}
/**
* Rules to be merged with the underlying webpack rules.
*
* @return {Array|Object}
*/
webpackRules() {
// Example:
// return {
// test: /\.less$/,
// loaders: ['...']
// });
}
/*
* Plugins to be merged with the underlying webpack plugins array.
*
* @return {Array|Object}
*/
webpackPlugins() {
// Example:
// return new webpack.ProvidePlugin(this.aliases);
}
/**
* Override the underlying webpack configuration.
*
* @param {Object} webpackConfig
* @return {void}
*/
webpackConfig(webpackConfig) {
// Example:
// webpackConfig.resolve.extensions.push('.ts', '.tsx');
}
/**
* Babel config to be merged with Mix's defaults.
*
* @return {Object}
*/
babelConfig() {
// Example:
// return { presets: ['@babel/preset-react'] };
}
}
Note that each of the methods in the example above are optional. In certain situations, your component may only need to add a webpack loader and/or tweak the Babel configuration that Mix uses. No problem. Omit the rest of the interface.
class Example {
webpackRules() {
return {
test: /\.test$/,
loaders: []
};
}
}
Now, when Mix constructs the underlying webpack configuration, your .test
rule will be included as part of the generated webpackConfig.module.rules
array.
Plugin Usage
Once you've constructed or installed your desired component, simply require it from your webpack.mix.js
file,
and you're all set to go.
// example.js
let mix = require('laravel-mix');
class Example {
webpackRules() {
return {
test: /\.test$/,
loaders: []
};
}
}
mix.extend('example', new Example());
// webpack.mix.js
let mix = require('laravel-mix');
require('./example');
mix.js('src', 'output')
.example();