feat: inject compilerOptions into customRenderer

[dancon]

I fix the issue#77,

I write a new npm package less-plugin-aliases and inject compilerOptions into the customRenderer that I can resolve the @import ~path manually.

The general use case is as below:

{
  "compilerOptions": {
    "plugins": [
      {
        "name": "typescript-plugin-css-modules",
        "options": {
          "classnameTransform": "camelCase",
          "customMatcher": "\\.less$",
          "customRenderer": "node_modules/less-plugin-aliases/lib/customRender.js"
        }
      }
    ],

    // ...
  }
}

ps: My english is poor, maybe there are some mistakes in README.md, pls fix it if you find ~

[dancon]

@mrmckeb pls take a time to review.

[mrmckeb]

This looks good, thanks @dancon - only one small suggestion, and I'll also add a little more to the docs before release.

I also wonder if you could use the customRenderer like the below? It should work.

        "options": {
          "classnameTransform": "camelCase",
          "customMatcher": "\\.less$",
          "customRenderer": "less-plugin-aliases"
        }

[dancon]

This looks good, thanks @dancon - only one small suggestion, and I'll also add a little more to the docs before release.

I also wonder if you could use the customRenderer like the below? It should work.

        "options": {
          "classnameTransform": "camelCase",
          "customMatcher": "\\.less$",
          "customRenderer": "less-plugin-aliases"
        }

It depends on the way the plugin load customRenderer, and it seems not working for now, becasuse you resolve the options.customRenderer base current directory here

I notice that when I write the less plugin, and decided finally not to touch it , becasuse the usage like node_module/less-plugin-aliases/lib/customRender.js is not a big deal, and if want to load npm package directly need more code for compatibility. I can do that, but maybe next version, is that ok?

I make a commit to support loading npm package as customRenderer.

And less-plugin-aliases default export a plugin for less, not a customRender for this ts plugin, so, after support load package from node_modules, the usage like below is acceptable?

"options": {
         "classnameTransform": "camelCase",
         "customMatcher": "\\.less$",
         "customRenderer": "less-plugin-aliases/lib/customRender.js"
 }

[dancon]

New commits happend after your first review @mrmckeb please check again:

• chore: uniform the variable name, compilerOpts -> compilerOptions
• feat: add support load npm package as customRenderer

[mrmckeb]

Hi @dancon, very sorry about the slow reply.

This looks great. I'll merge today/tomorrow and add some tests for this too. I'll release by the end of the week :)