Skip to content
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.

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

[BUG] NPM packages fail to update #3214

Open
4 tasks done
redactedscribe opened this issue Jan 22, 2025 · 7 comments
Open
4 tasks done

[BUG] NPM packages fail to update #3214

redactedscribe opened this issue Jan 22, 2025 · 7 comments
Assignees
Labels
bug Something isn't working ready-to-go
Milestone

Comments

@redactedscribe
Copy link
Contributor

Please confirm these before moving forward

  • I have searched for my issue and have not found a work-in-progress/duplicate/resolved issue.
  • I have tested that this issue has not been fixed in the latest (beta or stable) release.
  • I have checked the FAQ section for solutions.
  • This issue is about a bug (if it is not, please use the correct template).

UniGetUI Version

3.1.6-beta2

Windows version, edition, and architecture

Windows 11 Pro

Describe your issue

Not sure when this started, either with the current stable, or since the current beta 1, but I can't seem to update NPM packages anymore.

Steps to reproduce the issue

  1. Attempt to update an NPM package.

UniGetUI Log

-

Package Managers Logs

-

Relevant information

"Svelte" package update attempt:

Package update operation for Package=svelte with Manager=Npm
Installation options: <InstallationOptions: SkipHashCheck=False;InteractiveInstallation=False;RunAsAdministrator=False;Version=;Architecture=;InstallationScope=;InstallationScope=;CustomParameters=;RemoveDataOnUninstall=False>
Executing process with StartInfo:
 - FileName: "C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe"
 - Arguments: "-NoProfile -ExecutionPolicy Bypass -Command npm install [email protected] svelte"
Start Time: "22/01/2025 02:05:22"
npm error code EPERM
npm error syscall mkdir
npm error path C:\Program Files\UniGetUI\node_modules\.esrap-GCdCo29r
npm error errno -4048
npm error Error: EPERM: operation not permitted, mkdir 'C:\Program Files\UniGetUI\node_modules\.esrap-GCdCo29r'
npm error     at async Object.mkdir (node:internal/fs/promises:858:10)
npm error     at async moveFile (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\fs\lib\move-file.js:27:3)
npm error     at async Promise.all (index 0)
npm error     at async moveFile (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\fs\lib\move-file.js:36:9)
npm error     at async Promise.allSettled (index 0)
npm error     at async [reifyPackages] (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:325:11)
npm error     at async Arborist.reify (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:142:5)
npm error     at async Install.exec (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\lib\commands\install.js:150:5)
npm error     at async Npm.exec (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\lib\npm.js:207:9)
npm error     at async module.exports (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\lib\cli\entry.js:74:5) {
npm error   errno: -4048,
npm error   code: 'EPERM',
npm error   syscall: 'mkdir',
npm error   path: 'C:\\Program Files\\UniGetUI\\node_modules\\.esrap-GCdCo29r'
npm error }
npm error
npm error The operation was rejected by your operating system.
npm error It's possible that the file was already in use (by a text editor or antivirus),
npm error or that you lack permissions to access it.
npm error
npm error If you believe this might be a permissions issue, please double-check the
npm error permissions of the file and its containing directories, or try running
npm error the command again as root/Administrator.
npm error A complete log of this run can be found in: D:\Scoop\persist\nodejs\cache\_logs\2025-01-22T00_05_23_615Z-debug-0.log
End Time: "22/01/2025 02:05:25"
Process return value: "1" (0x1)
Svelte could not be updated

(Same output for) "Cli" (Tauri) package update attempt:

Package update operation for Package=@tauri-apps/cli with Manager=Npm
Installation options: <InstallationOptions: SkipHashCheck=False;InteractiveInstallation=False;RunAsAdministrator=False;Version=;Architecture=;InstallationScope=;InstallationScope=;CustomParameters=;RemoveDataOnUninstall=False>
Executing process with StartInfo:
 - FileName: "C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe"
 - Arguments: "-NoProfile -ExecutionPolicy Bypass -Command npm install @tauri-apps/[email protected] @tauri-apps/cli"
Start Time: "22/01/2025 02:05:25"
npm error code EPERM
npm error syscall mkdir
npm error path C:\Program Files\UniGetUI\node_modules\@tauri-apps
npm error errno -4048
npm error Error: EPERM: operation not permitted, mkdir 'C:\Program Files\UniGetUI\node_modules\@tauri-apps'
npm error     at async mkdir (node:internal/fs/promises:858:10)
npm error     at async D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:624:20
npm error     at async Promise.allSettled (index 0)
npm error     at async [reifyPackages] (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:325:11)
npm error     at async Arborist.reify (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:142:5)
npm error     at async Install.exec (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\lib\commands\install.js:150:5)
npm error     at async Npm.exec (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\lib\npm.js:207:9)
npm error     at async module.exports (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\lib\cli\entry.js:74:5) {
npm error   errno: -4048,
npm error   code: 'EPERM',
npm error   syscall: 'mkdir',
npm error   path: 'C:\\Program Files\\UniGetUI\\node_modules\\@tauri-apps'
npm error }
npm error
npm error The operation was rejected by your operating system.
npm error It's possible that the file was already in use (by a text editor or antivirus),
npm error or that you lack permissions to access it.
npm error
npm error If you believe this might be a permissions issue, please double-check the
npm error permissions of the file and its containing directories, or try running
npm error the command again as root/Administrator.
npm error A complete log of this run can be found in: D:\Scoop\persist\nodejs\cache\_logs\2025-01-22T00_05_27_211Z-debug-0.log
End Time: "22/01/2025 02:05:30"
Process return value: "1" (0x1)
Cli could not be updated

The full NPM log as mentioned in the output above for the "Cli" package:

0 verbose cli D:\Scoop\apps\nodejs\current\node.exe D:\Scoop\apps\nodejs\current\node_modules\npm\bin\npm-cli.js
1 info using [email protected]
2 info using [email protected]
3 silly config load:file:D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\npmrc
4 silly config load:file:C:\Program Files\UniGetUI\.npmrc
5 silly config load:file:C:\Users\User\.npmrc
6 silly config load:file:D:\Scoop\persist\nodejs\bin\etc\npmrc
7 verbose title npm install @tauri-apps/[email protected] @tauri-apps/cli
8 verbose argv "install" "@tauri-apps/[email protected]" "@tauri-apps/cli"
9 verbose logfile logs-max:10 dir:D:\Scoop\persist\nodejs\cache\_logs\2025-01-22T00_17_09_944Z-
10 verbose logfile D:\Scoop\persist\nodejs\cache\_logs\2025-01-22T00_17_09_944Z-debug-0.log
11 silly logfile start cleaning logs, removing 1 files
12 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368
13 silly logfile done cleaning log files
14 silly idealTree buildDeps
15 silly fetch manifest @tauri-apps/[email protected]
16 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli cache-miss
17 http fetch GET 200 https://registry.npmjs.org/@tauri-apps%2fcli 1650ms (cache updated)
18 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli set size:undefined disposed:false
19 silly placeDep ROOT @tauri-apps/[email protected] OK for:  want: 2.2.5
20 silly fetch manifest @tauri-apps/[email protected]
21 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-win32-x64-msvc cache-miss
22 silly fetch manifest @tauri-apps/[email protected]
23 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-darwin-x64 cache-miss
24 silly fetch manifest @tauri-apps/[email protected]
25 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-linux-x64-gnu cache-miss
26 silly fetch manifest @tauri-apps/[email protected]
27 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-darwin-arm64 cache-miss
28 silly fetch manifest @tauri-apps/[email protected]
29 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-linux-arm64-gnu cache-miss
30 silly fetch manifest @tauri-apps/[email protected]
31 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-linux-arm64-musl cache-miss
32 silly fetch manifest @tauri-apps/[email protected]
33 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-linux-arm-gnueabihf cache-miss
34 silly fetch manifest @tauri-apps/[email protected]
35 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-linux-x64-musl cache-miss
36 silly fetch manifest @tauri-apps/[email protected]
37 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-win32-ia32-msvc cache-miss
38 silly fetch manifest @tauri-apps/[email protected]
39 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-win32-arm64-msvc cache-miss
40 http fetch GET 200 https://registry.npmjs.org/@tauri-apps%2fcli-win32-x64-msvc 1462ms (cache updated)
41 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-win32-x64-msvc set size:undefined disposed:false
42 http fetch GET 200 https://registry.npmjs.org/@tauri-apps%2fcli-linux-arm64-musl 1679ms (cache updated)
43 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-linux-arm64-musl set size:undefined disposed:false
44 http fetch GET 200 https://registry.npmjs.org/@tauri-apps%2fcli-win32-ia32-msvc 1685ms (cache updated)
45 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-win32-ia32-msvc set size:undefined disposed:false
46 http fetch GET 200 https://registry.npmjs.org/@tauri-apps%2fcli-linux-arm-gnueabihf 1689ms (cache updated)
47 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-linux-arm-gnueabihf set size:undefined disposed:false
48 http fetch GET 200 https://registry.npmjs.org/@tauri-apps%2fcli-linux-x64-musl 1691ms (cache updated)
49 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-linux-x64-musl set size:undefined disposed:false
50 http fetch GET 200 https://registry.npmjs.org/@tauri-apps%2fcli-linux-arm64-gnu 1702ms (cache updated)
51 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-linux-arm64-gnu set size:undefined disposed:false
52 http fetch GET 200 https://registry.npmjs.org/@tauri-apps%2fcli-darwin-x64 1721ms (cache updated)
53 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-darwin-x64 set size:undefined disposed:false
54 http fetch GET 200 https://registry.npmjs.org/@tauri-apps%2fcli-linux-x64-gnu 1727ms (cache updated)
55 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-linux-x64-gnu set size:undefined disposed:false
56 http fetch GET 200 https://registry.npmjs.org/@tauri-apps%2fcli-win32-arm64-msvc 1732ms (cache updated)
57 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-win32-arm64-msvc set size:undefined disposed:false
58 http fetch GET 200 https://registry.npmjs.org/@tauri-apps%2fcli-darwin-arm64 1874ms (cache updated)
59 silly packumentCache full:https://registry.npmjs.org/@tauri-apps%2fcli-darwin-arm64 set size:undefined disposed:false
60 silly placeDep ROOT @tauri-apps/[email protected] OK for: @tauri-apps/[email protected] want: 2.2.5
61 silly placeDep ROOT @tauri-apps/[email protected] OK for: @tauri-apps/[email protected] want: 2.2.5
62 silly placeDep ROOT @tauri-apps/[email protected] OK for: @tauri-apps/[email protected] want: 2.2.5
63 silly placeDep ROOT @tauri-apps/[email protected] OK for: @tauri-apps/[email protected] want: 2.2.5
64 silly placeDep ROOT @tauri-apps/[email protected] OK for: @tauri-apps/[email protected] want: 2.2.5
65 silly placeDep ROOT @tauri-apps/[email protected] OK for: @tauri-apps/[email protected] want: 2.2.5
66 silly placeDep ROOT @tauri-apps/[email protected] OK for: @tauri-apps/[email protected] want: 2.2.5
67 silly placeDep ROOT @tauri-apps/[email protected] OK for: @tauri-apps/[email protected] want: 2.2.5
68 silly placeDep ROOT @tauri-apps/[email protected] OK for: @tauri-apps/[email protected] want: 2.2.5
69 silly placeDep ROOT @tauri-apps/[email protected] OK for: @tauri-apps/[email protected] want: 2.2.5
70 silly reify moves {}
71 verbose stack Error: EPERM: operation not permitted, mkdir 'C:\Program Files\UniGetUI\node_modules\@tauri-apps'
71 verbose stack     at async mkdir (node:internal/fs/promises:858:10)
71 verbose stack     at async D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:624:20
71 verbose stack     at async Promise.allSettled (index 0)
71 verbose stack     at async [reifyPackages] (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:325:11)
71 verbose stack     at async Arborist.reify (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:142:5)
71 verbose stack     at async Install.exec (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\lib\commands\install.js:150:5)
71 verbose stack     at async Npm.exec (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\lib\npm.js:207:9)
71 verbose stack     at async module.exports (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\lib\cli\entry.js:74:5)
72 error code EPERM
73 error syscall mkdir
74 error path C:\Program Files\UniGetUI\node_modules\@tauri-apps
75 error errno -4048
76 error Error: EPERM: operation not permitted, mkdir 'C:\Program Files\UniGetUI\node_modules\@tauri-apps'
76 error     at async mkdir (node:internal/fs/promises:858:10)
76 error     at async D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:624:20
76 error     at async Promise.allSettled (index 0)
76 error     at async [reifyPackages] (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:325:11)
76 error     at async Arborist.reify (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:142:5)
76 error     at async Install.exec (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\lib\commands\install.js:150:5)
76 error     at async Npm.exec (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\lib\npm.js:207:9)
76 error     at async module.exports (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\lib\cli\entry.js:74:5) {
76 error   errno: -4048,
76 error   code: 'EPERM',
76 error   syscall: 'mkdir',
76 error   path: 'C:\\Program Files\\UniGetUI\\node_modules\\@tauri-apps'
76 error }
77 error
77 error The operation was rejected by your operating system.
77 error It's possible that the file was already in use (by a text editor or antivirus),
77 error or that you lack permissions to access it.
77 error
77 error If you believe this might be a permissions issue, please double-check the
77 error permissions of the file and its containing directories, or try running
77 error the command again as root/Administrator.
78 silly unfinished npm timer reify 1737505030955
79 silly unfinished npm timer reify:createSparse 1737505034519
80 verbose cwd C:\Program Files\UniGetUI
81 verbose os Windows_NT 10.0.22631
82 verbose node v23.6.1
83 verbose npm  v10.9.2
84 verbose exit -4048
85 verbose code -4048
86 error A complete log of this run can be found in: D:\Scoop\persist\nodejs\cache\_logs\2025-01-22T00_17_09_944Z-debug-0.log

Trying to update "Cli" as admin:

Package update operation for Package=@tauri-apps/cli with Manager=Npm
Installation options: <InstallationOptions: SkipHashCheck=False;InteractiveInstallation=False;RunAsAdministrator=True;Version=;Architecture=;InstallationScope=;InstallationScope=;CustomParameters=;RemoveDataOnUninstall=False>
Executing process with StartInfo:
 - FileName: "C:\Program Files\UniGetUI\Assets\Utilities\UniGetUI Elevator.exe"
 - Arguments: ""C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe"  -NoProfile -ExecutionPolicy Bypass -Command npm install @tauri-apps/[email protected] @tauri-apps/cli"
Start Time: "22/01/2025 02:23:27"
The system cannot find the path specified.
up to date, audited 22 packages in 2s
1 package is looking for funding
run `npm fund` for details
found 0 vulnerabilities
End Time: "22/01/2025 02:23:33"
Process return value: "1" (0x1)
Cli could not be updated

Doesn't appear to be blocked in any way via my firewall.

Screenshots and videos

No response

@redactedscribe redactedscribe added the bug Something isn't working label Jan 22, 2025
@marticliment
Copy link
Owner

Please try to upgrade via terminal, and see if this still fails.
As you can see by the logs, this is npm crashing, not UniGetUI

@marticliment marticliment added this to the Bugs milestone Jan 22, 2025
@redactedscribe
Copy link
Contributor Author

redactedscribe commented Jan 22, 2025

I'm not particularly familiar with NPM which isn't helping. Interestingly, I don't see Svelte or Cli listed globally with the following command, so there's nothing to manually update:

> npm list -g
D:\Scoop\persist\nodejs\bin
+-- @electron/[email protected]
+-- @vscode/[email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
`-- [email protected]

I've run npm cache clean --force and re-run UniGetUI, but I'm still seeing the two updates available to these NPM packages.

Looking at the log above there's 71 verbose stack Error: EPERM: operation not permitted, mkdir 'C:\Program Files\UniGetUI\node_modules\@tauri-apps'. Why is NPM / UniGetUI trying to install(?) the Cli (Tauri) update under UniGetUI's installation path? The modules should be somewhere in D:\Scoop\apps\nodejs I believe.

I don't use NPM so I don't think its configuration would've changed.

Hmm, here's Cli and Svelte. I probably installed the two via UniGetUI some months ago. Why do they get installed to C:\Program Files\UniGetUI\node_modules\? Shouldn't they install to where NPM packages normally install (the Scoop path)? Or does UniGetUI come bundled with its own NPM and that's why?:

> npm list
UniGetUI@ C:\Program Files\UniGetUI
+-- @tauri-apps/[email protected]
`-- [email protected]

Running npm update here gives the same(?) output as before:

14:14 ❯ npm update
npm error code EPERM
npm error syscall mkdir
npm error path C:\Program Files\UniGetUI\node_modules\.esrap-GCdCo29r
npm error errno -4048
npm error Error: EPERM: operation not permitted, mkdir 'C:\Program Files\UniGetUI\node_modules\.esrap-GCdCo29r'
npm error     at async Object.mkdir (node:internal/fs/promises:858:10)
npm error     at async moveFile (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\fs\lib\move-file.js:27:3)
npm error     at async Promise.all (index 0)
npm error     at async moveFile (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\fs\lib\move-file.js:36:9)
npm error     at async Promise.allSettled (index 0)
npm error     at async [reifyPackages] (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:325:11)
npm error     at async Arborist.reify (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:142:5)
npm error     at async Update.exec (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\lib\commands\update.js:63:5)
npm error     at async Npm.exec (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\lib\npm.js:207:9)
npm error     at async module.exports (D:\Scoop\apps\nodejs\23.6.1\node_modules\npm\lib\cli\entry.js:74:5) {
npm error   errno: -4048,
npm error   code: 'EPERM',
npm error   syscall: 'mkdir',
npm error   path: 'C:\\Program Files\\UniGetUI\\node_modules\\.esrap-GCdCo29r'
npm error }
npm error
npm error The operation was rejected by your operating system.
npm error It's possible that the file was already in use (by a text editor or antivirus),
npm error or that you lack permissions to access it.
npm error
npm error If you believe this might be a permissions issue, please double-check the
npm error permissions of the file and its containing directories, or try running
npm error the command again as root/Administrator.
npm error A complete log of this run can be found in: D:\Scoop\persist\nodejs\cache\_logs\2025-01-22T12_17_55_340Z-debug-0.log

Thanks.

@marticliment
Copy link
Owner

If running npm update gives the same output, I am afraid this issue has nothing to do with UniGetUI

@marticliment marticliment closed this as not planned Won't fix, can't repro, duplicate, stale Jan 22, 2025
@redactedscribe
Copy link
Contributor Author

redactedscribe commented Jan 22, 2025

@marticliment But why are these packages (modules) installed under UniGetUI's C:\Program Files installation path in the first place? UniGetUI must've installed them there. I don't see why UniGetUI should install them there instead of where NPM installs packages normally.

After some further testing, I cannot even install any new NPM packages using UniGetUI. Same lack of permissions error. Installing packages directly via npm install -g <package> works fine however.

I have deleted C:\Program Files\UniGetUI\node_modules hoping that UniGetUI would recreate this when installing a new NPM package, but it cannot due to the error. Cli and Svelte updates are still somehow listed in UniGetUI (also deleted NPM's package.json in C:\Program Files\UniGetUI).

I'm not convinced this is an NPM issue.

@marticliment
Copy link
Owner

I have no such folder on C:\Program Files\UniGetUI, and I have just tested installing UniGetUI on a disposable VM and I don't see any node_modules nor packages.json folder.

In fact, those folders are not bundled on the installer, so I don't see how they did get created.

If you don't use NPM, you should disable it from UniGetUI Settings

@redactedscribe
Copy link
Contributor Author

redactedscribe commented Jan 22, 2025

@marticliment An old, bugged version of UniGetUI would've installed / copied the NPM packages to its installation directory is my guess, but who knows.

I understand that you have many UniGetUI issues, and limited time, but disabling NPM from being used is not a solution to this problem.

I found another C:\Users\User\node_modules and its package.json where Cli and Svelte lived. Deleted those, now UniGetUI doesn't see them as updates.

The issue remains however that UniGetUI cannot update or install any NPM packages for some reason.

If I could figure out why UniGetUI still causes NPM to try and install new packages to C:\Program Files\UniGetUI\node_modules that could be a lead. Some env setting is probably being passed wrongly to NPM...

Attempting to install npm-check-updates via UniGetUI, two processes launch, and this is some of what a task manager reveals for them:

powershell.exe:

  • Image file name: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
  • Command: "C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy Bypass -Command npm install [email protected] npm-check-updates
  • Current dir: C:\Program Files\UniGetUI\
  • Parent process: UniGetUI.exe

node.exe:

  • Image file name: D:\Scoop\apps\nodejs\23.6.1\node.exe
  • Command: "D:\Scoop\apps\nodejs\current\node.exe" D:\Scoop\apps\nodejs\current/node_modules/npm/bin/npm-cli.js install [email protected] npm-check-updates
  • Current dir: C:\Program Files\UniGetUI\
  • Parent process: powershell.exe

It looks like the issue is as simple as UniGetUI is attempting to install NPM packages without the -g global flag. It wouldn't make sense to install NPM packages non-globally via UniGetUI.

Can you please verify whether or not UniGetUI is passing a global install command to NPM? From the above info, the commands show no -g. If -g is passed, perhaps NPM won't attempt to install to node_modules in the current directory of C:\Program Files\UniGetUI\, but instead to where all other globally installed node modules get installed.

UniGetUI's NPM (Verbose) logs contain no errors.

@marticliment
Copy link
Owner

I will check this, it could be some edge case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ready-to-go
Projects
None yet
Development

No branches or pull requests

2 participants