manage.py tailwind build exits with success even if command failed

In my Dockerfile I have this step: RUN ./manage.py tailwind build (followed by ./manage.py collectstatic). The build completed successfully, but the image was broken, because it didn’t contain the static/css/dist directory.

It took a while to figure out; ideally, if manage.py tailwind build fails, it should exit with an error, so that the whole image building fails.

The error was apparent from inside the Docker container; should have run manage.py tailwind install first:

$ ./manage.py tailwind build && echo ok

> theme@3.1.1 build
> npm run build:clean && npm run build:tailwind


> theme@3.1.1 build:clean
> rimraf ../static/css/dist

sh: 1: rimraf: not found
ok

[timonweb]

Indeed, added returncode 1 in 3.3.0. Thanks for reporting.

[mgax]

@2qxtx I’m also on django-tailwind 3.4.0 and rimraf got installed alright. This is in a Docker image, so the node_modules is not left over from a previous version. Hope this helps:

wagtail@1f3f5a0f1cda:/app/theme/static_src$ ls -l node_modules/.bin/rimraf 
lrwxrwxrwx 1 wagtail wagtail 16 Sep 14 10:49 node_modules/.bin/rimraf -> ../rimraf/bin.js
wagtail@1f3f5a0f1cda:/app/theme/static_src$ pip freeze | grep tailwind
django-tailwind==3.4.0
wagtail@1f3f5a0f1cda:/app/theme/static_src$ grep rimraf package*
package-lock.json:        "rimraf": "^3.0.2",
package-lock.json:    "node_modules/rimraf": {
package-lock.json:      "resolved": "https://registry.npmjs.org/rimraf/-/rimraf-3.0.2.tgz",
package-lock.json:        "rimraf": "bin.js"
package-lock.json:    "rimraf": {
package-lock.json:      "resolved": "https://registry.npmjs.org/rimraf/-/rimraf-3.0.2.tgz",
package.json:    "build:clean": "rimraf ../static/css/dist",
package.json:    "rimraf": "^3.0.2",