Lazy symbol binding failed about vscode-stylint

[szhu]

I spent about 2 hours today trying to figure this out…

Clue 1:
Note that the error message has this snippet:
Referenced from: .../node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node

Clue 2:
I googled around for things involving VSCode extensions, node modules, dyld: lazy symbol binding failed: Symbol not found:, and various combinations of these. Some of these mention that npm rebuild package-name can solve these dyld issues. Example: LinusU/node-appdmg#167 (comment)

Given the above, this is how I finally fixed it:
Step 1: rm -rf node_modules/fsevents/lib/binding/Release
Step 2: npm rebuild fsevents

🎉

[lukesUbuntu]

some reason the rebuild fsevents didn't work for me but removing and reinstalling fsevents resolved the issue for me. Thanks for the fix.

[szhu]

Sorry, I wasn't clear. The two bullets I gave above are steps, not options -- you must remove the offending file (or all of fsevents) before rebuilding. Edited my earlier comment for clarity.

[HaaLeo]

Thank you @szhu for digging into this and finding a fix. As soon as the vscode API exposes some functionality to read/check files on the filesystem I will replace the fs call with those.
For now I will publish a new release with a known issues section, mentioning this issue and the possible fix.
Thank you all for helping out.

[HaaLeo]

Hi @bzeffren-rms,
thank you for your report. Unfortunately I could not reproduce this behaviour (I can only check on a windows PC). After searching for that error message I found this question on Stackoverflow which seems to be very similar to your issue. So maybe another package causes this issue?
Sorry that I cannot provide more support, in solving this.
If you (or anybody else) finds a solution for this issue, please let us know in the comments.

[szhu]

Also have been getting this issue since around earlier this month. What's the easiest way to find out the exact command line stylint is running?

[HaaLeo]

@szhu Not quite sure what you mean. However the actual stylint call is built and executed in the validate() method. I think debugging the extension is the easiest way, to find out the exact command line stylint is running. To debug the extension check out the docs:

1. Checkout the repo
2. Run npm i in the root
3. In vscode launch the Launch Client debug configuration
4. In vscode launch the Attach to Server debug configuration

Further, I think this bug could be related to the Node.js update they introduced in the latest release of VScode, because of this issue using native node modules.
Also microsoft/vscode#68024 seems to be related to this.
Said that I think getting rid of the calls to fs.existsSync() here and here could fix it.
But also the usage of sb-exec could cause similar errors, because it only wraps the native node api.

[HaaLeo]

You could try whether uninstalling the extension and then reinstalling it fixes this as a workaround?