With this enhancement, users can now specify multiple entrypoints by providing an array of file paths. When building, the entrypoint name should be passed to the command. If omitted, it defaults to the first entrypoint specified in the configuration.
This change enables the following behavior:
bin/console tailwind:build assets/styles/custom.css will build the provided CSS file.
bin/console tailwind:build will build assets/styles/index.css.
Additionally, the default tailwind.built.css file is no longer generated. Instead, each entrypoint is compiled to a file named based on the original entrypoint name. For example, index.built.css for index.css and custom.built.css for custom.css.
For BC compatibility, the input_css still accepts a string value and requires no changes from the developer
Feedback and improvement ideas are welcomed. Thank you!
This PR proposes a fix for issues #45 and #46, addressing the need to pass multiple entrypoints as an array to the tailwind builder.
With this enhancement, users can now specify multiple entrypoints by providing an array of file paths. When building, the entrypoint name should be passed to the command. If omitted, it defaults to the first entrypoint specified in the configuration.
This change enables the following behavior:
bin/console tailwind:build assets/styles/custom.css
will build the provided CSS file.bin/console tailwind:build
will buildassets/styles/index.css
.Additionally, the default
tailwind.built.css
file is no longer generated. Instead, each entrypoint is compiled to a file named based on the original entrypoint name. For example,index.built.css
forindex.css
andcustom.built.css
forcustom.css
.For BC compatibility, the
input_css
still accepts a string value and requires no changes from the developerFeedback and improvement ideas are welcomed. Thank you!