Setup JS toolchain for Tailwind and DaisyUI

[anirudhprabhakaran3]

Description

Setup JS toolchain for Tailwind and DaisyUI.

Fixes # (issue)

Dependencies

List any dependencies that are required for this change.

Type of Change

What types of changes does your code introduce?
Put an x in the boxes that apply

• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration. (for bug fix / breaking change)
Put an x in the boxes that apply

• Test A
• Test B

---

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[render]

Your Render PR Server URL is https://corpus-dev-pr-69.onrender.com.

Follow its progress at https://dashboard.render.com/web/srv-cm4nc0ud3nmc73chhr50.

[livecycle]

ieee-nitk

Your Livecycle playground is ready 🎉.

🔃 _Updating from 9430415 ➡️ 3fceac7 (view log)

Invite team members and start collaborating 💪

Members already invited

• Nishant Nayak
• Anirudh Prabhakaran

Click here to invite the rest of your team.

[nishant-nayak]

Is this something we want to add to dev environments? I definitely see the benefit in adding this toolchain for production releases, but unless there's a way to "hot reload" the Tailwind CSS definitions each time a change is made to frontend code I don't think we should add this to the development toolchain.

[anirudhprabhakaran3]

Aah yes, there is. In the README instructions given, instead of using --minify we just have to use --watch and it will automatically reload everything.

[nishant-nayak]

Update the README, I think the change itself works as expected. Nice addition!

[nishant-nayak]

LGTM!