style-loader
style-loader copied to clipboard
webpack-contrib
Add ID's to <style> tags
Why ?
I have many components. And I can not use 'ExtractTextPlugin' for special reasons.
I would like to distinguish which component and the version number to use.
How ?
I found the attrs
require('style-loader?{attrs:{id: "style-tag-id"}}!style.css');
But the information of the component can only be obtained in the compilation of each file.
So
I would like to make this change in 'style-loader/index.js'.
var findPackage = require('find-package');
...
if(this.cacheable) this.cacheable();
var query = loaderUtils.getOptions(this) || {};
var pkg = findPackage(this.resourcePath) || {};
if (query.attrs) {
Object.keys(query.attrs).forEach(function(key) {
query.attrs[key] = query.attrs[key].replace(/\[name\]/ig, pkg.name).replace(/\[version\]/ig, pkg.version);
});
}
return ...
Then
I use it like this
require('style-loader?{attrs:{component: "[name]@[version]"}}!style.css');
The result:
If it is acceptable ? Or is there any other solution?
Fork: https://github.com/alex-mm/style-loader/blob/master/index.js#L7-L17
@alex-mm What's the particular usecase for this in terms of development ? 😛
@michael-ciniawsky
It is mainly to help developers identify which components and versions.
When the dependent components are many, there are some common dependencies, especially when the dependent version is different, there will be style coverage problems, it is difficult to find which component is wrong version, there will also be repeated insert the situation, you are It is hard to see which component is repeated.
By adding the information on the 'attr', you can clearly find out the problem.
By making the private package, we've done it, it's really useful.
I would appreciate it too.
It is kind of frustrating to be able to add only "static values" to the attributes of the injected <style> elements...
We could maybe include the filename as attribute, but I'm still not really convinced by the idea. If this is really wanted someone feel free/please open a PR for further discussion
Really need this feature, like webpackChunkName, so we can distinguish source of styles.
I'm using this:
options: {
attrs: { title: 'less' }
}
It renders, however for some strange reason the style is not applied to the page...
Don't use:
options: {
attrs: { title: 'less' } // title specifies alternative style sheet sets
}
But maybe:
options: {
attrs: { data-debug: 'less' }
}
?
What if the attrs option accepted webpack placeholders via interpolateName from loader-utils?
options: {
attrs: { data-source: '[path]_[name]' }
}
Simple temporary solution without modily the lib（version 0.23.1）：
- ./build/loader.js
const path = require('path')
const loader = require('style-loader')
module.exports = function () {
}
module.exports.pitch = function (request) {
const result = loader.pitch.call(this, request)
const index = result.indexOf('options.transform = transform\n')
if (index <= -1) return result
const insertIndex = index - 1
// eslint-disable-next-line prefer-destructuring
const resourcePath = this.resourcePath
const relativePath = path.relative(path.resolve(__dirname, '..'), resourcePath)
const insertAttr = `
if (typeof options.attrs !== 'object') {
options.attrs = {}
}
options.attrs["source-path"] = '${relativePath}' // do anything you want
`
return result.slice(0, insertIndex) + insertAttr + result.slice(insertIndex)
}
- webpack config
{
test: /\.css$/,
use: [
'./build/style-loader',
'css-loader'
]
}
The loader output code will be like:
var options = {"attrs":{"name":"aa"},"hmr":true}
if (typeof options.attrs !== 'object') {
options.attrs = {}
}
options.attrs["source-path"] = 'src/components/color-picker.less'
options.transform = transform
options.insertInto = undefined;
The element in header:
any news regards webpack placeholders? I'm tryinig to insert the file name as a source attribute and [name] is being ignored...
I could really use this in runtime for caching. I have multiple apps bundling the same ui library (not externalised for a reason), resulting in the insertion of the same CSS and the only seemingly possible way to avoid that, is by calculating a content hash in build-time and then pass it to the style tag with an attribute data-hash (I currently calculate the hash in runtime, which is very costly, can take up to few seconds). WDYT? is there any other way to accomplish this?
