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.