You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
When installing electron-forge, it will result in this error
npm WARN deprecated wrench@1.5.9: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years.
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN ELOOP: too many symbolic links encountered, lstat '/Users/hanxue/DrRed/Quest-electron/node_modules/electron-forge/node_modules/path-exists'
npm ERR! path /Users/hanxue/DrRed/Quest-electron/node_modules/electron-forge/node_modules
npm ERR! code ELOOP
npm ERR! errno -62
npm ERR! syscall mkdir
npm ERR! ELOOP: too many symbolic links encountered, mkdir '/Users/hanxue/DrRed/Quest-electron/node_modules/electron-forge/node_modules'`
How can the CLI team reproduce the problem?
npm i --save-dev electron-forge
supporting information:
npm -v prints: 5.4.2 (also tested with 5.5.1)
node -v prints: 8.4.0
npm config get registry prints: ****
MacOS 10.10.5
Network issues:
Geographic location where npm was run:
I use a proxy to connect to the npm registry.
I use a proxy to connect to the web.
I use a proxy when downloading Git repos.
I access the npm registry via a VPN
I don't use a proxy, but have limited or unreliable internet access.
Container:
I develop using Vagrant on Windows.
I develop using Vagrant on OS X or Linux.
I develop / deploy using Docker.
I deploy to a PaaS (Triton, Heroku).
The text was updated successfully, but these errors were encountered:
I'm opening this issue because:
What's going wrong?
When installing
electron-forge
, it will result in this errorHow can the CLI team reproduce the problem?
supporting information:
npm -v
prints: 5.4.2 (also tested with 5.5.1)node -v
prints: 8.4.0npm config get registry
prints: ****The text was updated successfully, but these errors were encountered: