feat: Generate types declaration file

[jallamsetty1]

So that it can be imported in packages that use js-utils for type infomation.

[Copilot]

Pull Request Overview

This PR introduces a types declaration file by adding a TypeScript dependency, along with a minor update to the browser detection logic.

• Added TypeScript as a dependency in package.json to support generating declaration files.
• Updated BrowserDetection.ts to conditionally map the engine value using a ternary operator.

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

File	Description
package.json	Added TypeScript dependency and adjusted formatting.
browser-detection/BrowserDetection.ts	Changed engine mapping to handle falsy values.

Comments suppressed due to low confidence (1)

browser-detection/BrowserDetection.ts:61

• Ensure that treating falsy engine values as undefined is the intended behavior, especially for cases where engine might be an empty string.

engine: engine ? ENGINES[engine] : undefined,

[saghul]

Generally speaking we shouldn't commit the type declaration files.

Since they are generated by tsc we should try to add a build step that runs tsc and use the result as the entry point, and put a "types" entry in package.json pointing to the generated types inside dist/.

Take a look at how LJM does it (for the TS build, not the UMD one)