3 ms·
They mention in the post this has issues because browsers don’t have a build step in the same way Sass has. What’s your solution for that?
by blowski 4y ago
They mention in the post this has issues because browsers don’t have a build step in the same way Sass has. What’s your solution for that?
- JoBrad 4y agoSupport look ahead to some limit, then fail that css resource, with an error message that is more verbose in the dev console.
- blowski 4y agoSounds like a good idea. Are you able to suggest it to them?
- FractalHQ 4y agoI like this idea. Could even bake a warning into VSCode.
- jakelazaroff 4y agoOne of the goals for the web in general is to not impose the burden for that kind of strictness onto users. It's why we reversed course away from XHTML, which would refuse to render a page if the markup was incorrect. Put another way: inconveniencing developers is preferable to inconveniencing users.