Closed Bomper closed 2 hours ago
The Big part just re-exports an older version of Big.js. Big.js recently released a new major version, and this repo is 4 years old.
Big
What's the point of wrapping an old version?
Also the README looks unprofessional.
Wouldn't it be better to remove Big.js and let users use it from NPM?
Please note that this repository is 4 years old, when Deno was not mature.
This is for historical reasons.
And the repository is no longer maintained, it is recommended to import Big.js from npm
The
Big
part just re-exports an older version of Big.js. Big.js recently released a new major version, and this repo is 4 years old.What's the point of wrapping an old version?
Also the README looks unprofessional.
Wouldn't it be better to remove Big.js and let users use it from NPM?