v6.13.3

• Update of dependencies.

v6.13.2

• Adds explicit .js extension to imports of the runtime style name resolution helper injected into compiled code by this plugin, to avoid problems with ESM modules in Node environment (with type: module). — Thanks to @d-oliveros for PR #45
• Update of dependencies.

v6.13.1

• [#44] Support of named CSS imports, in particular by the replaceImport feature.

v6.13.0

• Compatibility to the latest css-loader v7.0.0.
• Updates dependencies.

v6.12.0

• Updates dependencies.
• Adds some TypeScript type declarations (non-exhaustive, just those options & exports I currently need in a TS project of mine relying on this plugin).
• Officially supported Node versions now are: 18.18+ (maintenance); 20.8+ (LTS); 21.0+ (current).

v6.11.0

• [#43] Reverts changes related to PR #42, introduced in the previous release (v6.10.0).

  When accepting the PR, it did not cross my mind that injecting an absolute path to a module into a compiled code (also suggested in #41, if I am not mistaken) is a terrible idea, as it implies that the compiled code will not work if its runtime environment is different from the build environment (e.g. modules have been moved around after the build, or the code is build on one system and used on another, etc.). I had a glance at pnpm documentation, and it seems to me that to avoid the problem PR #42 intended to solve, one just have to correctly configure his pnpm project, maybe to add some pnpm-specific configuration to this plugin as well. Not something I personally will spend my time on investigating further, unless somebody brings in funds to cover it. If you can't figure it out, neither able to bring in the funding for me to figure it out, I just suggest using the normal npm — it might be slower and less disk-space efficient, but it turns out it comes out with an easier developer experience :)

• Updates dependencies.

v6.10.0

• Fixes runtime class resolution for scenarios where this plugin is an indirect dependency of the host project. — Thanks to PR #42 by @moonlitusun
• Updates dependencies.
• Drops support for Node v14 and v19 (both reached their end-of-life); adds to CI/CD setup the testing with Node v20 (current).

v6.9.4

• Updates dependencies.

v6.9.3

• Updates dependencies.

v6.9.2

• Updates dependencies.