6 ms·

It'll likely embed Node I'm afraid — the vast majority of Tailwind is written in JS so we'd have to rewrite all of that in Rust just for the standalone CLI, and

It'll likely embed Node I'm afraid — the vast majority of Tailwind is written in JS so we'd have to rewrite all of that in Rust just for the standalone CLI, and migrating the entire project to Rust is impractical because we'd have no JS plugin story like we do now.

acaloiar 3y ago
Bummer, but thanks for resetting my expectations :)
- neilyio 3y ago
  I'm feeling a similar disappointment here, although I'm sure this was carefully considered by the Tailwind team. I've been working with a fully Rust-based web stack, and it's been such a joy. Tailwind compilation causes me to still deal with Node. I'd love to see that go away.
ajayvk 3y ago
The current standalone tailwind CLI does not support external plugins like DaisyUI. It would be great if external plugins could be supported in the next CLI version, it will reduce the need to use npm for some projects.
- adamwathan 3y ago
  Don't you need to use npm to install DaisyUI though? If you have to install third party plugins using node already to me the solution is to use our actual node CLI instead of the standalone one.
  - ajayvk 3y ago
    The way I was thinking this would work is that the standalone CLI could be configured to pick up plugins from a specified location. That way as long as the plugins are setup locally in the required format, the standalone CLI would be able to load them. The setup process need not require npm. There is a sibling comment which mentioned a project which is trying to bundle DaisyUI specifically with the standalone CLI. That would solve my use case but will not be a generic solution for other plugins.
- acaloiar 3y ago
  This is handy for that specific need: https://github.com/dobicinaitis/tailwind-cli-extra https://github.com/dobicinaitis/tailwind-cli-extra But I strongly agree.
  - ajayvk 3y ago
    Thanks, that looks like what I was looking for, did not find that when I looked few months back. I tried it now and had some issues with SIP check on macOS, started a discussion in the repo.

acaloiar 3y ago

Bummer, but thanks for resetting my expectations :)

neilyio 3y ago
I'm feeling a similar disappointment here, although I'm sure this was carefully considered by the Tailwind team. I've been working with a fully Rust-based web stack, and it's been such a joy. Tailwind compilation causes me to still deal with Node. I'd love to see that go away.

ajayvk 3y ago

The current standalone tailwind CLI does not support external plugins like DaisyUI. It would be great if external plugins could be supported in the next CLI version, it will reduce the need to use npm for some projects.

adamwathan 3y ago
Don't you need to use npm to install DaisyUI though? If you have to install third party plugins using node already to me the solution is to use our actual node CLI instead of the standalone one.
- ajayvk 3y ago
  The way I was thinking this would work is that the standalone CLI could be configured to pick up plugins from a specified location. That way as long as the plugins are setup locally in the required format, the standalone CLI would be able to load them. The setup process need not require npm. There is a sibling comment which mentioned a project which is trying to bundle DaisyUI specifically with the standalone CLI. That would solve my use case but will not be a generic solution for other plugins.
acaloiar 3y ago
This is handy for that specific need: https://github.com/dobicinaitis/tailwind-cli-extra https://github.com/dobicinaitis/tailwind-cli-extra But I strongly agree.
- ajayvk 3y ago
  Thanks, that looks like what I was looking for, did not find that when I looked few months back. I tried it now and had some issues with SIP check on macOS, started a discussion in the repo.