dyld: lazy symbol binding failed: Symbol not found: _node_module_register
See original GitHub issue❯ gulp scss-lint
dyld: lazy symbol binding failed: Symbol not found: _node_module_register
Referenced from: /Users/kevinsuttle/Code/XXX/node_modules/browser-sync/node_modules/socket.io/node_modules/engine.io/node_modules/ws/build/Release/bufferutil.node
Expected in: dynamic lookup
dyld: Symbol not found: _node_module_register
Referenced from: /Users/kevinsuttle/Code/XXX/node_modules/browser-sync/node_modules/socket.io/node_modules/engine.io/node_modules/ws/build/Release/bufferutil.node
Expected in: dynamic lookup
zsh: trace trap gulp scss-lint
No idea. This happens no matter what gulp task I run, and none of them depend on my browsers-sync task. In fact, it still happens even when I comment that task out.
Gulpfile
gulp.task('scss-lint', function() {
gulp.src('/scss/*.scss')
.pipe(scss-lint());
});
package.json
"devDependencies": {
"browser-sync": "^2.0.1",
"del": "^1.1.1",
"gulp": "^3.8.11",
"gulp-sass": "^1.3.2",
"gulp-scss-lint": "^0.1.6",
"gulp-size": "^1.2.0",
"psi": "^1.0.5",
"run-sequence": "^1.0.2",
"w3cjs": "^0.2.0"
}
I’ve had some weird issues with nvm lately. Wondering if that has something to do with it.
❯ node -v
v0.10.36
I deleted the browser-sync directory from node_modules. Then tried another gulp task.
❯ gulp watch
Error: Cannot find module 'browser-sync'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.<anonymous> (/Users/kevinsuttle/Code/XXX/gulpfile.js:8:15)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
Gulpfile.js
gulp.task('watch', function () {
gulp.watch('_sass/*.scss', ['styles']);
});
Deleted references to browser-sync in my package.json and gulpfile.
I uninstalled globally and locally in npm
.
❯ npm uninstall -g browser-sync
npm WARN uninstall not installed in /Users/kevinsuttle/.nvm/v0.10.36/lib/node_modules: "browser-sync"
~/Code/XXX master*
❯ npm uninstall browser-sync
npm WARN uninstall not installed in /Users/kevinsuttle/Code/XXX/node_modules: "browser-sync"
❯ gulp watch
ReferenceError: browserSync is not defined
at Object.<anonymous> (/Users/kevinsuttle/Code/XXX/gulpfile.js:8:10)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Liftoff.handleArguments (/usr/local/lib/node_modules/gulp/bin/gulp.js:116:3)
at Liftoff.<anonymous> (/usr/local/lib/node_modules/gulp/node_modules/liftoff/index.js:159:12)
at module.exports (/usr/local/lib/node_modules/gulp/node_modules/liftoff/node_modules/flagged-respawn/index.js:17:3)
Issue Analytics
- State:
- Created 9 years ago
- Reactions:1
- Comments:8
Top Results From Across the Web
node.js - dyld: lazy symbol binding failed: Symbol not found
Basically this error means - some binary packages was built under different node.js versions and not compatible to each other.
Read more >dyld: lazy symbol binding failed: Symbol not found ... - GitHub
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...
Read more >Dyld: Lazy Symbol Binding Failed: Symbol Not Found - ADocLib
I'm running into what appears to be a known issue with the macOS 10.13 SDK in Xcode 9 GM: dyld: lazy symbol binding...
Read more >Error dyld: lazy symbol binding failed: Symbol not found
Hi,. Im getting a error message while trying to run co-register. It worked fine on v2.1.7 but I updated to v.2.3.1 during the...
Read more >61406 (emacs @27.1_2+x11: dyld: lazy symbol binding failed
Hello,. I have so far been unable to build any version of Emacs 27 +x11. I keep getting this message during bootstrap build:...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Did you try delete the node_modules folder and run npm install again?
Because I had to do that right after I changed my node version with n.
I solved this problem by downgrading to node 4 LTS from 6