TypeError: Cannot read properties of undefined (reading 'prototype')
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- node.js
- Domain
- backend
Research direction
Reproduce the failure from MssqlMcp/Node/dist/index.js using Node v24 or later, then inspect the dependency path through jsonwebtoken, jwa, and buffer-equal-constant-time shown in the stack trace. Done means the MCP server starts without this TypeError on supported Node versions while retaining its existing behavior.
Written by the indexing model from the issue text.
Description
Running the MCP server with Node >= v24.x results in the following error (this capture is with Node v25.2.0):
❯ node /Users/me/Repositories/Clones/Microsoft/SQL-AI-samples/MssqlMcp/Node/dist/index.js
/Users/me/Repositories/Clones/Microsoft/SQL-AI-samples/MssqlMcp/Node/node_modules/buffer-equal-constant-time/index.js:37
var origSlowBufEqual = SlowBuffer.prototype.equal;
^
TypeError: Cannot read properties of undefined (reading 'prototype')
at Object. (/Users/me/Repositories/Clones/Microsoft/SQL-AI-samples/MssqlMcp/Node/node_modules/buffer-equal-constant-time/index.js:37:35)
at Module._compile (node:internal/modules/cjs/loader:1760:14)
at Object..js (node:internal/modules/cjs/loader:1892:10)
at Module.load (node:internal/modules/cjs/loader:1480:32)
at Module._load (node:internal/modules/cjs/loader:1299:12)
at TracingChannel.traceSync (node:diagnostics_channel:328:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:245:24)
at Module.require (node:internal/modules/cjs/loader:1503:12)
at require (node:internal/modules/helpers:152:16)
at Object. (/Users/me/Repositories/Clones/Microsoft/SQL-AI-samples/MssqlMcp/Node/node_modules/jsonwebtoken/node_modules/jwa/index.js:1:19)
I do not get this error with Node v23.11.0. See https://github.com/microsoft/vscode-vsce/issues/1139 for reference.
- Dominant language
- HTML
- Stars
- 331
- Forks
- 208
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure-Samples/SQL-AI-samples
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Azure-Samples/SQL-AI-samples#90 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Azure-Samples/SQL-AI-samples#79 · 6 reactions ·
-
Local db Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in Azure-Samples/SQL-AI-samples
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3312 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
needs-acceptance wg/data-plane-networking
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/semantic-router#4024 · 1 comment ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#165 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100