🐛 What's broken?
In tests/smoke.test.js, multiple CSS component files are manually concatenated into a single css string using the + operator (lines 31-32). If any of the source CSS files end with a comment (e.g., /* end of component */) or lack a trailing newline, they will merge directly into the first line of the next file. This can silently comment out rules or create invalid syntax that breaks the JSDOM CSS parser.
📋 Steps to Reproduce
- Navigate to the repository file:
tests/smoke.test.js.
- Inspect the
beforeAll block around lines 31-32.
- Observe the direct string addition of all CSS variables without line breaks.
✅ Expected Behavior
The CSS file contents should be grouped into an array and joined with a newline character (\n) to guarantee safe parsing between file boundaries.
❌ Actual Behavior
Files are squashed together directly, risking syntax errors if source file formatting changes.
🔗 Reproduction
Current Structure:
css = variables + base + animations + utilities + buttons + cards + chip + footer + masonry + navbar + scrollProgress + sidebar + tabs + badges + loaders + tooltips + modals;
🐛 What's broken?
In
tests/smoke.test.js, multiple CSS component files are manually concatenated into a singlecssstring using the+operator (lines 31-32). If any of the source CSS files end with a comment (e.g.,/* end of component */) or lack a trailing newline, they will merge directly into the first line of the next file. This can silently comment out rules or create invalid syntax that breaks the JSDOM CSS parser.📋 Steps to Reproduce
tests/smoke.test.js.beforeAllblock around lines 31-32.✅ Expected Behavior
The CSS file contents should be grouped into an array and joined with a newline character (
\n) to guarantee safe parsing between file boundaries.❌ Actual Behavior
Files are squashed together directly, risking syntax errors if source file formatting changes.
🔗 Reproduction
Current Structure: