getBpm issues: documentation; d.ts; and so result of `renderAbc(...)[0].getBpm()`

environment:

Using typescript, which I think matters here for the code part of the issue
abcjs v6.4.1

When doing a test as follow:

abc (click to expand):

const renderOut = renderAbc(elem, tune.abc, {
  add_classes: true,
  responsive: 'resize',
} as AbcVisualParams);
const tuneObj = renderOut[0];

const bpm = tuneObj.getBpm();

Expected result: bpm === 80 Actual result: bpm === 180

From what I can work out...

From https://github.com/search?q=repo%3Apaulrosen%2Fabcjs+getBpm&type=code it looks like getBpm has an optional tempo parameter, and all calls to it should supply tempo from const tempo = tune.metaText ? tune.metaText.tempo : null; if they want to get the actual tempo for the tune (e.g. abc_timing_callbacks).
But getBpm in the d.ts doesn't show this optional parameter, so when you use the getBpm method in typescript the parameter ends up being undefined. This means the result ends up as the default value of 180, as per abc_tune.
This ties in to the documentation which says

This is the starting beats per minute. Tempo changes could appear later in the tune, but this is the value that was set with the Q: statement, or if that statement doesn't exist, it is the default tempo of 180.

which implies that we don't need to supply the tempo metaText to this function, when it looks like we do?

This all assumes I'm not incorrectly using renderAbc and getBpm from the elements of the renderAbc result.

paulrosen / abcjs

getBpm issues: documentation; d.ts; and so result of `renderAbc(...)[0].getBpm()` #1040