🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 74 (from laksa064)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa074.int.ahrefs:8124/' \
  -H 'Content-Type: text/plain' \
  -H 'X-ClickHouse-Database: crawler3' \
  -H 'Authorization: Basic YXBpOg==' \
  -d 'SELECT getAhrefsURLFromUnparsed(src_unparsed) AS found_url, ifNull(toUnixTimestamp(download_stamp), 0) AS crawl_time, ifNull(toUnixTimestamp(props_url_first_seen), 0) AS first_indexed_time, download_http_code AS http_code, src_unparsed AS src_unparsed, src_root_hash AS src_root_hash, history_drop_reason AS history_drop_reason, meta_title AS meta_title, meta_descriptions AS meta_descriptions, attrs_boilerpipe_text AS attrs_boilerpipe_text, attrs_markdown AS attrs_markdown, attrs_readable_markdown AS attrs_readable_markdown, meta_canonical AS meta_canonical FROM crawler3.page_info_local FINAL PREWHERE (src_root_hash, src_unparsed) IN ((getAhrefsRootHashFromUnparsed(getAhrefsUnparsedNoserviceFromURL(\'https://www.npmjs.com/package/node-simconnect\')), getAhrefsUnparsedNoserviceFromURL(\'https://www.npmjs.com/package/node-simconnect\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/www.npmjs.com\/package\/node-simconnect","crawl_time":1757310307,"first_indexed_time":1517038165,"http_code":200,"src_unparsed":"com,npmjs!www,\/package\/node-simconnect s443","src_root_hash":"1717991728988514674","history_drop_reason":null,"meta_title":"node-simconnect - npm","meta_descriptions":["A SimConnect client library for Node.JS.. Latest version: 4.0.0, last published: a year ago. Start using node-simconnect in your project by running `npm i node-simconnect`. There are 2 other projects in the npm registry using node-simconnect."],"attrs_boilerpipe_text":"A non-official SimConnect client library written in TypeScript. Lets you write Node.js applications that communicates directly with Microsoft Flight Simulator, FSX and Prepar3D without need for additional SDK files. Runs on Windows, Linux and Mac. This project is a port of the Java client library\n jsimconnect , originally written by\n lc0277 . Details about the protocol can be found on  lc0277's old website . A huge thanks to everyone involved in that project! 🙏 💡 Tip: check out the  msfs-simconnect-api-wrapper  which provides a more user-friendly wrapper around some of the  node-simconnect  APIs. npm install node-simconnect Check out the  \/samples  folder for example scripts. Refer to the  official SimConnect documentation  for comprehensive details on SimConnect APIs and usage. There are also  auto generated API-docs . You always start by calling  open(...)  which will attempt to open a connection with the SimConnect server (your flight simulator). If this succeeds you will get access to: recvOpen : contains simulator information handle : used for accessing the SimConnect APIs Example: import { open , Protocol } from 'node-simconnect' ; const EVENT_ID_PAUSE = 1 ; open ( 'My SimConnect client' , Protocol . FSX_SP2 ) . then ( function ( {  recvOpen ,  handle  } ) { console . log ( 'Connected to' , recvOpen . applicationName ) ; handle . on ( 'event' , function ( recvEvent ) { switch ( recvEvent . clientEventId ) { case EVENT_ID_PAUSE :\n                     console . log ( recvEvent . data === 1  ?  'Sim paused'  :  'Sim unpaused' ) ; break ; } } ) ; handle . on ( 'exception' , function ( recvException ) { console . log ( recvException ) ; } ) ; handle . on ( 'quit' , function ( ) { console . log ( 'Simulator quit' ) ; } ) ; handle . on ( 'close' , function ( ) { console . log ( 'Connection closed unexpectedly (simulator CTD?)' ) ; } ) ; handle . subscribeToSystemEvent ( EVENT_ID_PAUSE , 'Pause' ) ; } ) . catch ( function ( error ) { console . log ( 'Connection failed:' , error ) ; } ) ; node-simconnect vs the official API Most of the APIs described in the  official SimConnect documentation  are implemented in  node-simconnect . For information on how each feature works, please refer to the official documentation. Several new features have been added to the SimConnect API after the new Microsoft Flight Simulator was released, and more features are likely to come. Most of these will only be implemented on request. If you are missing any features in  node-simconnect  feel free to  open a new issue  or create a pull request. Prepar3D support and Prepar3D-only-features will not be prioritized. For a complete list of available API methods, please refer to the  SimConnectConnection  class. A major feature used by C\/C++\/C# implementation of SimConnect client libraries is the ability to directly cast a memory block to a user-defined structure. This is technically impossible to do in JavaScript or TypeScript since memory layout of classes and types are not accessible. Consequently, the wrapping\/unwrapping steps must be done by the user. Example using the official SimConnect SDK (C++): \/\/  C++ code \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ struct Struct1  {\n     double   kohlsmann;\n     double   altitude;\n     double   latitude;\n     double   longitude;\n     int      verticalSpeed;\n};\n\n \/\/  .... \n    hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1,  \" Kohlsman setting hg \" ,  \" inHg \" );\n    hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1,  \" Indicated Altitude \" ,  \" feet \" );\n    hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1,  \" Plane Latitude \" ,  \" degrees \" );\n    hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1,  \" Plane Longitude \" ,  \" degrees \" );\n    hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1,  \" VERTICAL SPEED \" ,  \" Feet per second \" , SimConnectDataType.INT32);\n\n     SimConnect_RequestDataOnSimObject (hSimConnect, REQUEST_1, DEFINITION_1, SIMCONNECT_OBJECT_ID_USER, SIMCONNECT_PERIOD_SECOND);\n \/\/  .... void  CALLBACK  MyDispatchProc (SIMCONNECT_RECV* pData, DWORD cbData) {\n     switch (pData-> dwID ) {\n         case  SIMCONNECT_RECV_ID_SIMOBJECT_DATA: {\n            SIMCONNECT_RECV_SIMOBJECT_DATA *pObjData = (SIMCONNECT_RECV_SIMOBJECT_DATA*) pData;\n             switch (pObjData-> dwRequestID ) {\n                 case  REQUEST_1:\n                    Struct1 *pS = (Struct1*)&pObjData-> dwData ;\n                     break ;\n                }\n             break ;\n        }\n    }\n} The code below demonstrates how the same is achieved with  node-simconnect : \/\/ TypeScript code \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ const REQUEST_1 = 0 ; const DEFINITION_1 = 0 ; \/\/ .... handle . addToDataDefinition ( DEFINITION_1 , 'Kohlsman setting hg' , 'inHg' , SimConnectDataType . FLOAT64 ) ; handle . addToDataDefinition ( DEFINITION_1 , 'Indicated Altitude' , 'feet' , SimConnectDataType . FLOAT64 ) ; handle . addToDataDefinition ( DEFINITION_1 , 'Plane Latitude' , 'degrees' , SimConnectDataType . FLOAT64 ) ; handle . addToDataDefinition ( DEFINITION_1 , 'Plane Longitude' , 'degrees' , SimConnectDataType . FLOAT64 ) ; handle . addToDataDefinition ( DEFINITION_1 , 'VERTICAL SPEED' , 'Feet per second' , SimConnectDataType . INT32 ) ; handle . requestDataOnSimObject ( REQUEST_1 , DEFINITION_1 , SimConnectConstants . OBJECT_ID_USER , SimConnectPeriod . SIM_FRAME ) ; \/\/ .... handle . on ( 'simObjectData' , recvSimObjectData => { switch ( recvSimObjectData . requestID ) { case REQUEST_1 :  { const receivedData = { \/\/ Read order is important! kohlsmann :  recvSimObjectData . data . readFloat64 ( ) , altitude :  recvSimObjectData . data . readFloat64 ( ) , latitude :  recvSimObjectData . data . readFloat64 ( ) , longitude :  recvSimObjectData . data . readFloat64 ( ) , verticalSpeed :  recvSimObjectData . data . readInt32 ( ) , } break ; } } } ) ; When the  simObjectData  callback is triggered, the  recvSimObjectData.data  is used to extract the requested simulation variables. These values are stored as a single continuous binary data chunk\/buffer, maintaining the order in which the simulation variables were added to the data definition. In this case, the buffer is 288 bits long (64 + 64 + 64 + 64 + 32), or 36 bytes. The  read...()  functions are used to extract each value individually. When the correct function is used, the reading \"cursor\" (offset) automatically moves after each read, positioning it at the beginning of the next value in the buffer. Consequently, it is crucial to ensure that the values are read in the same order and using the same data type as initially requested. If the Node.js application runs on the same computer as the flight simulator you don't need to worry about this part. To connect from an external computer you must configure SimConnect to accept connections from other hosts. This procedure is also described in the official docs, but here is the short version: Open  SimConnect.xml . FSX:  X:\\Users\\<USER>\\AppData\\Roaming\\Microsoft\\FSX MSFS:  X:\\Users\\<USER>\\AppData\\Local\\Packages\\Microsoft.FlightSimulator_**********\\LocalCache . Set property  <Address>0.0.0.0<\/Address> . Example of a working SimConnect.xml file: <? xml  version = \" 1.0 \"  encoding = \" Windows-1252 \" ?>\n< SimBase .Document  Type = \" SimConnect \" version = \" 1,0 \" >\n    < Filename >SimConnect.xml<\/ Filename >\n    < SimConnect .Comm>\n        < Protocol >IPv4<\/ Protocol >\n        < Scope >local<\/ Scope >\n        < Port >5111<\/ Port >\n        < MaxClients >64<\/ MaxClients >\n        < MaxRecvSize >41088<\/ MaxRecvSize >\n        < Address >0.0.0.0<\/ Address >\n    <\/ SimConnect .Comm>\n<\/ SimBase .Document> Connecting from a remote script can be done by providing the IP address of the flight simulator PC and the port number when calling  open : const options = { remote :  { host :  'localhost' , port :  5111 } } ; open ( 'My SimConnect client' , Protocol . FSX_SP2 , options ) . then ( \/* ... *\/ ) . catch ( \/* try again? *\/ ) ; Note that if no connection options are specified,  node-simconnect  will auto-discover connection details in the following order: Look for a  SimConnect.cfg  in the folder where Node.js is located. If the script is running in Electron, this will be the folder where the Electron executable is installed. Look for a  SimConnect.cfg  in the user's home directory ( %USERPROFILE% , eg.  C:\\Users\\<username> ) Look for a named pipe in the Windows registry, automatically set by the simulator Look for a port number in the Windows registry, automatically set by the simulator. node-simconnect will then connect to  localhost:<port> .","attrs_markdown":"skip to:[content](https:\/\/www.npmjs.com\/package\/node-simconnect#main)[package search](https:\/\/www.npmjs.com\/package\/node-simconnect#search)[sign in](https:\/\/www.npmjs.com\/package\/node-simconnect#signin)\n\n❤\n\n- [Pro](https:\/\/www.npmjs.com\/products\/pro)\n- [Teams](https:\/\/www.npmjs.com\/products\/teams)\n- [Pricing](https:\/\/www.npmjs.com\/products)\n- [Documentation](https:\/\/docs.npmjs.com\/)\n\nnpm\n\n[Sign Up](https:\/\/www.npmjs.com\/signup)[Sign In](https:\/\/www.npmjs.com\/login)\n\n## node-simconnect![TypeScript icon, indicating that this package has built-in type declarations](https:\/\/static-production.npmjs.com\/255a118f56f5346b97e56325a1217a16.svg)\n4\\.0.0 • Public\n\n• Published\n\na year ago\n\n- [Readme](https:\/\/www.npmjs.com\/package\/node-simconnect?activeTab=readme)\n- [Code Beta](https:\/\/www.npmjs.com\/package\/node-simconnect?activeTab=code)\n- [5 Dependencies](https:\/\/www.npmjs.com\/package\/node-simconnect?activeTab=dependencies)\n- [2 Dependents](https:\/\/www.npmjs.com\/package\/node-simconnect?activeTab=dependents)\n- [58 Versions](https:\/\/www.npmjs.com\/package\/node-simconnect?activeTab=versions)\n\n# node-simconnect\n[![npm version](https:\/\/badge.fury.io\/js\/node-simconnect.svg)](https:\/\/badge.fury.io\/js\/node-simconnect) [![Strict TypeScript Checked](https:\/\/badgen.net\/badge\/TS\/Strict)](https:\/\/www.typescriptlang.org\/)\n\nA non-official SimConnect client library written in TypeScript. Lets you write Node.js applications that communicates directly with Microsoft Flight Simulator, FSX and Prepar3D without need for additional SDK files. Runs on Windows, Linux and Mac.\n\nThis project is a port of the Java client library [jsimconnect](https:\/\/github.com\/mharj\/jsimconnect), originally written by [lc0277](https:\/\/www.fsdeveloper.com\/forum\/members\/lc0277.1581). Details about the protocol can be found on [lc0277's old website](http:\/\/web.archive.org\/web\/20090620063532\/http:\/\/lc0277.nerim.net\/jsimconnect\/doc\/flightsim\/simconnect\/package-summary.html#package_description). A huge thanks to everyone involved in that project! 🙏\n\n## Installation and use\n> 💡 Tip: check out the [msfs-simconnect-api-wrapper](https:\/\/www.npmjs.com\/package\/msfs-simconnect-api-wrapper) which provides a more user-friendly wrapper around some of the `node-simconnect` APIs.\n\n1. `npm install node-simconnect`\n2. Check out the [\/samples](https:\/\/github.com\/EvenAR\/node-simconnect\/tree\/master\/samples) folder for example scripts.\n3. Refer to the [official SimConnect documentation](https:\/\/docs.flightsimulator.com\/html\/Programming_Tools\/SimConnect\/SimConnect_API_Reference.htm) for comprehensive details on SimConnect APIs and usage.\n\nThere are also [auto generated API-docs](https:\/\/evenar.github.io\/node-simconnect\/).\n\n### Getting started\nYou always start by calling [`open(...)`](https:\/\/evenar.github.io\/node-simconnect\/functions\/open.html) which will attempt to open a connection with the SimConnect server (your flight simulator). If this succeeds you will get access to:\n\n- [`recvOpen`](https:\/\/evenar.github.io\/node-simconnect\/classes\/RecvOpen.html): contains simulator information\n- [`handle`](https:\/\/evenar.github.io\/node-simconnect\/classes\/SimConnectConnection.html): used for accessing the SimConnect APIs\n\nExample:\n```\nimport { open, Protocol } from 'node-simconnect';\n\nconst EVENT_ID_PAUSE = 1;\n\nopen('My SimConnect client', Protocol.FSX_SP2)\n    .then(function ({ recvOpen, handle }) {\n        console.log('Connected to', recvOpen.applicationName);\n\n        handle.on('event', function (recvEvent) {\n            switch (recvEvent.clientEventId) {\n                case EVENT_ID_PAUSE:\n                    console.log(recvEvent.data === 1 ? 'Sim paused' : 'Sim unpaused');\n                    break;\n            }\n        });\n        handle.on('exception', function (recvException) {\n            console.log(recvException);\n        });\n        handle.on('quit', function () {\n            console.log('Simulator quit');\n        });\n        handle.on('close', function () {\n            console.log('Connection closed unexpectedly (simulator CTD?)');\n        });\n\n        handle.subscribeToSystemEvent(EVENT_ID_PAUSE, 'Pause');\n    })\n    .catch(function (error) {\n        console.log('Connection failed:', error);\n    });\n```\n## node-simconnect vs the official API\n### Supported APIs\nMost of the APIs described in the [official SimConnect documentation](https:\/\/docs.flightsimulator.com\/html\/Programming_Tools\/SimConnect\/SimConnect_API_Reference.htm) are implemented in `node-simconnect`. For information on how each feature works, please refer to the official documentation.\n\nSeveral new features have been added to the SimConnect API after the new Microsoft Flight Simulator was released, and more features are likely to come. Most of these will only be implemented on request. If you are missing any features in `node-simconnect` feel free to [open a new issue](https:\/\/github.com\/EvenAR\/node-simconnect\/issues) or create a pull request.\n\nPrepar3D support and Prepar3D-only-features will not be prioritized.\n\nFor a complete list of available API methods, please refer to the [`SimConnectConnection`](https:\/\/evenar.github.io\/node-simconnect\/classes\/SimConnectConnection.html) class.\n\n### Data unwrapping\nA major feature used by C\/C++\/C\\# implementation of SimConnect client libraries is the ability to directly cast a memory block to a user-defined structure. This is technically impossible to do in JavaScript or TypeScript since memory layout of classes and types are not accessible. Consequently, the wrapping\/unwrapping steps must be done by the user.\n\nExample using the official SimConnect SDK (C++):\n```\n\/\/ C++ code \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\n\nstruct Struct1 {\n    double  kohlsmann;\n    double  altitude;\n    double  latitude;\n    double  longitude;\n    int     verticalSpeed;\n};\n\n\/\/ ....\n    hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1, \"Kohlsman setting hg\", \"inHg\");\n    hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1, \"Indicated Altitude\", \"feet\");\n    hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1, \"Plane Latitude\", \"degrees\");\n    hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1, \"Plane Longitude\", \"degrees\");\n    hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1, \"VERTICAL SPEED\", \"Feet per second\", SimConnectDataType.INT32);\n\n    SimConnect_RequestDataOnSimObject(hSimConnect, REQUEST_1, DEFINITION_1, SIMCONNECT_OBJECT_ID_USER, SIMCONNECT_PERIOD_SECOND);\n\/\/ ....\n\nvoid CALLBACK MyDispatchProc(SIMCONNECT_RECV* pData, DWORD cbData) {\n    switch(pData->dwID) {\n        case SIMCONNECT_RECV_ID_SIMOBJECT_DATA: {\n            SIMCONNECT_RECV_SIMOBJECT_DATA *pObjData = (SIMCONNECT_RECV_SIMOBJECT_DATA*) pData;\n            switch(pObjData->dwRequestID) {\n                case REQUEST_1:\n                    Struct1 *pS = (Struct1*)&pObjData->dwData;\n                    break;\n                }\n            break;\n        }\n    }\n}\n```\nThe code below demonstrates how the same is achieved with `node-simconnect`:\n```\n\/\/ TypeScript code \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\n\nconst REQUEST_1 = 0;\nconst DEFINITION_1 = 0;\n\/\/ ....\nhandle.addToDataDefinition(DEFINITION_1, 'Kohlsman setting hg', 'inHg', SimConnectDataType.FLOAT64);\nhandle.addToDataDefinition(DEFINITION_1, 'Indicated Altitude', 'feet', SimConnectDataType.FLOAT64);\nhandle.addToDataDefinition(DEFINITION_1, 'Plane Latitude', 'degrees', SimConnectDataType.FLOAT64);\nhandle.addToDataDefinition(DEFINITION_1, 'Plane Longitude', 'degrees', SimConnectDataType.FLOAT64);\nhandle.addToDataDefinition(DEFINITION_1, 'VERTICAL SPEED', 'Feet per second', SimConnectDataType.INT32);\n\nhandle.requestDataOnSimObject(REQUEST_1, DEFINITION_1, SimConnectConstants.OBJECT_ID_USER, SimConnectPeriod.SIM_FRAME);\n\n\/\/ ....\nhandle.on('simObjectData', recvSimObjectData => {\n    switch (recvSimObjectData.requestID) {\n        case REQUEST_1: {\n            const receivedData = {\n                \/\/ Read order is important!\n                kohlsmann: recvSimObjectData.data.readFloat64(),\n                altitude: recvSimObjectData.data.readFloat64(),\n                latitude: recvSimObjectData.data.readFloat64(),\n                longitude: recvSimObjectData.data.readFloat64(),\n                verticalSpeed: recvSimObjectData.data.readInt32(),\n            }\n            break;\n        }\n    }\n});\n```\nWhen the `simObjectData` callback is triggered, the `recvSimObjectData.data` is used to extract the requested simulation variables. These values are stored as a single continuous binary data chunk\/buffer, maintaining the order in which the simulation variables were added to the data definition. In this case, the buffer is 288 bits long (64 + 64 + 64 + 64 + 32), or 36 bytes.\n\nThe `read...()` functions are used to extract each value individually. When the correct function is used, the reading \"cursor\" (offset) automatically moves after each read, positioning it at the beginning of the next value in the buffer. Consequently, it is crucial to ensure that the values are read in the same order and using the same data type as initially requested.\n\n## Running over network?\nIf the Node.js application runs on the same computer as the flight simulator you don't need to worry about this part.\n\nTo connect from an external computer you must configure SimConnect to accept connections from other hosts. This procedure is also described in the official docs, but here is the short version:\n\n1. Open `SimConnect.xml`.\n   - FSX: `X:\\Users\\<USER>\\AppData\\Roaming\\Microsoft\\FSX`\n   - MSFS: `X:\\Users\\<USER>\\AppData\\Local\\Packages\\Microsoft.FlightSimulator_**********\\LocalCache`.\n2. Set property `<Address>0.0.0.0<\/Address>`. Example of a working SimConnect.xml file:\n   ```\n   <?xml version=\"1.0\" encoding=\"Windows-1252\"?>\n<SimBase.Document Type=\"SimConnect\" version=\"1,0\">\n    <Filename>SimConnect.xml<\/Filename>\n    <SimConnect.Comm>\n        <Protocol>IPv4<\/Protocol>\n        <Scope>local<\/Scope>\n        <Port>5111<\/Port>\n        <MaxClients>64<\/MaxClients>\n        <MaxRecvSize>41088<\/MaxRecvSize>\n        <Address>0.0.0.0<\/Address>\n    <\/SimConnect.Comm>\n<\/SimBase.Document>\n   ```\n\nConnecting from a remote script can be done by providing the IP address of the flight simulator PC and the port number when calling `open`:\n```\nconst options = { remote: { host: 'localhost', port: 5111 } };\n\nopen('My SimConnect client', Protocol.FSX_SP2, options).then(\/* ... *\/).catch(\/* try again? *\/);\n```\nNote that if no connection options are specified, `node-simconnect` will auto-discover connection details in the following order:\n\n1. Look for a [`SimConnect.cfg`](https:\/\/docs.flightsimulator.com\/html\/Programming_Tools\/SimConnect\/SimConnect_CFG_Definition.htm) in the folder where Node.js is located. If the script is running in Electron, this will be the folder where the Electron executable is installed.\n2. Look for a [`SimConnect.cfg`](https:\/\/docs.flightsimulator.com\/html\/Programming_Tools\/SimConnect\/SimConnect_CFG_Definition.htm) in the user's home directory (`%USERPROFILE%`, eg. `C:\\Users\\<username>`)\n3. Look for a named pipe in the Windows registry, automatically set by the simulator\n4. Look for a port number in the Windows registry, automatically set by the simulator. node-simconnect will then connect to `localhost:<port>`.\n\n## Readme\n### Keywords\n- [FSX](https:\/\/www.npmjs.com\/search?q=keywords:FSX)\n- [P3D](https:\/\/www.npmjs.com\/search?q=keywords:P3D)\n- [SDK](https:\/\/www.npmjs.com\/search?q=keywords:SDK)\n- [SimConnect](https:\/\/www.npmjs.com\/search?q=keywords:SimConnect)\n- [Prepar3D](https:\/\/www.npmjs.com\/search?q=keywords:Prepar3D)\n- [FlightSimulator](https:\/\/www.npmjs.com\/search?q=keywords:FlightSimulator)\n- [Simulator](https:\/\/www.npmjs.com\/search?q=keywords:Simulator)\n\n## Package Sidebar\n### Install\n`npm i node-simconnect`\n\n### Repository\n[github.com\/EvenAR\/node-simconnect](https:\/\/github.com\/EvenAR\/node-simconnect)\n\n### Homepage\n[github.com\/EvenAR\/node-simconnect\\#readme](https:\/\/github.com\/EvenAR\/node-simconnect#readme)\n\n### Weekly Downloads\n60\n\n### Version\n4\\.0.0\n\n### License\nLGPL-3.0-or-later\n\n### Unpacked Size\n642 kB\n\n### Total Files\n278\n\n### Last publish\na year ago\n\n### Collaborators\n- [![evenar](https:\/\/www.npmjs.com\/npm-avatar\/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdmF0YXJVUkwiOiJodHRwczovL3MuZ3JhdmF0YXIuY29tL2F2YXRhci9hMzIzNWY3NDRhMTc2Mjg1OWIwNzY3NTM2Yjk0ZTIzYz9zaXplPTEwMCZkZWZhdWx0PXJldHJvIn0.Q59jEsEp6o2zSNZP1VpjLEW7A71g8K1ieOVyZMX3e0w)](https:\/\/www.npmjs.com\/~evenar)\n\n[**Try** on RunKit](https:\/\/runkit.com\/npm\/node-simconnect)\n\n[**Report** malware](https:\/\/www.npmjs.com\/support?inquire=security&security-inquire=malware&package=node-simconnect&version=4.0.0)\n\n## Footer\n### Support\n- [Help](https:\/\/docs.npmjs.com\/)\n- [Advisories](https:\/\/github.com\/advisories)\n- [Status](http:\/\/status.npmjs.org\/)\n- [Contact npm](https:\/\/www.npmjs.com\/support)\n\n### Company\n- [About](https:\/\/www.npmjs.com\/about)\n- [Blog](https:\/\/github.blog\/tag\/npm\/)\n- [Press](https:\/\/www.npmjs.com\/press)\n\n### Terms & Policies\n- [Policies](https:\/\/www.npmjs.com\/policies\/)\n- [Terms of Use](https:\/\/www.npmjs.com\/policies\/terms)\n- [Code of Conduct](https:\/\/www.npmjs.com\/policies\/conduct)\n- [Privacy](https:\/\/www.npmjs.com\/policies\/privacy)","attrs_readable_markdown":null,"meta_canonical":null}

3. Robots.txt Check

Query:

Response:

4. Spam/Ban Check

Query:

Response:

5. Seen Status Check

ℹ️ Skipped - page is already crawled

🚫

NOT INDEXABLE

✅

CRAWLED

7 months ago

🤖

ROBOTS ALLOWED

Page Info Filters

Filter	Status	Condition	Details
HTTP status	PASS	`download_http_code = 200`	HTTP 200
Age cutoff	FAIL	`download_stamp > now() - 6 MONTH`	7.4 months ago
History drop	PASS	`isNull(history_drop_reason)`	No drop reason
Spam/ban	PASS	`fh_dont_index != 1 AND ml_spam_score = 0`	ml_spam_score=0
Canonical	PASS	`meta_canonical IS NULL OR = '' OR = src_unparsed`	Not set

Page Details

Property	Value
URL	https://www.npmjs.com/package/node-simconnect
Last Crawled	2025-09-08 05:45:07 (7 months ago)
First Indexed	2018-01-27 07:29:25 (8 years ago)
HTTP Status Code	200
Meta Title	node-simconnect - npm
Meta Description	A SimConnect client library for Node.JS.. Latest version: 4.0.0, last published: a year ago. Start using node-simconnect in your project by running `npm i node-simconnect`. There are 2 other projects in the npm registry using node-simconnect.
Meta Canonical	null
Boilerpipe Text	A non-official SimConnect client library written in TypeScript. Lets you write Node.js applications that communicates directly with Microsoft Flight Simulator, FSX and Prepar3D without need for additional SDK files. Runs on Windows, Linux and Mac. This project is a port of the Java client library jsimconnect , originally written by lc0277 . Details about the protocol can be found on lc0277's old website . A huge thanks to everyone involved in that project! 🙏 💡 Tip: check out the msfs-simconnect-api-wrapper which provides a more user-friendly wrapper around some of the node-simconnect APIs. npm install node-simconnect Check out the /samples folder for example scripts. Refer to the official SimConnect documentation for comprehensive details on SimConnect APIs and usage. There are also auto generated API-docs . You always start by calling open(...) which will attempt to open a connection with the SimConnect server (your flight simulator). If this succeeds you will get access to: recvOpen : contains simulator information handle : used for accessing the SimConnect APIs Example: import { open , Protocol } from 'node-simconnect' ; const EVENT_ID_PAUSE = 1 ; open ( 'My SimConnect client' , Protocol . FSX_SP2 ) . then ( function ( { recvOpen , handle } ) { console . log ( 'Connected to' , recvOpen . applicationName ) ; handle . on ( 'event' , function ( recvEvent ) { switch ( recvEvent . clientEventId ) { case EVENT_ID_PAUSE : console . log ( recvEvent . data === 1 ? 'Sim paused' : 'Sim unpaused' ) ; break ; } } ) ; handle . on ( 'exception' , function ( recvException ) { console . log ( recvException ) ; } ) ; handle . on ( 'quit' , function ( ) { console . log ( 'Simulator quit' ) ; } ) ; handle . on ( 'close' , function ( ) { console . log ( 'Connection closed unexpectedly (simulator CTD?)' ) ; } ) ; handle . subscribeToSystemEvent ( EVENT_ID_PAUSE , 'Pause' ) ; } ) . catch ( function ( error ) { console . log ( 'Connection failed:' , error ) ; } ) ; node-simconnect vs the official API Most of the APIs described in the official SimConnect documentation are implemented in node-simconnect . For information on how each feature works, please refer to the official documentation. Several new features have been added to the SimConnect API after the new Microsoft Flight Simulator was released, and more features are likely to come. Most of these will only be implemented on request. If you are missing any features in node-simconnect feel free to open a new issue or create a pull request. Prepar3D support and Prepar3D-only-features will not be prioritized. For a complete list of available API methods, please refer to the SimConnectConnection class. A major feature used by C/C++/C# implementation of SimConnect client libraries is the ability to directly cast a memory block to a user-defined structure. This is technically impossible to do in JavaScript or TypeScript since memory layout of classes and types are not accessible. Consequently, the wrapping/unwrapping steps must be done by the user. Example using the official SimConnect SDK (C++): // C++ code //////////////////// struct Struct1 { double kohlsmann; double altitude; double latitude; double longitude; int verticalSpeed; }; // .... hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1, " Kohlsman setting hg " , " inHg " ); hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1, " Indicated Altitude " , " feet " ); hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1, " Plane Latitude " , " degrees " ); hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1, " Plane Longitude " , " degrees " ); hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1, " VERTICAL SPEED " , " Feet per second " , SimConnectDataType.INT32); SimConnect_RequestDataOnSimObject (hSimConnect, REQUEST_1, DEFINITION_1, SIMCONNECT_OBJECT_ID_USER, SIMCONNECT_PERIOD_SECOND); // .... void CALLBACK MyDispatchProc (SIMCONNECT_RECV* pData, DWORD cbData) { switch (pData-> dwID ) { case SIMCONNECT_RECV_ID_SIMOBJECT_DATA: { SIMCONNECT_RECV_SIMOBJECT_DATA pObjData = (SIMCONNECT_RECV_SIMOBJECT_DATA) pData; switch (pObjData-> dwRequestID ) { case REQUEST_1: Struct1 pS = (Struct1)&pObjData-> dwData ; break ; } break ; } } } The code below demonstrates how the same is achieved with node-simconnect : // TypeScript code //////////////////// const REQUEST_1 = 0 ; const DEFINITION_1 = 0 ; // .... handle . addToDataDefinition ( DEFINITION_1 , 'Kohlsman setting hg' , 'inHg' , SimConnectDataType . FLOAT64 ) ; handle . addToDataDefinition ( DEFINITION_1 , 'Indicated Altitude' , 'feet' , SimConnectDataType . FLOAT64 ) ; handle . addToDataDefinition ( DEFINITION_1 , 'Plane Latitude' , 'degrees' , SimConnectDataType . FLOAT64 ) ; handle . addToDataDefinition ( DEFINITION_1 , 'Plane Longitude' , 'degrees' , SimConnectDataType . FLOAT64 ) ; handle . addToDataDefinition ( DEFINITION_1 , 'VERTICAL SPEED' , 'Feet per second' , SimConnectDataType . INT32 ) ; handle . requestDataOnSimObject ( REQUEST_1 , DEFINITION_1 , SimConnectConstants . OBJECT_ID_USER , SimConnectPeriod . SIM_FRAME ) ; // .... handle . on ( 'simObjectData' , recvSimObjectData => { switch ( recvSimObjectData . requestID ) { case REQUEST_1 : { const receivedData = { // Read order is important! kohlsmann : recvSimObjectData . data . readFloat64 ( ) , altitude : recvSimObjectData . data . readFloat64 ( ) , latitude : recvSimObjectData . data . readFloat64 ( ) , longitude : recvSimObjectData . data . readFloat64 ( ) , verticalSpeed : recvSimObjectData . data . readInt32 ( ) , } break ; } } } ) ; When the simObjectData callback is triggered, the recvSimObjectData.data is used to extract the requested simulation variables. These values are stored as a single continuous binary data chunk/buffer, maintaining the order in which the simulation variables were added to the data definition. In this case, the buffer is 288 bits long (64 + 64 + 64 + 64 + 32), or 36 bytes. The read...() functions are used to extract each value individually. When the correct function is used, the reading "cursor" (offset) automatically moves after each read, positioning it at the beginning of the next value in the buffer. Consequently, it is crucial to ensure that the values are read in the same order and using the same data type as initially requested. If the Node.js application runs on the same computer as the flight simulator you don't need to worry about this part. To connect from an external computer you must configure SimConnect to accept connections from other hosts. This procedure is also described in the official docs, but here is the short version: Open SimConnect.xml . FSX: X:\Users\<USER>\AppData\Roaming\Microsoft\FSX MSFS: X:\Users\<USER>\AppData\Local\Packages\Microsoft.FlightSimulator_*********\LocalCache . Set property <Address>0.0.0.0</Address> . Example of a working SimConnect.xml file: <? xml version = " 1.0 " encoding = " Windows-1252 " ?> < SimBase .Document Type = " SimConnect " version = " 1,0 " > < Filename >SimConnect.xml</ Filename > < SimConnect .Comm> < Protocol >IPv4</ Protocol > < Scope >local</ Scope > < Port >5111</ Port > < MaxClients >64</ MaxClients > < MaxRecvSize >41088</ MaxRecvSize > < Address >0.0.0.0</ Address > </ SimConnect .Comm> </ SimBase .Document> Connecting from a remote script can be done by providing the IP address of the flight simulator PC and the port number when calling open : const options = { remote : { host : 'localhost' , port : 5111 } } ; open ( 'My SimConnect client' , Protocol . FSX_SP2 , options ) . then ( / ... / ) . catch ( / try again? */ ) ; Note that if no connection options are specified, node-simconnect will auto-discover connection details in the following order: Look for a SimConnect.cfg in the folder where Node.js is located. If the script is running in Electron, this will be the folder where the Electron executable is installed. Look for a SimConnect.cfg in the user's home directory ( %USERPROFILE% , eg. C:\Users\<username> ) Look for a named pipe in the Windows registry, automatically set by the simulator Look for a port number in the Windows registry, automatically set by the simulator. node-simconnect will then connect to localhost:<port> .
Markdown	skip to:[content](https://www.npmjs.com/package/node-simconnect#main)[package search](https://www.npmjs.com/package/node-simconnect#search)[sign in](https://www.npmjs.com/package/node-simconnect#signin) ❤ - [Pro](https://www.npmjs.com/products/pro) - [Teams](https://www.npmjs.com/products/teams) - [Pricing](https://www.npmjs.com/products) - [Documentation](https://docs.npmjs.com/) npm [Sign Up](https://www.npmjs.com/signup)[Sign In](https://www.npmjs.com/login) ## node-simconnect![TypeScript icon, indicating that this package has built-in type declarations](https://static-production.npmjs.com/255a118f56f5346b97e56325a1217a16.svg) 4\.0.0 • Public • Published a year ago - [Readme](https://www.npmjs.com/package/node-simconnect?activeTab=readme) - [Code Beta](https://www.npmjs.com/package/node-simconnect?activeTab=code) - [5 Dependencies](https://www.npmjs.com/package/node-simconnect?activeTab=dependencies) - [2 Dependents](https://www.npmjs.com/package/node-simconnect?activeTab=dependents) - [58 Versions](https://www.npmjs.com/package/node-simconnect?activeTab=versions) # node-simconnect [![npm version](https://badge.fury.io/js/node-simconnect.svg)](https://badge.fury.io/js/node-simconnect) [![Strict TypeScript Checked](https://badgen.net/badge/TS/Strict)](https://www.typescriptlang.org/) A non-official SimConnect client library written in TypeScript. Lets you write Node.js applications that communicates directly with Microsoft Flight Simulator, FSX and Prepar3D without need for additional SDK files. Runs on Windows, Linux and Mac. This project is a port of the Java client library [jsimconnect](https://github.com/mharj/jsimconnect), originally written by [lc0277](https://www.fsdeveloper.com/forum/members/lc0277.1581). Details about the protocol can be found on [lc0277's old website](http://web.archive.org/web/20090620063532/http://lc0277.nerim.net/jsimconnect/doc/flightsim/simconnect/package-summary.html#package_description). A huge thanks to everyone involved in that project! 🙏 ## Installation and use > 💡 Tip: check out the [msfs-simconnect-api-wrapper](https://www.npmjs.com/package/msfs-simconnect-api-wrapper) which provides a more user-friendly wrapper around some of the `node-simconnect` APIs. 1. `npm install node-simconnect` 2. Check out the [/samples](https://github.com/EvenAR/node-simconnect/tree/master/samples) folder for example scripts. 3. Refer to the [official SimConnect documentation](https://docs.flightsimulator.com/html/Programming_Tools/SimConnect/SimConnect_API_Reference.htm) for comprehensive details on SimConnect APIs and usage. There are also [auto generated API-docs](https://evenar.github.io/node-simconnect/). ### Getting started You always start by calling [`open(...)`](https://evenar.github.io/node-simconnect/functions/open.html) which will attempt to open a connection with the SimConnect server (your flight simulator). If this succeeds you will get access to: - [`recvOpen`](https://evenar.github.io/node-simconnect/classes/RecvOpen.html): contains simulator information - [`handle`](https://evenar.github.io/node-simconnect/classes/SimConnectConnection.html): used for accessing the SimConnect APIs Example: ``` import { open, Protocol } from 'node-simconnect'; const EVENT_ID_PAUSE = 1; open('My SimConnect client', Protocol.FSX_SP2) .then(function ({ recvOpen, handle }) { console.log('Connected to', recvOpen.applicationName); handle.on('event', function (recvEvent) { switch (recvEvent.clientEventId) { case EVENT_ID_PAUSE: console.log(recvEvent.data === 1 ? 'Sim paused' : 'Sim unpaused'); break; } }); handle.on('exception', function (recvException) { console.log(recvException); }); handle.on('quit', function () { console.log('Simulator quit'); }); handle.on('close', function () { console.log('Connection closed unexpectedly (simulator CTD?)'); }); handle.subscribeToSystemEvent(EVENT_ID_PAUSE, 'Pause'); }) .catch(function (error) { console.log('Connection failed:', error); }); ``` ## node-simconnect vs the official API ### Supported APIs Most of the APIs described in the [official SimConnect documentation](https://docs.flightsimulator.com/html/Programming_Tools/SimConnect/SimConnect_API_Reference.htm) are implemented in `node-simconnect`. For information on how each feature works, please refer to the official documentation. Several new features have been added to the SimConnect API after the new Microsoft Flight Simulator was released, and more features are likely to come. Most of these will only be implemented on request. If you are missing any features in `node-simconnect` feel free to [open a new issue](https://github.com/EvenAR/node-simconnect/issues) or create a pull request. Prepar3D support and Prepar3D-only-features will not be prioritized. For a complete list of available API methods, please refer to the [`SimConnectConnection`](https://evenar.github.io/node-simconnect/classes/SimConnectConnection.html) class. ### Data unwrapping A major feature used by C/C++/C\# implementation of SimConnect client libraries is the ability to directly cast a memory block to a user-defined structure. This is technically impossible to do in JavaScript or TypeScript since memory layout of classes and types are not accessible. Consequently, the wrapping/unwrapping steps must be done by the user. Example using the official SimConnect SDK (C++): ``` // C++ code //////////////////// struct Struct1 { double kohlsmann; double altitude; double latitude; double longitude; int verticalSpeed; }; // .... hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1, "Kohlsman setting hg", "inHg"); hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1, "Indicated Altitude", "feet"); hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1, "Plane Latitude", "degrees"); hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1, "Plane Longitude", "degrees"); hr = SimConnect_AddToDataDefinition(hSimConnect, DEFINITION_1, "VERTICAL SPEED", "Feet per second", SimConnectDataType.INT32); SimConnect_RequestDataOnSimObject(hSimConnect, REQUEST_1, DEFINITION_1, SIMCONNECT_OBJECT_ID_USER, SIMCONNECT_PERIOD_SECOND); // .... void CALLBACK MyDispatchProc(SIMCONNECT_RECV* pData, DWORD cbData) { switch(pData->dwID) { case SIMCONNECT_RECV_ID_SIMOBJECT_DATA: { SIMCONNECT_RECV_SIMOBJECT_DATA pObjData = (SIMCONNECT_RECV_SIMOBJECT_DATA) pData; switch(pObjData->dwRequestID) { case REQUEST_1: Struct1 pS = (Struct1)&pObjData->dwData; break; } break; } } } ``` The code below demonstrates how the same is achieved with `node-simconnect`: ``` // TypeScript code //////////////////// const REQUEST_1 = 0; const DEFINITION_1 = 0; // .... handle.addToDataDefinition(DEFINITION_1, 'Kohlsman setting hg', 'inHg', SimConnectDataType.FLOAT64); handle.addToDataDefinition(DEFINITION_1, 'Indicated Altitude', 'feet', SimConnectDataType.FLOAT64); handle.addToDataDefinition(DEFINITION_1, 'Plane Latitude', 'degrees', SimConnectDataType.FLOAT64); handle.addToDataDefinition(DEFINITION_1, 'Plane Longitude', 'degrees', SimConnectDataType.FLOAT64); handle.addToDataDefinition(DEFINITION_1, 'VERTICAL SPEED', 'Feet per second', SimConnectDataType.INT32); handle.requestDataOnSimObject(REQUEST_1, DEFINITION_1, SimConnectConstants.OBJECT_ID_USER, SimConnectPeriod.SIM_FRAME); // .... handle.on('simObjectData', recvSimObjectData => { switch (recvSimObjectData.requestID) { case REQUEST_1: { const receivedData = { // Read order is important! kohlsmann: recvSimObjectData.data.readFloat64(), altitude: recvSimObjectData.data.readFloat64(), latitude: recvSimObjectData.data.readFloat64(), longitude: recvSimObjectData.data.readFloat64(), verticalSpeed: recvSimObjectData.data.readInt32(), } break; } } }); ``` When the `simObjectData` callback is triggered, the `recvSimObjectData.data` is used to extract the requested simulation variables. These values are stored as a single continuous binary data chunk/buffer, maintaining the order in which the simulation variables were added to the data definition. In this case, the buffer is 288 bits long (64 + 64 + 64 + 64 + 32), or 36 bytes. The `read...()` functions are used to extract each value individually. When the correct function is used, the reading "cursor" (offset) automatically moves after each read, positioning it at the beginning of the next value in the buffer. Consequently, it is crucial to ensure that the values are read in the same order and using the same data type as initially requested. ## Running over network? If the Node.js application runs on the same computer as the flight simulator you don't need to worry about this part. To connect from an external computer you must configure SimConnect to accept connections from other hosts. This procedure is also described in the official docs, but here is the short version: 1. Open `SimConnect.xml`. - FSX: `X:\Users\<USER>\AppData\Roaming\Microsoft\FSX` - MSFS: `X:\Users\<USER>\AppData\Local\Packages\Microsoft.FlightSimulator_*********\LocalCache`. 2. Set property `<Address>0.0.0.0</Address>`. Example of a working SimConnect.xml file: ``` <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="SimConnect" version="1,0"> <Filename>SimConnect.xml</Filename> <SimConnect.Comm> <Protocol>IPv4</Protocol> <Scope>local</Scope> <Port>5111</Port> <MaxClients>64</MaxClients> <MaxRecvSize>41088</MaxRecvSize> <Address>0.0.0.0</Address> </SimConnect.Comm> </SimBase.Document> ``` Connecting from a remote script can be done by providing the IP address of the flight simulator PC and the port number when calling `open`: ``` const options = { remote: { host: 'localhost', port: 5111 } }; open('My SimConnect client', Protocol.FSX_SP2, options).then(/ ... /).catch(/ try again? /); ``` Note that if no connection options are specified, `node-simconnect` will auto-discover connection details in the following order: 1. Look for a [`SimConnect.cfg`](https://docs.flightsimulator.com/html/Programming_Tools/SimConnect/SimConnect_CFG_Definition.htm) in the folder where Node.js is located. If the script is running in Electron, this will be the folder where the Electron executable is installed. 2. Look for a [`SimConnect.cfg`](https://docs.flightsimulator.com/html/Programming_Tools/SimConnect/SimConnect_CFG_Definition.htm) in the user's home directory (`%USERPROFILE%`, eg. `C:\Users\<username>`) 3. Look for a named pipe in the Windows registry, automatically set by the simulator 4. Look for a port number in the Windows registry, automatically set by the simulator. node-simconnect will then connect to `localhost:<port>`. ## Readme ### Keywords - [FSX](https://www.npmjs.com/search?q=keywords:FSX) - [P3D](https://www.npmjs.com/search?q=keywords:P3D) - [SDK](https://www.npmjs.com/search?q=keywords:SDK) - [SimConnect](https://www.npmjs.com/search?q=keywords:SimConnect) - [Prepar3D](https://www.npmjs.com/search?q=keywords:Prepar3D) - [FlightSimulator](https://www.npmjs.com/search?q=keywords:FlightSimulator) - [Simulator](https://www.npmjs.com/search?q=keywords:Simulator) ## Package Sidebar ### Install `npm i node-simconnect` ### Repository [github.com/EvenAR/node-simconnect](https://github.com/EvenAR/node-simconnect) ### Homepage [github.com/EvenAR/node-simconnect\#readme](https://github.com/EvenAR/node-simconnect#readme) ### Weekly Downloads 60 ### Version 4\.0.0 ### License LGPL-3.0-or-later ### Unpacked Size 642 kB ### Total Files 278 ### Last publish a year ago ### Collaborators - [![evenar](https://www.npmjs.com/npm-avatar/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdmF0YXJVUkwiOiJodHRwczovL3MuZ3JhdmF0YXIuY29tL2F2YXRhci9hMzIzNWY3NDRhMTc2Mjg1OWIwNzY3NTM2Yjk0ZTIzYz9zaXplPTEwMCZkZWZhdWx0PXJldHJvIn0.Q59jEsEp6o2zSNZP1VpjLEW7A71g8K1ieOVyZMX3e0w)](https://www.npmjs.com/~evenar) [Try* on RunKit](https://runkit.com/npm/node-simconnect) [Report malware](https://www.npmjs.com/support?inquire=security&security-inquire=malware&package=node-simconnect&version=4.0.0) ## Footer ### Support - [Help](https://docs.npmjs.com/) - [Advisories](https://github.com/advisories) - [Status](http://status.npmjs.org/) - [Contact npm](https://www.npmjs.com/support) ### Company - [About](https://www.npmjs.com/about) - [Blog](https://github.blog/tag/npm/) - [Press](https://www.npmjs.com/press) ### Terms & Policies - [Policies](https://www.npmjs.com/policies/) - [Terms of Use](https://www.npmjs.com/policies/terms) - [Code of Conduct](https://www.npmjs.com/policies/conduct) - [Privacy](https://www.npmjs.com/policies/privacy)
Readable Markdown	null
Shard	74 (laksa)
Root Hash	1717991728988514674
Unparsed URL	com,npmjs!www,/package/node-simconnect s443