Reconsider package breakdown

[sarahdayan]

The current v2 alpha is broken down between multiple packages:

• @dinero.js/calculator-bigint
• @dinero.js/calculator-number
• @dinero.js/core
• @dinero.js/currencies
• dinero.js

Not all packages may be relevant:

• Most users only need dinero.js and @dinero.js/currencies
• @dinero.js/core isn't tested to avoid duplicates with dinero.js
• @dinero.js/calculator-number is used by default in dinero.js and hasn't much use elsewhere

Multi-packages make sense when there are strong reasons why you might not need them all (e.g., when implementing a library in multiple JavaScript flavors, when providing fully optional plugins, etc.) and in case of large bundle size impact.

Right now, there might be more packages than necessary, which hurts developer experience (e.g., it's easy to have mismatched versions) for no gain.

Let's reconsider how the packages are broken down before going beta.

[johnhooks]

I support combining the calculators and core into dinero.js.

[johnhooks]

I would recommend using tsconfig paths to reduce the need for relative paths.

[sarahdayan]

I'm going to write a proper RFC for this issue. This goes beyond just splitting the codebase into packages, we can go as far as detailing UMD endpoints.

I'll post a link here once it's up.

[sarahdayan]

It took me a while, but the RFC is up!

Please read and comment so we can iron out the kinks and move forward.