# Error running BuildClientProjects.bat - @yarnpkg/parsers@3.0.0-rc.49: The engine “node” is incompatible with this module

**URL:** <https://forum.litium.com/t/error-running-buildclientprojects-bat-yarnpkg-parsers-3-0-0-rc-49-the-engine-node-is-incompatible-with-this-module/3027>\
**Category:** Questions\
**Tags:** litium-7, litium-8\
**Created:** [August 24, 2023, 10:38am UTC](https://forum.litium.com/t/error-running-buildclientprojects-bat-yarnpkg-parsers-3-0-0-rc-49-the-engine-node-is-incompatible-with-this-module/3027 "2023-08-24T10:38:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![timothybrostrom](https://avatars.discourse-cdn.com/v4/letter/t/c67d28/32.png) [@timothybrostrom](https://forum.litium.com/u/timothybrostrom)\
**Post date:** [August 24, 2023, 10:38am UTC](https://forum.litium.com/t/error-running-buildclientprojects-bat-yarnpkg-parsers-3-0-0-rc-49-the-engine-node-is-incompatible-with-this-module/3027/1 "2023-08-24T10:38:50Z")

</div>

We are currently getting this error when running BuildClientProjects.bat on all of our projects if they don’t have an older yarn.lock file already

We’ve solved it temporarily by adding  
“resolutions”: {  
“@yarnpkg/parsers”: “3.0.0-rc.48.1”  
}  
to the package.json files but that’s not a long term solution.

* * *

error @yarnpkg/parsers@3.0.0-rc.49: The engine “node” is incompatible with this module. Expected version “\>=18.12.0”. Got “16.10.0”  
error Found incompatible module.

* * *

I can see that this has been an issue before with a previous version of the parsers but now the issue has arisen again.

The Litium versions affected are all of them.

---

<div class="post-metadata">

**Author:** ![samuel](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.litium.com/samuel/32/479_2.png) [@samuel](https://forum.litium.com/u/samuel)\
**Post date:** [August 24, 2023, 11:34am UTC](https://forum.litium.com/t/error-running-buildclientprojects-bat-yarnpkg-parsers-3-0-0-rc-49-the-engine-node-is-incompatible-with-this-module/3027/2 "2023-08-24T11:34:53Z")

</div>

I reported it the last time but noticed it happening again the other day. Our temporary solution was to add --ignore-engines after the “&$yarnCommand install” command in the BuildClientProjects.ps1 file. But that’s not a long term solution either.

Last time it started working again after a few days so that we could revert our temporary solution. Not sure what fixed it though but it was nothing we did.

---

<div class="post-metadata">

**Author:** ![patric.forsgard](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.litium.com/patric.forsgard/32/10_2.png) [@patric.forsgard](https://forum.litium.com/u/patric.forsgard)\
**Post date:** [August 24, 2023, 3:48pm UTC](https://forum.litium.com/t/error-running-buildclientprojects-bat-yarnpkg-parsers-3-0-0-rc-49-the-engine-node-is-incompatible-with-this-module/3027/3 "2023-08-24T15:48:06Z")

</div>

The problem is in the [nx package](https://github.com/nrwl/nx/blob/12db1e0c775c0db71fc98692feb975aa2446e644/package.json#L321C39-L321C39) that refer the pre-release package of yarnpkg/parsers and until they have solved their package dependency to not use the prerelease version I think we will have and need this workaround, that it was fixed before was that the yarnpkg/parsers maintainers was obsoleting the new version they was putting out but now it seams they have created new prereleases out for the 3-version and the problem come back again.

If you have newer node version you will get other dependency that have the similar restrictions but we monitoring this and looking for a permanent solution.

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex030/uploads/litium/original/1X/12eddac3b8b661de1db86af10ac8151b571e6fb9.png) [@system](https://forum.litium.com/u/system)\
**Post date:** [September 21, 2023, 3:48pm UTC](https://forum.litium.com/t/error-running-buildclientprojects-bat-yarnpkg-parsers-3-0-0-rc-49-the-engine-node-is-incompatible-with-this-module/3027/4 "2023-09-21T15:48:45Z")

</div>

Closed on September 21, 2023, 3:48pm UTC

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