Consider merging with i18next-gettext-converter again

[perrin4869]

@adrai I just released [email protected] which upgrades to gettext-parser@6 fresh off the oven.
This new version of gettext-parser upgraded to readable-stream@4 which removes the circular dependency that was causing trouble when packing it for browser consumption. (see: smhg/gettext-parser#63, nodejs/readable-stream#348).
This means that it might be possible to use one of the packages again, instead of having to maintain two separate packages (and maintaining a copy of gettext-parser here).
Maybe you could try replacing this package with [email protected] and see if you encounter any issues sometime?

[adrai]

hmmm... can't just use i18next-gettext-converter, this module is not only offering the i18next conversions, but also non-i18next...
but it might be we can reuse the official gettext-parser again...

[adrai]

made a quick test... and tried to run the existing tests... half of them fail...
will postpone this topic in to the future ;-)

[perrin4869]

Maybe the tests are failing because of this change?
smhg/gettext-parser#72
I had to adjust some tests in i18next-gettext-converter.
Anyways nothing urgent, just think it'll be nice to tidy things up!

[adrai]

no, not just that...