Troubleshooting

Common issues and solutions when using SpiraCSS tools.

Comment Links path resolution fails

• Ensure there is no @ in the aliasRoots keys
• Ensure the paths are relative to the project root
• Save spiracss.config.js and reload the workspace

Stylelint rules are not applied

• Ensure the plugin is loaded in your Stylelint config
• Ensure spiracss.config.js exists in the cwd where Stylelint is run (if running from a subdirectory, use createRulesAsync(path) to specify the config path explicitly)

Generated SCSS structure looks wrong

• Ensure the generator.globalScssModule path is correct
• Ensure HTML class names follow the naming rules