You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've run into this need a couple of times now, and I thought that this gem might be the right home for a utility like this. Basically, I am needing a way to call the tailwindcss binary to have it generate styles for me on demand. This gem is already solving the problem of getting the binary in place on the system, but it doesn't expose any way to access it externally.
At the most basic, something like this would be really helpful:
It could also possibly expose an API for calling the binary, but there are many different ways to do that, and there may not be a reasonable one-size-fits-all approach, so it may be best to just leave it at the path.
This could be accomplished in a different gem, but more than likely any user of that gem would also be using this gem, and it seems non-ideal to download the binary twice. Would the maintainers of this gem be open to exposing the path of the binary like this?
The text was updated successfully, but these errors were encountered:
I've run into this need a couple of times now, and I thought that this gem might be the right home for a utility like this. Basically, I am needing a way to call the
tailwindcss
binary to have it generate styles for me on demand. This gem is already solving the problem of getting the binary in place on the system, but it doesn't expose any way to access it externally.At the most basic, something like this would be really helpful:
It could also possibly expose an API for calling the binary, but there are many different ways to do that, and there may not be a reasonable one-size-fits-all approach, so it may be best to just leave it at the path.
This could be accomplished in a different gem, but more than likely any user of that gem would also be using this gem, and it seems non-ideal to download the binary twice. Would the maintainers of this gem be open to exposing the path of the binary like this?
The text was updated successfully, but these errors were encountered: