# Discourse Theme CLI errors with pnpm installed node\_modules due to symlinks

**URL:** <https://meta.discourse.org/t/discourse-theme-cli-errors-with-pnpm-installed-node-modules-due-to-symlinks/341168>\
**Category:** Development\
**Created:** [December 8, 2024, 4:14am UTC](https://meta.discourse.org/t/discourse-theme-cli-errors-with-pnpm-installed-node-modules-due-to-symlinks/341168 "2024-12-08T04:14:15Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Alteras](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/alteras/32/179824_2.png) [@Alteras](https://meta.discourse.org/u/Alteras)\
**Post date:** [December 9, 2024, 6:52pm UTC](https://meta.discourse.org/t/discourse-theme-cli-errors-with-pnpm-installed-node-modules-due-to-symlinks/341168/3 "2024-12-09T18:52:59Z")

</div>

I use it from within the TC directory itself since I’m usually developing/testing the theme either against my local dev instance, a dev copy of the forum not on my machine, or the Theme Creator site (which the API key generator doesn’t seem to be working lately). Trying to avoid getting confused about which environment I’m working in.

I’ve git cloned the mermaid TC into the same codespace as a fresh discourse codespace install and tried to run the discourse\_theme watch from the discourse directory instead. Gives the same errors.

---

_[View the full topic](https://meta.discourse.org/t/discourse-theme-cli-errors-with-pnpm-installed-node-modules-due-to-symlinks/341168)._
