+ lHjRt^RIt^RIt^RIt^RIHt^RIHtRt]P!R4t ]P!R]P4t !RR] 4tRR ltR R ltR R ltRRltR#)aStdio MCP servers whose native addon was built for a different Node.js (#124264). Hermes runs every stdio MCP server on its own managed Node, never the user's. A server whose ``.node`` addon was compiled under another Node (typically through the ``~/.npm/_npx`` cache the user's ``npx`` shares with ours) dies at startup with ``NODE_MODULE_VERSION`` / ``ERR_DLOPEN_FAILED`` and only its stderr says so. This module turns that stderr into an error that names the remedy: rebuild the server under Hermes's Node. N)Path)Optionalz '([^'\n]+?\.node)'|(\S+?\.node):zJusing\s+NODE_MODULE_VERSION (\d+)\..*?requires\s+NODE_MODULE_VERSION (\d+)c]tRt^tRtRtR#)NodeAbiMismatchErrorzA stdio server's native addon does not load under Hermes's Node. Permanent: every retry loads the same binary, so the server parks until the user rebuilds it.N)__name__ __module__ __qualname____firstlineno____doc____static_attributes__r)BRBRBRI  i// 0bXbb sA AAchV^8dQhR\R\\\,\3,/#)r module_pathrr)rs"rrr$s( & &S &U8D>3+>%? &r c\V4Pp\V4UUu.uFwr#VR8XgKVNK pppV'dVR,^,\V48dR#VR,pW^,,pVP R4'd,V^,\V48dV RW^,, 2p\VRV!V3#uuppi)z``(project root, package name)`` owning *module_path*: the directory above its innermost ``node_modules`` and the (possibly scoped) package under it. node_modulesN@/r)rparts enumeratelen startswith)r#r)ipartmarksatpackages& r _package_ofr2$s   # #E'. I.71$.2HQQ.E I E"IMSZ/ rBFmG#26CJ#6IQu!V}o. s g %% Js C C c jV^8dQhR\\,R\R\R\R\/#)rrootr1nodenpmr)rrr)rs"rrr2s:NN(4.N3NdNN#Nr c\PR8HpV'dRMRpVeRV!V4 RV!V4 2MRpV'd3RV!\VP4R,4 R V!V4 R V 2pM!R V!VP4 R V!V4 R V 2pVfR V 2#VPPR8wdV#V'd RV!V4 2M RV!V4 2pV RV 2#)zThe fix in the host shell's syntax: delete an npx cache entry (Hermes's npx reinstalls it on the next start) or rebuild with Hermes's npm, Hermes's Node first on PATH because npm's shebang and its lifecycle scripts both run the first ``node`` there.ntcTR\V4PRR4,R,#)'z'')rreplaceps&r_remedy..7s3QT22S8r c@\P!\V44#N)shlexquoterr<s&rr>r?7sUZU`U`adefagUhr  z --prefix rz $env:Path = ;z + $env:Path; & z rebuildzPATH=z :"$PATH" z&in the server's package directory run _npxzRemove-Item -Recurse -Force zrm -rf z. (Hermes reinstalls it on the next start), or )osrrparent) r4r1r5r6windowsqtargetrebuilddeletes &&&& r_remedyrN2sggoG=D 8KhA484Dq7 Jqwi 0"F 3t{{#3c#9!: ;;KAcF8S[\b[cd!DKK.)QsVHHVHM |7yAA {{6!9@+AdG9 5PQRVPWyFYFXCG9 MMr cRV^8dQhR\R\R\\,/#)r server_name stderr_textr)rrr)rs"rrrEs,PPP#P(CW:XPr c aS'dI\;QJd#V3Rl\4F 'gK RM RM!V3Rl\44'gR#\PS4pV'd+VP ^4;'gVP ^4MRp\ PS4p\ R4wrV\ R4wrxV'dRV 2P4MR p V'd*R VP ^4 R V R VP ^4 2MR V 2p RT RT;'gR R2p VeVf\V RV R24#V'd \V4MRwr\V R\WWW4 24#)z_The remedy-naming error for a server whose stderr shows a native-addon load failure, else None.c3,<"TF qS9xK R#5irAr).0markerrQs& r !node_abi_error..Gs!SlFK"7lsTFNrr5r6zHermes's Node z Hermes's NodezNODE_MODULE_VERSION z; z needs zit does not load under z,native addon built for a different Node.js (z): zsee logs/mcp-stderr.logzF. Hermes runs MCP servers on its own Node; rebuild the server under itzP: install Hermes's Node with `hermes pm install npm`, then run `hermes mcp test `z: r) any _ABI_MARKERS _MODULE_PATHsearchgroup _ABI_VERSIONSr!striprr2rN)rPrQfoundmoduleversionsr5 node_versionr6_oursbuiltheadr4r1s&f rnode_abi_errorrhEs] cc!Sl!Sccc!Sl!SSS    ,E38ekk!n.. AbF##K0H!&)D e_FC6B^L> * 0 0 2D]e#HNN1$5#6bghnnUVFWEX Y+D62 ;5'VEhEhOhDijS SD |s{#tf-88C}A%GH H+1K'zMD 4&74$+L*M N OOr )NODE_MODULE_VERSIONERR_DLOPEN_FAILED)r rGrerBpathlibrtypingrrZcompiler[DOTALLr^ RuntimeErrorrr!r2rNrhrr rrqsl ; zz=>  hjljsjst N<N c &N&Pr