Problem with error "Invalid number of arguments, expected 0" when calling javascript method .toString(16)

Update:

this was actually a flaw in my code.

the .toString() methhod only allows a radix parameter on numbers not on other variable types.

var str = "16";
var hstr = str.toString(16); // causes the warning
// Result: '16'
// not what I actually expected

var num = 16;
var hnum = num.toString(16); // causes no warning
// Result: '10'
// what I actually expected

so the warning is just fine as it is :)

> the .toString() methhod only allows a radix parameter on numbers not on other variable types.

Not only numbers

buffer.toString([encoding[, start[, end]]])

Node 8 docs

you have to let WebStorm know explicitly what buffer type is

/**
 * @type {Buffer}
 */
let buffer;
buffer.toString(`base64`)

and, of course, Node.js Core library has to be enabled;

otherwise, Object toString() definition will be used

@Elena Pogorelova Why do we have to do anything? It's terrible IDE comparing to VS Code. Why we cannot exclude this and other warnings that is wrong by clicking in more actions? Why there's no such option?

How to disable it? I see it in vuex action inside of, for example in method: `vuexContext.commit('SET_PLAYERS_LIST', result)`,

You can suppress it for statement using comments, like

// noinspection JSCheckFunctionSignatures
const data54 = buffer.toString(`base64`)

I'm getting similar warning by creating new Map() - Invalid number of arguments, expected 1. Why is that I must provide arguments for creating Map? 

@Plart can't reproduce - no errors are shown for me

Can you repeat the issue in a new project?

Elena Pogorelova

Created new project (see screenshot with options), created empty test.js  -  the same (see screenshot)

can't reproduce:

please try ctrl+clicking on Map() in

const map = new Map();

- what definition are you taken to?

Problem has gone after updating to 2021.1 version