4 ms·
Let me disagree. This is HTML-first because you can always grab the compiled CSS and optionally, compiled JS and reference it in your plain HTML file via <link
by sveltecult 2y ago
Let me disagree. This is HTML-first because you can always grab the compiled CSS and optionally, compiled JS and reference it in your plain HTML file via <link rel="" href=""> and it will work just fine.
The TypeScript and Tailwind insanities are just there for easier development and my convenience. ;)
Maybe soon, someone will publish the compiled CSS. IDK
- lelanthran 2y ago> This is HTML-first because you can always grab the compiled CSS and optionally, compiled JS and reference it in your plain HTML file via <link rel="" href=""> and it will work just fine. But this is true for almost every web thing, and every web framework - you can just grab the final outputs and stick it into your web page. So either your thing is "HTML-first", but so is everything else, or your thing is not "HTML-first", and some other things are. > Maybe soon, someone will publish the compiled CSS. So, until then, not only is this not HTML-first, it's not HTML at all. To me (and maybe others), there's a difference between web development and Node/npm. They are not one and the same.