Users might not realise they need to still actually <link> to their built CSS file after adding tailwind (see #30). I'd like to at least notify the user that they need to update their index.html to include the css file that will be generated in ./priv/static/app.css.
As a stretch, we could prompt the user the very first time they run lustre/dev start and we detected a tailwind.config.js and ask if they want dev tools to generate tailwind styles. This would close #25. For the prompt we could use this library.
Similarly we could ask the user when we first download tailwind if they want us to update their index.html (using the lib linked above). We could do a simple regex to find the first <link> tag and insert one before it (or the first <script> tag if no links are present).
Users might not realise they need to still actually
<link>to their built CSS file after adding tailwind (see #30). I'd like to at least notify the user that they need to update theirindex.htmlto include the css file that will be generated in./priv/static/app.css.As a stretch, we could prompt the user the very first time they run
lustre/dev startand we detected atailwind.config.jsand ask if they want dev tools to generate tailwind styles. This would close #25. For the prompt we could use this library.Similarly we could ask the user when we first download tailwind if they want us to update their
index.html(using the lib linked above). We could do a simple regex to find the first<link>tag and insert one before it (or the first<script>tag if no links are present).