Bundle all entry points with rollup #8
Conversation
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.
|
@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 |
|
Why don't you use lock files? They speed up installing a lot and improve safety (at least yarn does). |
|
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 this all might be better - never tested - but my experience is using |
|
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. |
|
will check it in for now...will see...nothing to loose |
|
published in [email protected] |
Here's a set of result files
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:mainwas deprecated a few years ago. It's better to remove in in the next major release.