Vite Dev server crachses due to a circular reference in a symlink #620
-
| 
         package.json script that is being run via  Waiting for the debugger to disconnect...
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^
Error: ELOOP: too many symbolic links encountered, stat '/opt/homebrew/Library/Homebrew/vendor/gems/mechanize-2.9.1/mechanize-2.9.1'
Emitted 'error' event on FSWatcher instance at:
    at FSWatcher._handleError (file:///Users/vladimir/Dev_Projects/lime812/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:52169:10)
    at FsEventsHandler._handleFsEventsSymlink (file:///Users/vladimir/Dev_Projects/lime812/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:51395:18) {
  errno: -62,
  code: 'ELOOP',
  syscall: 'stat',
  path: '/opt/homebrew/Library/Homebrew/vendor/gems/mechanize-2.9.1/mechanize-2.9.1'
}
Node.js v18.16.1
error: script "dev" exited with code 1 (SIGHUP)while a simple  homebrew/Library/Homebrew/vendor/gems/mechanize-2.9.1 on  stable [$]                                        12:01:15
➜ lsa
total 8
drwxr-xr-x  5 vladimir  admin   160B Jul  4 11:59 .
drwxr-xr-x  4 vladimir  admin   128B May  4 20:53 ..
-rw-r--r--  1 vladimir  admin   1.2K May  4 20:53 LICENSE.txt
drwxr-xr-x  3 vladimir  admin    96B May  4 20:53 lib
lrwxr-xr-x  1 vladimir  admin    16B Jul  4 11:59 mechanize-2.9.1 -> mechanize-2.9.1/any advice would be appreciated.  | 
  
Beta Was this translation helpful? Give feedback.
      
      
          Answered by
          
            flavorjones
          
      
      
        Jul 5, 2023 
      
    
    Replies: 1 comment 1 reply
-
| 
         This seems like an issue with how homebrew is packaging the gem, and not with Mechanize itself. I'd like to suggest that you ask for help from the homebrew project.  | 
  
Beta Was this translation helpful? Give feedback.
                  
                    1 reply
                  
                
            
      Answer selected by
        kolchurinvv
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
This seems like an issue with how homebrew is packaging the gem, and not with Mechanize itself. I'd like to suggest that you ask for help from the homebrew project.