BroadcomMFD / BroadcomMFD/explorer-for-endevor
Workspace synchronization fails with "l.isNullOrUndefined is not a function" error
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Explorer for Endevor The workspace synchronization from Source Control>Changes>Synchronize a Workspace fails with the following error: "Unable to synchronize workspace folder because of an error: l.isNullOrUndefined is not a function."
Issue seems to be due to a newer version of node.js packaged along with the latest vscode version.
VS Code version details on which this issue occurs:
Version: 1.124.0 (user setup)
Commit: 1b50d58d73426c9171299ec4037d01365d995b78
Date: 2026-06-09T21:29:32-07:00
Electron: 42.2.0
ElectronBuildId: 14159160
Chromium: 148.0.7778.97
Node.js: 24.15.0
V8: 14.8.178.14-electron.0
OS: Windows_NT x64 10.0.26200
Explorer for Endevor extension version: 1.11.4
Issue is resolved after switching to an older version of vscode as given below:
Version: 1.122.1 (user setup)
Commit: 8761a5560cfd65fdd19ce7e2bd18dab5c0a4d84e
Date: 2026-05-29T09:25:37+02:00
Electron: 39.8.8
ElectronBuildId: 13870025
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200
Regards,
Deepak
Contributor guide
No contributing guide indexed for this repository
Research direction
No source file or test is identified in the report. First reproduce workspace synchronization under VS Code 1.124.0 with Node.js 24.15.0, then compare it with VS Code 1.122.1 and Node.js 22.22.1 while tracing the synchronization entry point. Done means synchronization succeeds on the newer VS Code version without the isNullOrUndefined error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100