Electron seems depending an unsupported package: npm warn deprecated [email protected]: Package no longer supported.
Forwarding this issue from here : https://github.com/electron/electron/issues/44416
Just encountered the same issue.
System: Sonoma MacBook Pro M1 14"
I was updating node_mods and seemed to get the same:
npm warn deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
Any Solution?
Same issue here.
Reposting from the electron/electron issue, but this is the upstream problem: https://github.com/gajus/global-agent/issues/70
use npm install electron@latest
use npm install electron@latest
That won't work. The global-agent package has not been patched to remove usage of the boolean package yet as per the upstream issue.
Same issue here.
Any Solution?
I had this same issue when I try to create an electron folder myself, but when I used the Electron quick start on Github it no longer gave me the warning that the package wasn't supported. Very odd but that's what worked for me.
Installing a new version of electron won't solve the issue according to this project's lockfile. Perhaps npm just isn't showing the warning on every single install?
https://github.com/electron/get/blob/e2be2100331a7873a8e2b0b209b7953eef8f9803/yarn.lock#L1130-L1133
It is still there after half a year no ? Any solution found or any news about it ?
I'm currently building on Electron and the warning did go away. npm i just now, no issues
I'm currently building on Electron and the warning did go away.
npm ijust now, no issues
Maybe they fixed it now, I started the project when I commented, or it happens to some and to some not xd
It is still there after half a year no ? Any solution found or any news about it ?
There hasn't been a new release fixing the upstream issue since, so no. Please read the above context in thread.
Same here
it's not fixed yet
i had the same issue but solved it running "npm update", in the CLI. after that you can run the "npm install electron --save-dev" sucessfully. let me know if it worked for you.
The issue still persists as of today:
npm warn deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
added 70 packages, and audited 71 packages in 6s
17 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
Installed version
"electron": "^36.3.2"
However if I install the latest version of @electron/get first (4.0.0), then install electron after, the warning disappears.
Create a new directory, run 'npm init - y' Then run 'npm update' You will get the package - lock. Json script Run 'npm i - d electron'. The quote is not included in the code pls . Are you on windows?
On Sun, Jun 1, 2025, 4:54 PM Karim @.***> wrote:
karimb11 left a comment (electron/get#304) https://github.com/electron/get/issues/304#issuecomment-2927450764
The issue still persists as of today:
npm warn deprecated @.***: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
added 70 packages, and audited 71 packages in 6s
17 packages are looking for funding run
npm fundfor detailsfound 0 vulnerabilities
Installed version
"electron": "^36.3.2"
— Reply to this email directly, view it on GitHub https://github.com/electron/get/issues/304#issuecomment-2927450764, or unsubscribe https://github.com/notifications/unsubscribe-auth/APYOCIZTRGR6J3TD7RYDNKL3BMO4DAVCNFSM6AAAAABQZHTAQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMRXGQ2TANZWGQ . You are receiving this because you commented.Message ID: @.***>
Sorry I saw the rest of your message and realized that it was successful. It will still show you the warn message but then it will work. Try initializing the window and see if it doesn't work use the directions of the previous message I sent you. Cheers
On Sun, Jun 1, 2025, 5:05 PM Ebis Watson-Aputu @.***> wrote:
Create a new directory, run 'npm init - y' Then run 'npm update' You will get the package - lock. Json script Run 'npm i - d electron'. The quote is not included in the code pls . Are you on windows?
On Sun, Jun 1, 2025, 4:54 PM Karim @.***> wrote:
karimb11 left a comment (electron/get#304) https://github.com/electron/get/issues/304#issuecomment-2927450764
The issue still persists as of today:
npm warn deprecated @.***: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
added 70 packages, and audited 71 packages in 6s
17 packages are looking for funding run
npm fundfor detailsfound 0 vulnerabilities
Installed version
"electron": "^36.3.2"
— Reply to this email directly, view it on GitHub https://github.com/electron/get/issues/304#issuecomment-2927450764, or unsubscribe https://github.com/notifications/unsubscribe-auth/APYOCIZTRGR6J3TD7RYDNKL3BMO4DAVCNFSM6AAAAABQZHTAQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMRXGQ2TANZWGQ . You are receiving this because you commented.Message ID: @.***>
One more thing if you are using powershell in vscode change it to cmd prompt
On Sun, Jun 1, 2025, 5:09 PM Ebis Watson-Aputu @.***> wrote:
Sorry I saw the rest of your message and realized that it was successful. It will still show you the warn message but then it will work. Try initializing the window and see if it doesn't work use the directions of the previous message I sent you. Cheers
On Sun, Jun 1, 2025, 5:05 PM Ebis Watson-Aputu @.***> wrote:
Create a new directory, run 'npm init - y' Then run 'npm update' You will get the package - lock. Json script Run 'npm i - d electron'. The quote is not included in the code pls . Are you on windows?
On Sun, Jun 1, 2025, 4:54 PM Karim @.***> wrote:
karimb11 left a comment (electron/get#304) https://github.com/electron/get/issues/304#issuecomment-2927450764
The issue still persists as of today:
npm warn deprecated @.***: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
added 70 packages, and audited 71 packages in 6s
17 packages are looking for funding run
npm fundfor detailsfound 0 vulnerabilities
Installed version
"electron": "^36.3.2"
— Reply to this email directly, view it on GitHub https://github.com/electron/get/issues/304#issuecomment-2927450764, or unsubscribe https://github.com/notifications/unsubscribe-auth/APYOCIZTRGR6J3TD7RYDNKL3BMO4DAVCNFSM6AAAAABQZHTAQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMRXGQ2TANZWGQ . You are receiving this because you commented.Message ID: @.***>
The issue still persists as of today:截至今天,该问题仍然存在:
npm warn deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. added 70 packages, and audited 71 packages in 6s 17 packages are looking for funding run `npm fund` for details found 0 vulnerabilitiesInstalled version 安装版本
"electron": "^36.3.2"However if I install the latest version of
@electron/getfirst (4.0.0), then install electron after, the warning disappears.但是,如果我先安装最新版本的@electron/get(4.0.0),然后再安装 electron,警告就会消失。
This is useful for me
The issue still persists as of today:截至今天,该问题仍然存在:
npm warn deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. added 70 packages, and audited 71 packages in 6s 17 packages are looking for funding run `npm fund` for details found 0 vulnerabilitiesInstalled version 安装版本
"electron": "^36.3.2"However if I install the latest version of
@electron/getfirst (4.0.0), then install electron after, the warning disappears.但是,如果我先安装最新版本的@electron/get(4.0.0),然后再安装 electron,警告就会消失。This is useful for me
The warning persists for me even with this method, it's just that it appears during installation of @electron/get instead of electron. (Ventura MacBook Air M1, if it helps.)
Create a new directory, run 'npm init - y' Then run 'npm update' You will get the package - lock. Json script Run 'npm i - d electron'. The quote is not included in the code pls . Are you on windows? …
Oh god thank you for this. I was about to pull my last few hairs out. Did the "npm i - d electron" command and no issue. Ran "npm install electron --save-dev" again and no errors.
It seems that someone has fixed the upstream issue, but the pull request is still pending for review: https://github.com/gajus/global-agent/pull/72#issue-2793183545