Looking for "css modules" on Google shows me this repo as the top result, although I was looking for native CSS Modules (EDIT: "CSS Module Scripts" is the official term).

I think it would be sweet if this project could somehow adopt the native CSS Modules format as a compiler option to help people get it working in their projects in all browsers, or if that is not desirable then to potentially rename the project to something like css-scoped-modules or similar to attempt to eliminate the ambiguity on search engines.

Additionally, either way, the README of the project could mention something about native CSS Modules (with links) to help people not get confused and find their way. I could help with this either way.

I think basically three options:

1. officially support the new native CSS Modules format
2. rename the project
3. or at the very least (but also if one of the two previous options are selected) document the differences in the README.

Here is the CSS Modules explainer:

https://github.com/WICG/webcomponents/blob/gh-pages/proposals/css-modules-v1-explainer.md

Here's the article on web.dev by Google, including links to the issue trackers for Firefox and Safari:

https://web.dev/articles/css-module-scripts

It's interesting that there appears to not be a formal spec describing CSS Modules, only the explainer and the article (albeit it is easy to understand the concept without a formal spec), with interest from all parties to implement it. This proves something: it is possible to guide specs based on implementation instead of the other way around (the potentially more arduous route of getting concencus on a spec before browsers implement). So if someone shuts down an idea because "that's what the spec says", we know where we can point them to with hard evidence.