fsevents: dyld: lazy symbol binding failed: Symbol not found: _FSEventStreamCreate

I use @vue/cli 4.2.3 to build a vue project on my Mac, when running npm run serve, I got some error:

dyld: lazy symbol binding failed: Symbol not found: _FSEventStreamCreate
  Referenced from: /Users/bunnyxt/Projects/njauiot-frontend/node_modules/fsevents/build/Release/fse.node
  Expected in: flat namespace

dyld: Symbol not found: _FSEventStreamCreate
  Referenced from: /Users/bunnyxt/Projects/njauiot-frontend/node_modules/fsevents/build/Release/fse.node
  Expected in: flat namespace

Abort trap: 6

My system version is 10.15.3 (19D76). Actually, old projects created via vue-cli can still running, so I checked difference, found the new project has fsevents 1.2.12 and goes down, but old projects use 1.2.9 and works. I change version to 1.2.9 and no error comes. I wanna know why it happens.

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 8
Comments: 28 (6 by maintainers)

Most upvoted comments

Install Node JS (Version 11.10.0) and NPM (Version 6.7.0)

Doing that using NVM (installation process below): Run the installation file: curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh | bash atom the .bashrc to ensure it has the following shell script: export NVM_DIR="$([ -z "${XDG_CONFIG_HOME-}" ] && printf %s "${HOME}/.nvm" || printf %s "${XDG_CONFIG_HOME}/nvm")" [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm source .bashrc file using the following command: source ~/.bashrc You might need to do the source ~/.bashrc every time you trying to use the nvm command. You can add this script to the .bash_profile to ensure it is doing that each time. if [ -n "$BASH_VERSION" ] && [ -f $HOME/.bashrc ]; then source $HOME/.bashrc fi Check all available versions of Node nvm ls-remote Install NPM & Node by the following script nvm install 11.10.0

At this point I really think you should be good to go. I did that and it works for me when I run npm start

jliu419 on Jun 14, 2020

This command alone fixed my issue rm -rf node_modules && npm i --cache /tmp/tmp-cache

GabeAboy on Feb 23, 2021

Updating node to the latest 14.8.0 worked for me

brew update brew upgrade node

danilo-znamerovszkij on Aug 14, 2020

Just for the record in case anyone else is googling this: I was getting the exact same error message on MacOS 10.14.6 with XCode 11.3.1 (the last version compatible with MacOS 10.14).

What fixed it for me was making sure I had node upgraded to the latest version

george-carlin on Apr 23, 2020

(try re-doing npm install)

paulmillr on Apr 5, 2020

Ensure you have the latest xcode and command line tools in place

paulmillr on Apr 5, 2020

Worked by typing npm i chokidar@3.4.2 The problem is caused by chokidar version 2, and upgrade it to version 3 solved this issue.

jakehsiao on Apr 18, 2021

Tried ALL methods above but none of them work, still telling me that “dyld: lazy symbol binding failed: Symbol not found: _FSEventStreamCreate”. When I start a react app using “npx create-react-app” and “npm start”, everytime it got me this error message, it’s so strange that it’s not like that a month ago. But old react apps still work fine, just cannot start newer ones. The only way to start a react app right now is to copy an old react app.

jakehsiao on Apr 18, 2021

So, still having the error?

paulmillr on Apr 5, 2020