[RESOLVED] Tailwind PostCSS work with linux but don't work with windows

support
, ,
1

Hello, I’m using @dirkolbrich Hugo’s project with Tailwind CSS look my repository. The project is running fine on a Linux environment but doesn’t work on a Windows environment. I’ve tried reviewing the different Windows paths, but I can’t seem to solve my problem. :s

hugo server --disableFastRender --verbose
WARN  deprecated: --verbose was deprecated in Hugo v0.114.0 and will be removed in a future release. use --logLevel info
Watching for changes in C:\Users\valen\Documents\Dev_site\site valentin\diyhugo\{archetypes,content,layouts,package.json,themes}
Watching for config changes in C:\Users\valen\Documents\Dev_site\site valentin\diyhugo\hugo.toml
Start building sites … 
hugo v0.121.0-e321c3502aa8e80a7a7c951359339a985f082757+extended windows/amd64 BuildDate=2023-12-05T15:22:31Z VendorInfo=gohugoio

INFO  copy static: syncing static files to \
INFO  build: running step "process" duration "1.0177ms"
INFO  build: running step "assemble" duration "3.0169ms"
INFO  deprecated: .Site.IsServer was deprecated in Hugo v0.120.0 and will be removed in a future release. Use hugo.IsServer instead.
INFO  postcss: use config file "C:\\Users\\valen\\Documents\\Dev_site\\site valentin\\diyhugo\\themes\\diyhugo\\assets\\css\\postcss.config.js"
INFO  postcss: 'C:\Program' n'est pas reconnu en tant que commande interne
ou externe, un programme ex�cutable ou un fichier de commandes.
INFO  build: running step "render" duration "139.4655ms"
INFO  build: running step "postProcess" duration "0s"
Built in 148 ms
Error: error building site: POSTCSS: failed to transform "css/styles.css" (text/css): 'C:\Program' n'est pas reconnu en tant que commande interne

I’m looking for a solution here before creating a workspace on Linux on my desktop computer, which I unfortunately wanted to keep under Windows.
Thank you so munch

2

https://gohugo.io/hugo-pipes/postcss/#setup

If you are a Windows user, and the path to your project contains a space, you must place the PostCSS configuration within the package.json file. See this example and issue #7333.

1 Like
3

Hi @jmooring I feel really silly for not having read that line in the documentation :frowning: I sincerely feel embarrassed about it. Thank you for your help, and I apologize to @dirkolbrich for the time spent assisting me.

4

@FR-Coco No problem. The underlying upstream issue has been open since 2016.

1 Like
5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.