fix: nested props resolution

[ineshbose]

#603

[atinux]

Is it good for you @ineshbose ?

[ineshbose]

It works, but I hit the dynamic import occasionally (1 out of 10 times maybe) but write: true for base config gives no error - any suggestion on that? If you don't encounter it, perhaps I may be testing it wrong. @atinux

[atinux]

What is the example where you get the error? if write: true works for you with no errors we can add it.

[ineshbose]

If you copy the linked issue's reproduction's app.vue into say, playground/pages/nested.vue:

<script setup>
import colors from '#tailwind-config/theme/colors';
</script>

<template>
  <div>
    {{ JSON.stringify(colors, null, 2) }}
  </div>
</template>

On starting the playground, either index.vue gives dynamic import error, or nested.vue would not be resolved without this. Sorry but I'm thinking I can brainstorm a bit more into having the base .mjs with write: true but have imports to be from #build/tailwind.config rather than relative ./tailwind.config/...

I'll share a screen recording

[ineshbose]

module.ts.-.nuxt-tailwindcss-module.Codespaces.-.Visual.Studio.Code.-.Google.Chrome.2023-02-17.11-20-05.mp4

@atinux

Happens once after boot I think and a refresh fixes it, but sharing with you (the nginx error was codespaces)

[atinux]

Do you have the error locally and not on github.dev?

[ineshbose]

Yes the error happens locally too, but I've added the suggestion #616 (comment) that should fix it

[atinux]

Released in v6.4.1