search

windicss / windicss

Next generation utility-first CSS framework.
https://windicss.org
MIT License
6.51k stars 180 forks source link

extract.include symlink problem #515

Open mrwokkel opened 2 years ago

mrwokkel commented 2 years ago

When working from a monorepo with pnpm (which uses symlinks for package management) and requiring package A from package B, and pointing extract.include to include node_module package A, the following occurs.

Initial load works. But when using HMR, WindiCSS works for changes in package B, but not for changes in package A.

When pointing pointing extract.include to package A directly (not using the symlink, so like ../packageA/*/.{html,js}) and using HMR, WindiCSS also updates changes in package A.

Maybe the included path/globs kan be turned to realpaths before using passing it on for scanning? But then, I don't have sufficient knowledge of this code base and have not considered possible consequences.

outerlook commented 2 years ago

Originally:

I am having symlink problems too using vite-plugin-windicss. Everything works on dev, but building makes things on the package inside node_modules not being extracted

Edit: figured the problem is other. Components loaded with client:* doesn't work... nothing with this issue.