A data handler for the VATSIM status system coded in JavaScript
| Check | Provider | Status |
|---|---|---|
| Build | TravisCI | |
| Coverage | Coveralls | |
| Discord | Discord | |
| Github Version | GitHub | |
| License | License |
npm install vatsim-data-handler
const {handler} = require('vatsim-data-handler');
handler.getSupervisors().then(val => console.log(val));This would log the number of clients connected to the VATSIM network
getCount(type)- Returns the number of connected clients, where type is the type of requested client. Available arguments are 'all', 'pilots' and 'controllers'getAirportInfo(airport)- Returns the details of pilots into or out of a certain airport along with the controllers controlling that airport, the airport argument is a 4 letter ICAO codegetPopularAirports()- Returns a list of the top 10 airports for arriving and departing aircraftgetFlightInfo(callsign)- Returns the details of a specific pilots flight, where callsign is a valid VATSIM callsign as a stringgetClients()- Returns a list of all connected clientsgetClientDetails(cid)- Returns the details of a specific pilots flight, where cid is a valid VATSIM cid as an integergetControllers()- Returns a list of all the controllers connected to VATSIMgetSupervisors()- Returns a list of all the supervisors/admins connected to VATSIM
on('newController')- Triggered when a new controller, or when new controllers, connect to the networkon('newPilot')- Triggered when a new pilot, or when new pilots, connect to the network
process.on("newController", (data) => {
console.log(data);
})This would log any new controllers, including observers, that connect to the VATSIM network.
getClientCount()- Returns the number of clients connected to the VATSIM network (Replaced bygetCount(type))getPilotCount()- Returns the number of pilots connected to the VATSIM network (Replaced bygetCount(type))getControllerCount()- Returns the number of controllers connected to the VATSIM network (Replaced bygetCount(type))
npm test
If you have any issues or feature requests, either create an issue or you can join my Discord Server.
In lieu of a formal style guide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code.