fix: tailwindcss
import insertions and execution order
#221
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #220
This is a good instance where having
runsAfter
would've been useful. Whiletailwindcss
doesn't requireprettier
to function, ensuring that it's executed afterprettier
would've guaranteed that theprettier-plugin-tailwindcss
is installed when they've both been selectedrather than bringing
runsAfter
back, I've tweaked the sorting order so that 2 adders that don't havedependsOn
specified stay in place, which is just a temp fixRe: Duplicate
@import
statements - this was another case where"
vs'
made a difference