This is a draft of refactoring theglobalifySelector to use a CSS parser rather than a regex to hopefully allow major libraries like Tailwind and DaisyUI to work better with Svelte.

I put more details in theglobalfy/README.md however I'll summarize here:

• I looked intoparsel and it doesn't seem to be able to take a modified AST (or even the original) and convert it back into a valid CSS selector.
• css-selector-parser seems to work much better.
• I'm curious why we currently try to nest the:global() operator (e.g., fordiv > p we do:global(div) > :global(p) rather than:global(div > p). The latter is more performant because you can avoid traversing deeper into the AST.
• What do the maintainers of this project think about moving to a CSS parser?
• Do the maintainers have any thoughts about my work here? Do any of you disgaree with usingcss-selector-parser for some reason? Or prefer another CSS parser?

My main goal for opening this PR in draft is to get feedback on if there is any likelihood this could get merged and, since it's a fairly significant change, if the maintainers of this project want to push me in a particular direction or otherwise provide feedback.

Thanks

This is also related to and would probablyfix#501. Though if the maintainers are OK with it I would prefer the quick and dirty#632 get merged to fix that since it's ready to go and simpler. It at least gets Tailwind to work property, however DaisyUI still doesn't work, and that's what this PR is all about.