Clientlibs not being built properly

[l3szek]

Hi,
First of all, I would like to thank you for this plugin. It is very promising.

After following the AEM Vite official documentation, I am able to see the local AEM instance being proxied on localhost:3000, but
I've run into few issues with it, as described below. Please see my repo for reference.

The problem is that my JS/CSS changes doesn't seem to be available there. I've added a console.log in the main script, but it's not being shown anywhere under localhost content pages (e.g. http://127.0.0.1:5173/content/wknd/us/en.html).
These are my settings under viteForAem:
viteForAem({ contentPaths: [ '/content/wknd/us/en', '/', './', '/content/wknd/us/en.html', ], publicPath: '/etc.clientlibs/wknd/clientlibs/clientlib-site', })

The clientlibs folder doesn't seem to be updated after vite build --mode development or vite build --mode production, also it's not automatically updated (synced) once I change something in the code while running vite serve.
After vite build, only the 'dist' folder under ui.frontend is being populated, due to outDir set to 'dist' and I am wondering if that causes the issue? That causes the clientlibs folder to be untouched and not updated.

I was wondering if there is a working AEM Vite demo repo, with everything properly configured (maybe based on the AEM Project Archetype) that could be used as a boilerplate?

Any help on what I might be doing wrong in my repo is highly appreciated.

[l3szek]

To anyone stumbling across similar issue, I've resolved it by adding a category to the settings of the clientlib-site folder: categories="[aem-vite]" (in the .content.xml file under <project>/clientlibs/clientlib-site), and then setting that category in the template's policy, like so:
`<policy
jcr:primaryType="nt:unstructured"
sling:resourceType="wcm/core/components/policy/policy"
clientlibs="[aem-vite]"
clientlibsJsHead="[clientlib-site]"

`