At least in production with config.assets.compile = false set the tailwind build should be skipped. In any case, @Bramjetten mentioned that this step could be skipped completely, since Spina ships with a standard tailwind build, and the additional tailwind build is only necessary when using additional plugins / classes.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
We had already talked about this once in the Dicord, so here is only to track progress. At the moment a tailwind build is triggered in the Spina Initializer, no matter if in production with pre-compiled assets or in development. https://github.com/SpinaCMS/Spina/blob/0525adb0d20a8980ea5fbf48fd23b4e8ea7d6f01/lib/generators/spina/install_generator.rb#L88
At least in production with
config.assets.compile = false
set the tailwind build should be skipped. In any case, @Bramjetten mentioned that this step could be skipped completely, since Spina ships with a standard tailwind build, and the additional tailwind build is only necessary when using additional plugins / classes.