5t3ph / 5t3ph/eleventy-plugin-sass-lightningcss
Autoprefixing not triggering
- Lenguaje dominante
- JavaScript
- Estrellas
- 42
- Forks
- 4
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
I may have my .eleventy.js file misconfigured (although it is converting the Sass files to CSS), but how do I get it to autoprefix? I'm seeing some bizarre effects when I go from one browser and operating system to another that I suspect may have something to do with it not auto-prefixing anything.
```
const striptags = require("striptags");
const he = require('he');
const prettier = require('./src/transforms/prettier.js');
const sass = require("sass");
const browserslist = require("browserslist");
const { transform, browserslistToTargets } = require("lightningcss");
const eleventySass = require("@11tyrocks/eleventy-plugin-sass-lightningcss");
// Call this once per build.
let targets = browserslistToTargets(browserslist('>= 0.25%'));
// Use `targets` for each file you transform.
module.exports = function (eleventyConfig) {
eleventyConfig.setServerOptions({
showAllHosts: true,
})
// eleventyConfig.addPassthroughCopy('src/assets/js');
// eleventyConfig.addPassthroughCopy({ 'src/assets/css': 'css/' });
eleventyConfig.addPassthroughCopy({ 'src/fonts': 'fonts/' });
eleventyConfig.addPassthroughCopy({ 'src/img': 'img/' });
eleventyConfig.addPlugin(eleventySass);
eleventyConfig.setQuietMode(true);
eleventyConfig.addFilter("dateOnly", function (dateVal, locale = "en-US") {
var theDate = new Date(dateVal);
const options = { year: 'numeric', month: 'short', day: 'numeric', timeZone: 'UTC' };
return theDate.toLocaleDateString(locale, options);
});
eleventyConfig.addFilter("longDate", function (dateVal, locale = "en-US") {
var theDate = new Date(dateVal);
const options = { year: 'numeric', month: 'long', day: 'numeric', timeZone: 'UTC' };
return theDate.toLocaleDateString(locale, options);
});
eleventyConfig.addFilter("apaDate", function (dateVal, locale = "en-US") {
const months = ['January', 'February', 'March', 'April',
'May', 'June', 'July', 'August',
'September', 'October', 'November', 'December'];
var year = dateVal.getUTCFullYear();
var month = dateVal.getUTCMonth();
var day = dateVal.getDate() + 1;
var retDate = `${year}, ${months[month]} ${day}`;
return retDate;
});
eleventyConfig.addFilter("stripHTMLTags", function (data) {
return striptags(data);
});
eleventyConfig.addFilter("decodeHTML", function (data) {
return he.decode(data);
});
eleventyConfig.addShortcode("folderDepth", function (depth) {
var depthPrefix = "";
if (depth > 0) {
for (var i = 0; i < depth; i++) {
depthPrefix = depthPrefix + "../"
}
}
return depthPrefix;
});
eleventyConfig.addTransform("prettier", prettier);
return {
dir: {
input: 'src',
output: 'build',
data: '_data',
includes: 'partials'
},
templateFormats: ["md", "njk", "11ty.js"],
markdownTemplateEngine: "njk"
}
}
```
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
The issue is about autoprefixing not working in an Eleventy plugin that uses LightningCSS. Start by examining the plugin's source code, particularly how it processes Sass and passes options to LightningCSS. Check the configuration in the provided .eleventy.js to see if targets are correctly passed. Look at the plugin's documentation or examples to verify the expected setup. Test the build output to confirm if vendor prefixes are missing.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- javascript, sass
- Área
- build-system, tooling
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 55/100