docs: mention plugins in editor support (#675)

* fix: typeof import default in dts

* chore: using nuxt convention for indexing type

* docs: mention plugins in editor support

* Update docs/content/2.tailwind/3.editor-support.md

Author: ineshbose

docs/content/2.tailwind/3.editor-support.md

@@ -21,7 +21,7 @@ Add the following configuration to your `.vscode/settings.json` file, so that Ta
 
 If you use pnpm, make sure that tailwindcss is installed in your top level node_modules folder.
 
-Since Tailwind CSS v3.3, [ESM/TS configuration has been supported](https://tailwindcss.com/blog/tailwindcss-v3-3#esm-and-type-script-support) so your editor should automatically configure autocomplete based on your config. If you happen to use a lower version and/or require the configuration in CommonJS, you can use the `tailwindcss:resolvedConfig` hook and a custom Nuxt module:
+Since Tailwind CSS v3.3, [ESM/TS configuration has been supported](https://tailwindcss.com/blog/tailwindcss-v3-3#esm-and-type-script-support) so your editor should automatically configure autocomplete based on your `tailwind.config`. If you happen to use a lower version and/or require the configuration in CommonJS, you can use the `tailwindcss:resolvedConfig` hook and a custom Nuxt module:
 
 ```ts [modules/tw-cjs-config.ts]
 import { defineNuxtModule, addTemplate } from '@nuxt/kit'
@@ -47,3 +47,5 @@ export default defineNuxtModule({
 },
 // ...
 ```
+
+This hook will allow you to customise your generated template through a module in different ways (e.g., different filename, contents, etc.). Please note that `JSON.stringify` will remove plugins from your configuration.