Run Tailwind CSS from installed plugin directory#8
Merged
justinmayer merged 1 commit intomainfrom Feb 19, 2025
Merged
Conversation
Workaround to address an error, possibly related to Tailwind CSS 4.x: npm error could not determine executable to run
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Recently the following error began to appear:
Three possibly-relevant lines from the NPM verbose log are:
The test site project and plugin are configured for Tailwind CSS 3.x, so it is not at all clear how and why Tailwind CSS 4.0.7 appears in the verbose log, but that is the mostly likely culprit given that this error has never occurred before.
My current workaround is to ensure that Tailwind CSS is invoked from the installed plugin directory instead of the Pelican site project root.