Fails to extract on Windows due to wrong path.sep used (2.4)

[MartijnHols]

Describe the bug
lingui extract returns No locales defined! when extracting messages on Windows.

To Reproduce
Run lingui extract on a Windows machine in cmd.

Additional context
The issue is that locale returned by

js-lingui/packages/cli/src/api/catalog.js

Line 150 in 0bb80a4

const [locale] = filename.split(path.sep).reverse()

contains the entire path, not just the locale name. This is because path.sep is \ while the result from glob.sync contains paths with forward slashes /. Replacing path.sep with / fixes this specific issue (but my extraction still fails because of a different error).

I would have made a PR if I didn't fear side-effects.

[tricoder42]

Hey @MartijnHols,
thank you for bug report! Don't fear side-effects at all :) Feel free to follow contributors guide, the tests should back you up.

I tried to make this method platform compatible, but didn't realize glob.sync normalize slashes...

[tricoder42]

No worries, I'm going to release it with upcoming patch

[tricoder42]

Released in v2.4.1, thanks for reporting the issue!