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

Windows Script Host Error when trying to run tailwindcss compiler #1992

Open
Deewens opened this issue Feb 21, 2025 · 1 comment
Open

Windows Script Host Error when trying to run tailwindcss compiler #1992

Deewens opened this issue Feb 21, 2025 · 1 comment

Comments

@Deewens
Copy link

Deewens commented Feb 21, 2025

Describe the bug
I need to compile tailwind because I want to edit the layout of one of my page. I tried with three Blowfish (v2.83.0, v2.82.0 and v2.81.0).
The v2.83.0 version does not work due to the upgrade to tailwind 4 (#1985). But 2.82 and 2.81 gives me an error that I don't understand when I run this command (the one given in the documentation) :
./themes/blowfish/node_modules/tailwindcss/lib/cli.js -c ./themes/blowfish/tailwind.config.js -i ./themes/blowfish/assets/css/main.css -o ./assets/css/compiled/main.css --jit

To Reproduce
Steps to reproduce the behavior:

  1. Use version 2.82.0 or 2.81.0 of Blowfish
  2. npm install within the theme folder
  3. run command: ./themes/blowfish/node_modules/tailwindcss/lib/cli.js -c ./themes/blowfish/tailwind.config.js -i ./themes/blowfish/assets/css/main.css -o ./assets/css/compiled/main.css --jit
  4. See error

Expected behavior
Tailwind CLI should work.

Screenshots
Image

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser: Zen Browser (Firefox)
  • Version: 1.7.6b

Hugo & Blowfish versions
Which version of Hugo and Blowfish are you using?
v2.82.0 and v2.81.0 (alongside their supported version, for 2.81.0 I am using hugo v0.140.2)

Additional context
This look like a Windows issue, but I have never seen this kind of dialog error before, and I am not sure how to fix it.

@Deewens
Copy link
Author

Deewens commented Feb 21, 2025

OK, I just found out that I needed to add node before the command for this to works. This should probably be added to the documentation.

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

No branches or pull requests

1 participant