Skip to content

fix: use npm update instead of npm install in update notification #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Jamkris merged 1 commit into from
Apr 13, 2026
Merged

fix: use npm update instead of npm install in update notification #23

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/i18n/locales/en.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,7 @@ export const en: Messages = {

// Update check
updateAvailable: (current, latest) => `Update available: ${current} → ${latest}`,
updateCommand: 'Run `npm install -g git-env-manager` to update.',
updateCommand: 'Run `npm update -g git-env-manager` to update.',

// General
unexpectedError: 'An unexpected error occurred.',
Expand Down
2 changes: 1 addition & 1 deletion src/i18n/locales/ko.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,7 @@ export const ko: Messages = {

// Update check
updateAvailable: (current, latest) => `새 버전이 있습니다: ${current} → ${latest}`,
updateCommand: '업데이트: npm install -g git-env-manager',
updateCommand: '업데이트: npm update -g git-env-manager',

// General
unexpectedError: '예상치 못한 오류가 발생했습니다.',
Expand Down
Loading