Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Tailwind CSS standalone CLI instead of NPM #10

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

justinmayer
Copy link
Contributor

Adds pytailwindcss Python package as a dependency, removing need for Node.js / NPM to be installed.

Other notes:

  • This PR is currently focused on Tailwind CSS v3 and may not function correctly on v4.
  • Only Tailwind CSS plugins that are bundled with Tailwind CSS standalone CLI v3 are supported — adding Tailwind CSS plugins to the TAILWIND Pelican setting is no longer supported.
  • If someone wants to submit a follow-up PR to re-instate the removed Node.js/NPM-based functionality via a configuration setting along the lines of what I mentioned previously, that would be welcome.
  • v0.3.0 of this plugin fixed one problem but may have created another — changing the working directory may have caused Tailwind to no longer find templates, resulting in an output.css file that is missing needed utility classes.
  • v0.2.0 of this plugin does not appear to function correctly after the release of Tailwind CSS v4, so at present the only version of this plugin that seems to work correctly is the code in this branch, and only then if you set "TAILWIND": {"version": "3.x.x"} in your Pelican settings file (pelicanconf.py).
  • This PR should probably be adjusted to support Tailwind CSS v4, perhaps before merging.

Closes #4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Prevent the npm install to run every time
1 participant