The problem:

// rcon.js, line 238

// Cannot be read by the module system
exports.default = RCON;

When converting this to use modules, I can finally read my server's status:

// rcon.js, line 238

module.exports = RCON;

I have recreated this issue by doing the following:

// app.js
const Rcon = require("rcon-srcds");

const server = new Rcon({
	host: "my.server.here"
});

(async () => {
	await server.authenticate("password");
	console.log(await server.execute("status"));
	return await server.disconnect();
})();

/*
Expects:
hostname: my_server_here
version : ...

Gets:
const server = new Rcon({
               ^

TypeError: Rcon is not a constructor
*/

Doing the same thing in TypeScript will not throw this error, since it the resulting code is compiled. Tested with same example as above, and it works as expected.

You can either use TypeScript, which is a superset of JavaScript, or modify the lines as decribed below.
To do this, you rename your app.js file to app.ts and use tsc app.js to compile the TypeScript file to JavaScript, and run that compiled file, which will work from my testing. This is a bit much to do if you need to convert a whole project to TypeScript, so a better solution is below.

The solution:
https://stackoverflow.com/questions/40294870/module-exports-vs-export-default-in-node-js-and-es6

Because this library is written in ES6, the tsc compiler converts the export default RCON to exports.default = RCON. This in turns makes the importing when using commonjs a bit different:

// Wrong
const Rcon = require('rcon-srcds');

// Right
const Rcon = require('rcon-srcds').default;

This isn't necessarily a bug with the library, just how tsc compiles the source code.

Rcon is not a constructor #13

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions