josdejong/mathjs

AI Summary: The minified browser build of the `mathjs` NPM package (`lib/browser/math.js`) incorrectly bundles code from `core-js`, despite `core-js` being listed only as a dev-dependency. This leads to an unnecessarily large production file containing dead code, including potentially sensitive functions like ActiveXObject and iframe manipulation, which was even flagged as a Trojan. The problem indicates a misconfiguration in the build process that includes development-only dependencies in the final published output.

AI Summary: The task is to debug and fix a bug in the math.js library where the `sign` function applied to a fraction with a numerator of 0 returns 1/1 instead of the expected 0/1. This involves understanding the library's internal representation of fractions and modifying the `sign` function to handle this edge case correctly.

AI Summary: The task is to investigate why the dependencies `evalDependencies`, `eyeDependencies`, `typeofDependencies`, and `varDependencies` listed in `index.d.ts` of the math.js project are causing import errors, and then either remove them from `index.d.ts` if they are indeed nonexistent or correct the issue if they are present but not properly exported.

AI Summary: Debug and fix a parsing ambiguity in the math.js library where the parser misinterprets the unary and binary uses of the modulo (%) and negation (-) operators, leading to incorrect results when they appear together in expressions. The solution should ensure correct operator precedence and handle whitespace inconsistencies.

AI Summary: The task is to fix a TypeScript type error in the math.js library's unit conversion function. The `to()` method of the `Unit` object is incorrectly typed, causing a compilation error when passing another `Unit` object as an argument. The solution involves correcting the TypeScript type definition for the `to()` method to accept a `Unit` object as a valid argument.

AI Summary: The task is to debug a TypeScript type error occurring when using the `math.unit()` function from the math.js library with a BigNumber object. The error arises because TypeScript's type inference doesn't correctly handle the implicit conversion from BigNumber to string or Unit, requiring a type assertion workaround. The solution involves investigating the math.js library's type definitions and potentially improving them to correctly handle BigNumber inputs to `math.unit()`, ensuring proper type inference without the need for type assertions.