fix: bundle array deps

[tpoisseau]

bundle is-any-array and ml-array-rescale into ml-matrix

build: build mjs with rollup

Remove build-esm-facade.mjs script

build: add sourcemaps

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 64.83%. Comparing base (b398a84) to head (dcfd6f7).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #204   +/-   ##
=======================================
  Coverage   64.83%   64.83%           
=======================================
  Files          47       47           
  Lines        5625     5625           
  Branches      954      954           
=======================================
  Hits         3647     3647           
  Misses       1967     1967           
  Partials       11       11           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[tpoisseau]

@targos It should be good

[targos]

I will review tomorrow

[targos]

I'm thinking about: "module": "src/index.js", (for bundlers). We should probably keep the deps in prod dependencies for this use case.

[tpoisseau]

I did not pay attention,
Should not we use "module": "matrix.mjs" ?

[targos]

The idea is to point to the source code to make tree shaking potentially more effective, but I have no strong opinion.

[tpoisseau]

Where is the documentation of this module field ?

• https://docs.npmjs.com/cli/v11/configuring-npm/package-json contains nothing about this field
• https://nodejs.org/api/packages.html no documentation about this field

[targos]

It's used by bundlers. e.g. https://rollupjs.org/introduction/#publishing-es-modules

[tpoisseau]

Ok to keep deps instead devDeps so.