feat(windicss): add windicss ui setup

[Olyno]

Description

Hi 👋🏻
Here is a pull request to implement the WindiCSS UI library. It is a great alternative to Tailwind, with fewer configurations, and more utilities.

Currently, this pull request should be tested. Due to a conflict with local packages from the Framework project, I wasn't able to test what I've done so far.

[netlify]

✅ Deploy Preview for redwoodjs-docs canceled.

Name	Link
🔨 Latest commit	d8eba11
🔍 Latest deploy log	https://app.netlify.com/sites/redwoodjs-docs/deploys/625fa8c83acc6b000843b003

[jtoar]

Hey @Olyno I've used windicss once and it was a great experience. I tested this out locally and left a few comments. You can also lint fix to get some of the GitHub warnings to go away.

Due to a conflict with local packages from the Framework project, I wasn't able to test what I've done so far

Mind expanding on this? I was able to get things hooked locally up using yarn rwfw. And as long as you run the command with --no-isntall, node_modules won't be reset (and then you can install after the setup command). Did you have a hard time with the contributing docs? You can also try Gitpod, it's often just an easier experience.

[Olyno]

Mind expanding on this? I was able to get things hooked locally up using yarn rwfw. And as long as you run the command with --no-isntall, node_modules won't be reset (and then you can install after the setup command). Did you have a hard time with the contributing docs? You can also try Gitpod, it's often just an easier experience.

When I tried it locally, I encountered some problems. For example, when running the command "yarn rwfw", I got an error that it was not possible to find the workspace "web":

I also got an error at one point with the dependencies:

I honestly don't know how to explain these issues. I didn't try Gitpod, but it can be a good option if it works better. I would have highlighted it in the documentation in these cases.

There's a thread on the Discord with probably more information if you're curious to find out what's wrong).

Also, I think that the "Test the CLI" part should be before the "Test the Framework" part because it seems that we don't need sync, which would allow us to go straight to the concrete.

[thedavidprice]

@jtoar re: local dev topic — we have two next steps to address now that we're beyond 1.0:

1. given that the yarn dev command is hit or miss, we need to update documentation to clarify (i.e. experimental/incomplete) or remove entirely
2. we still need to resolve yarn rwfw project:copy issues (due to yarn 3), which may also be affecting rwfw project:sync. Behavior so far has been that project:copy works once but on subsequent uses it break node_modules

[jtoar]

@Olyno here's another round of reviews. I think it's good to go after all these are addressed.

[jtoar]

Thanks @Olyno, this looks great. Let's get this one merged

[thedavidprice]

Thanks for the work here @Olyno And most of all for taking me up on the invitation — well done 🚀

@jtoar can you make sure Docs for this are updated accordingly?

@Tobbe is there anything that needs to be connected between this PR and the work in #4900

?

[Tobbe]

@Tobbe is there anything that needs to be connected between this PR and the work in #4900

No, it's all good. They're both touching App.{js,tsx} but 1) you most likely won't have both at the same time, and 2) with all the advanced merge stuff going on in #4900 I'm sure it can handle it anyway 🙂