Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Be explicit about which Sass compilers we support
See original GitHub issueWhat
Document which Sass compilers we expect GOV.UK Frontend to correctly compile with, including minimum versions.
Why
By being explicit about which Sass compilers we support we enable our users to make informed decisions about their build pipeline.
This will also help us when making changes, as we’ll be able to make informed decisions about which features we can safely use. This is especially important given the current landscape and the different features supported by the different compilers (see http://sass-compatibility.github.io for details)
Questions / prompts
- If we drop support for a compiler, or change the minimum version of a compiler (e.g. so that we can start relying on a newer Sass feature) does that count as a breaking change?
- Where would users expect to find this information?
- Is there a way of defining this in the
package.jsonfile such that any unmet dependencies are flagged at install time? Or otherwise detecting / flagging this to the user?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi @36degrees - can you involve me when you kick this one off please? I should have time to write this - and I’d like to be involved in the discussions about where it would sit.
https://github.com/nickcolley/govuk-frontend-sass-compilers