5t3ph / 5t3ph/eleventy-plugin-lightningcss
ERRORS: Having trouble rendering/compiling css template + Browser queries must be an array or string. Got object.
- Dominant language
- JavaScript
- Stars
- 45
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Enabling the plugin via `eleventyConfig.addPlugin(lightningCSS);` in `.eleventy.js` produces the following error:
````
[11ty] 1. Having trouble rendering css template ./src/Box.css (via TemplateContentRenderError)
[11ty] 2. Having trouble compiling template ./src/Box.css (via TemplateContentCompileError)
[11ty] 3. Browser queries must be an array or string. Got object. (via BrowserslistError)
[11ty]
[11ty] Original error stack trace: BrowserslistError: Browser queries must be an array or string. Got object.
[11ty] at checkQueries (/projects/eleventy/node_modules/browserslist/index.js:387:11)
[11ty] at browserslist (/projects/eleventy/node_modules/browserslist/index.js:398:3)
[11ty] at Object.compile (/projects/eleventy/node_modules/@11tyrocks/eleventy-plugin-lightningcss/.eleventy.js:100:43)
[11ty] at CustomEngine.compile (/projects/eleventy/node_modules/@11ty/eleventy/src/Engines/Custom.js:201:7)
[11ty] Wrote 0 files in 0.01 seconds (v2.0.1)
````
If I rename or delete `Box.css` I get the same error, but for the next CSS file in my project (`/src/Center.css`).
I'm configuring `browserslist` in my `package.json`, but I've also tried the default method and produced the same error.
[Contents of `.eleventy.js`](https://github.com/5t3ph/eleventy-plugin-lightningcss/files/13572887/eleventy.txt)
Contributor guide
No contributing guide indexed for this repository
Research direction
The error originates in the plugin's compile function at .eleventy.js line 100, where browserslist receives an object instead of an array/string. Start by examining the plugin's source to see how the browserslist query is constructed. Check the project's package.json for browserslist configuration and ensure it's valid. Run the plugin in a minimal Eleventy project to reproduce the issue and trace the data flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 40/100