Tailwind fails if lektor build
run from outside the Lektor project directory
#4
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.
Since relative paths are used to configure the
content
paths intailwind.config.js
, tailwind can not find the source content unless it is run from the Lektor project directory.Lektor-tailwind currently fails to chdir to the Lektor project directory before running tailwind for
lektor build
. (It does chdir before running tailwind in watch mode forlektor server
.)This fixes that.