# The engine "yarn" is incompatible with this module. Expected version "please-use-pnpm". Got "1.22.19"

**URL:** <https://meta.discourse.org/t/the-engine-yarn-is-incompatible-with-this-module-expected-version-please-use-pnpm-got-1-22-19/350557>\
**Category:** Product Support\
**Created:** [February 5, 2025, 1:17am UTC](https://meta.discourse.org/t/the-engine-yarn-is-incompatible-with-this-module-expected-version-please-use-pnpm-got-1-22-19/350557 "2025-02-05T01:17:40Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![CRCinAU](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crcinau/32/249856_2.png) [@CRCinAU](https://meta.discourse.org/u/CRCinAU)\
**Post date:** [February 5, 2025, 1:17am UTC](https://meta.discourse.org/t/the-engine-yarn-is-incompatible-with-this-module-expected-version-please-use-pnpm-got-1-22-19/350557/1 "2025-02-05T01:17:40Z")

</div>

After getting a notification that an update was available, I jumped into the web interface as normal and hit the update button.

In classic discourse style, the installation has now self-destructed and I can’t seem to get the images built again to run.

I’m running separate data and web images, all via docker.

My manual rebuild script that normally fixes this is:

```plaintext
./launcher bootstrap discourse-web && ./launcher destroy discourse-web && ./launcher start discourse-web

```

When running this, it explodes with:

```plaintext
I, [2025-02-05T01:12:54.160568 #1] INFO -- : > cd /var/www/discourse && gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock)
I, [2025-02-05T01:12:55.503875 #1] INFO -- : Successfully installed bundler-2.5.18
1 gem installed

I, [2025-02-05T01:12:55.503987 #1] INFO -- : > cd /var/www/discourse && find /var/www/discourse ! -user discourse -exec chown discourse {} \+
I, [2025-02-05T01:12:56.681293 #1] INFO -- : 
I, [2025-02-05T01:12:56.681583 #1] INFO -- : > cd /var/www/discourse && if ["beta" != "tests-passed"]; then
  rm -rf app/assets/javascripts/node_modules
fi
I, [2025-02-05T01:12:56.685171 #1] INFO -- : 
I, [2025-02-05T01:12:56.685238 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'yarn install --frozen-lockfile && yarn cache clean'
error discourse@: The engine "yarn" is incompatible with this module. Expected version "please-use-pnpm". Got "1.22.19"
warning discourse@: The engine "pnpm" appears to be invalid.
error Found incompatible module.
I, [2025-02-05T01:12:57.086009 #1] INFO -- : yarn install v1.22.19
info No lockfile found.
[1/5] Validating package.json...
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'yarn install --frozen-lockfile && yarn cache clean' failed with return #<Process::Status: pid 202 exit 1>
Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"yarn", "cmd"=>["if [\"$version\" != \"tests-passed\"]; then\n rm -rf app/assets/javascripts/node_modules\nfi", "su discourse -c 'yarn install --frozen-lockfile && yarn cache clean'"]}
bootstrap failed with exit code 1
**FAILED TO BOOTSTRAP** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
d480e23784a1dd765d52d483ee94174d7d5cfad5ba8ccec61e76a48ac8ddf32a

```

I don’t seem to find any matches to this error, and any kind of reset / pull of the discourse-base image doesn’t seem to make any difference - it all dies here.

Is there a way to get things back up and running again?

---

_[View the full topic](https://meta.discourse.org/t/the-engine-yarn-is-incompatible-with-this-module-expected-version-please-use-pnpm-got-1-22-19/350557)._