Typescript definitions in NPM are outdated

Description

It seems typescript definitions in NPM are outdated.

Run npm install mathlive@0.59.0

in node_modules/mathlive/dist/public/mathlive.d.ts file the definition is like this:

export declare function makeMathField(element: HTMLElement | string, options: MathfieldOptions): Mathfield;

It should be generated like so though:

export declare function makeMathField(element: HTMLElement | string, options?: Partial<MathfieldOptions>): Mathfield;

[arnog]

In general, MathLive supports the last two major versions of evergreen browsers. Unfortunately, supporting older browsers is not something within the reach of an unfunded open source project.

If your project require supporting older devices, you are more than welcome to keep using older versions of MathLive.

The benefits of web components were covered in #665:

• easier integration with UI libraries and frameworks, including reactive libraries
• encapsulation of the DOM elements and stylesheets used by the mathfield: as a web component implemented behind a shadow DOM, the DOM elements and styles of the component are invisible to the DOM outside of the element, and vice-versa, protecting from unwanted interaction between them
• simpler programming model built on top of standard DOM elements conventions, for example using 'content-did-change' events instead of onContentDidChange callbacks, or calling methods directly on the element, i.e. getElementById('mf').$latex('f(x) = x + 1')
• declarative syntax to configure a mathfield, for example: <math-field virtual-keyboard-mode="manual"></math-field>, while still supporting a programmatic way to create elements (i.e. new MathfieldElement({virtualKeyboardMode: "manual"}))
• proper handling of focusing, including properly respecting tabindex attribute (see #544)

[arnog]

Fixed in mathlive@0.60.0