Bundle all entry points with rollup

[TrySound]

Here's a set of result files

• ./dist/cjs/i18nextChainedBackend.js
• ./dist/esm/i18nextChainedBackend.js
• ./dist/umd/i18nextChainedBackend.js
• ./dist/umd/i18nextChainedBackend.min.js

Amd and iife are part of umd format.

Babel helpers are reused across packages.

Windows specific scripts are simplified.

If you agree I can make PRs in another packages.

Also jsnext:main was deprecated a few years ago. It's better to remove in in the next major release.

[jamuhl]

@TrySound looks great for me...to make sure I get no "complains" I will make a major version with those changes - as whoever imported something like import * as utils from './dist/commonjs/utils'; would be not amused (won't be a lot...but better be save). -> so jsnext:main could be removed on the same run...

[TrySound]

Why don't you use lock files? They speed up installing a lot and improve safety (at least yarn does).

[jamuhl]

not sure how they are nowadays...but in the past they were just a pain in the ass when updating dependencies.

my personal solution, which was safe in the last years of doing production stuff...fix versions - never ever use "@babel/runtime": "^7.4.5" -> dependency of dependency of dependency does no proper semver -> ends in being doomed...

this all might be better - never tested - but my experience is using "@babel/runtime": "7.4.5" is save

[TrySound]

Well, there were problems with babel runtime when it was in beta. Now it's quite stable. I didn't see any problems since babel 7 release.

[jamuhl]

will check it in for now...will see...nothing to loose

[jamuhl]

published in i18next-chained-backend@2.0.0