[GH-ISSUE #77] [BUG] Launcher is not setting the NODE_ENV environment variable. #35

Closed
opened 2026-10-15 18:06:25 +00:00 by bsakaguchi · 1 comment
Owner

Originally created by @Cohee1207 on GitHub (Sep 25, 2024).
Original GitHub issue: https://github.com/SillyTavern/SillyTavern-Launcher/issues/77

Environment

🪟 Windows

System

Any Windows

Describe the problem

The startup scripts in the main repo set the NODE_ENV to production.
github.com/SillyTavern/SillyTavern@5a4e23f62f/Start.bat (L3)

This doesn't happen when using the launcher.

Additional info

Why is it bad?

  1. The server will report as running in an undefined environment upon startup.
  2. Some libraries may not include additional optimizations that are only activated in production.

How to fix?

Add set NODE_ENV=production at the very start of the launcher.bat or in the server startup string.

Please tick the boxes

Originally created by @Cohee1207 on GitHub (Sep 25, 2024). Original GitHub issue: https://github.com/SillyTavern/SillyTavern-Launcher/issues/77 ### Environment 🪟 Windows ### System Any Windows ### Describe the problem The startup scripts in the main repo set the NODE_ENV to production. https://github.com/SillyTavern/SillyTavern/blob/5a4e23f62f12d3b91d01d261d52a3e78abff8492/Start.bat#L3 This doesn't happen when using the launcher. ### Additional info Why is it bad? 1. The server will report as running in an undefined environment upon startup. 2. Some libraries may not include additional optimizations that are only activated in production. How to fix? Add `set NODE_ENV=production` at the very start of the launcher.bat or in the server startup string. ### Please tick the boxes - [X] I have explained the issue clearly, and I included all relevant info - [X] I have checked that this [issue hasn't already been raised](https://github.com/SillyTavern/SillyTavern/issues?q=is%3Aissue) - [X] I have checked the [docs](https://docs.sillytavern.app/) ![important](https://img.shields.io/badge/Important!-F6094E)
Author
Owner

@deffcolony commented on GitHub (Sep 25, 2024):

this issue has now been fixed at

github.com/SillyTavern/SillyTavern-Launcher@3c6bca6006 (diff-a0205db631)
and
github.com/SillyTavern/SillyTavern-Launcher@a07fa2eea0

<!-- gh-comment-id:2373828869 --> @deffcolony commented on GitHub (Sep 25, 2024): this issue has now been fixed at https://github.com/SillyTavern/SillyTavern-Launcher/commit/3c6bca60065e3fd69faad98e51ffd292689e1414#diff-a0205db631f5d0cd7cb7ccd40570bf1addb891e7775d7aa8cba136ee3b30834dR21 and https://github.com/SillyTavern/SillyTavern-Launcher/commit/a07fa2eea096dc455b1e0df2eab71d8598860ad8
Sign in to join this conversation.
No description provided.