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

Error in setup:static-content:deploy #71

Open
slackerzz opened this issue Jan 13, 2023 · 1 comment
Open

Error in setup:static-content:deploy #71

slackerzz opened this issue Jan 13, 2023 · 1 comment

Comments

@slackerzz
Copy link

I'm using versione 1.1.18 with Magento 2.4.4-p2 and while deploying the static content using compact strategy with this command:

php bin/magento setup:static-content:deploy --ansi --no-interaction -f -s compact --jobs 4 --no-html-minify --theme Magento/backend en_US

I get this output:

Deploy using compact strategy
base/Magento/base/default               1461/1461           ============================ 100%   17 secs
adminhtml/Magento/base/default          1425/1425           ============================ 100%   21 secs
frontend/Magento/base/default           1284/1284           ============================ 100%   21 secs
adminhtml/Magento/backend/default       0/266               >--------------------------- 0%     1 sec
Error happened during deploy process: The contents from the "/var/www/html/pub/static/adminhtml/Magento/base/default/tailwind/components/forms.css" file can't be read. Warning!file_get_contents(/var/www/html/pub/static/adminhtml/Magento/base/default/tailwind/components/forms.css): Failed to open stream: No such fil
e or directory

It seems that magento tries to deploy the content of the tailwind directory.

I have found 2 workarounds:

  • switch to standard strategy, but it is slower
  • move the tailwind directory out of web
@Vinai
Copy link
Collaborator

Vinai commented Feb 14, 2023

Thanks for the issue @slackerz!
Back when I wrote the module I had no clue about tailwind, so I just followed the approach in hyva-themes.
I agree the tailwind folder should not be inside of web. Moving it out should be fine.

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

2 participants