mirror of
https://github.com/SillyTavern/SillyTavern-Launcher.git
synced 2026-11-05 00:27:39 +00:00
[PR #122] [MERGED] Add --no-save option to npm install #125
Labels
No labels
🚏 Awaiting User Response
🐛Bug
🐛Bug
🐛Bug
🦄 Feature Request
✅ Fixed
✅ Fixed
👩💻 Good First Issue
‼️ High Priority
🧑💻 In Progress
🐧 Linux
🐧 Linux
💤 Low Priority
🍎 Mac
❕ Medium Priority
pull-request
🪟 Windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
SillyTavern/SillyTavern-Launcher#125
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/SillyTavern/SillyTavern-Launcher/pull/122
Author: @Cohee1207
Created: 12/2/2025
Status: ✅ Merged
Merged: 12/2/2025
Merged by: @deffcolony
Base:
main← Head:feat/no-save📝 Commits (1)
a7736cbAdd --no-save option to npm install📊 Changes
3 files changed (+6 additions, -6 deletions)
View changed files
📝
Launcher.bat(+1 -1)📝
bin/functions/Toolbox/App_Launcher/Core_Utilities/start_st.bat(+3 -3)📝
bin/functions/Toolbox/App_Launcher/Core_Utilities/update_start_st.bat(+2 -2)📄 Description
This should prevent writing
package-lock.json, which creates merge conflicts if the local npm version is older than the one used to generate thepackage-lock.jsonfile.Reference: https://docs.npmjs.com/cli/v11/commands/npm-install#save
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.