Experimental webpack loader for colocated modules. Very much inspired by .vue
and svelte components, but (almost) completely unopinionated about your blocks and their behaviour.
By default, the content of all non-script
blocks is available as strings to the script
block, via camel-cased globals:
<!-- myModule.html -->
<style>
.red {
color: red;
border-color: red;
}
</style>
<template><p>hello!</p></template>
<my-crazy-block-name>something handy</my-crazy-block-name>
<script>
console.log(style); // '.red { color: red; border-color: red; }'
console.log(template); // '<p>hello!</p>'
console.log(myCrazyBlockName); // 'something handy'
</script>
However, blocks can also be processed by webpack loaders, as if they were individual files:
// webpack.config.js
module.exports = {
...
module: {
rules: [
{
test: /\.html$/,
use: {
loader: "colocate-loader",
options: {
rules: [
{
test: /^style$/,
loader: "css-loader" // `style` is now a css-loader object
},
{
test: /^script$/,
use: [{ loader: "babel-loader" }] // the script block is now es5 etc.
},
{
test: "my-crazy-block-name",
loader: "my-crazy-block-name-loader" // who knows...
}
]
}
}
}
]
}
};
Non-script
blocks are injected as imports into the script
block, once it has passed through its loaders. So given the config above, myModule.html
would be transformed into the following:
import style from 'css-loader!colocate-loader?block=style!myModule.html';
import template from 'colocate-loader?block=template!myModule.html';
import myCrazyBlockName from 'my-crazy-block-name-loader!colocate-loader?block=my-crazy-block-name!myModule.html';
console.log(style);
console.log(template);
console.log(myCrazyBlockName);