Consider to migrate to "postcss-modules" dependency from "@dr.pogodin/postcss-modules-parser"

[birdofpreyru]

• Right now this plugin depends on https://www.npmjs.com/package/@dr.pogodin/postcss-modules-parser, which is my upgraded fork of seeminly long-abandoned https://github.com/css-modules/postcss-icss project (it looks nobody uses it anymore).
• Looking in PostCSS plugins catalog, I found https://www.npmjs.com/package/postcss-modules, which at the first glance does the similar job, but has ~1M weekly downloads, and is actively maintained.

Thus, it will be great to migrate postcss-modules.

[birdofpreyru]

For a record, it turns out to be impossible at the moment:

• postcss-modules provides asynchronous interface only, and thus cannot be used within Babel plugins (which must be synchronous, as of current Babel versions).
• Support of synchronous interface in postcss-modules was requested in past to no avail, and the alternative library mentioned in that ticket (https://www.npmjs.com/package/postcss-modules-sync) is not actively used / maintained, thus makes no sense to migrate to.
• A possible workaround would be to use deasync to incorporate async running of PostCSS into synchronous flow of Babel plugin, but it turns out that deasync does not work correctly in Jest tests, which seems a dealbreaker to me. That is beside other problems deasync may create.