Svelte

Describe the bug
The validateArgs method in lib/router/src/utils.ts is using VALIDATION_REGEXP, NUMBER_REGEXP, HEX_REGEXP or COLOR_REGEXP pattern to determine whether the string value is validated or not, but any string which not match those pattern (like something with + prefix or some character that is not in Alphabet) will not be validated and be dropped in future actions.

Repo: https://github.com/codercatdev/mitosis-example

Video Exmaple: https://youtu.be/fFjzpB3JkwU

I would expect this to default to reacts own state useState

 mitosis compile --to=react component.lite.jsx > output/component.jsx

for tailwindcss:

<div className="relative w-4 h-4 bg-red-400 after:absolute after:top-4 after:w-full after:h-full after:bg-blue-400" />

for windicss:

<div className="relative w-4 h-4 bg-red-400 after:(absolute top-4 w-full h-full bg-blue-400)" />
`

All preset readme files needs updates for v2

I have an podcast with episode uploaded to Mixcloud. I also have my music uploaded to Soundcloud. I'd like to see Mixcloud and Soundcloud added as providers with Vime.js

Also I endorse the feature request for playlist.

I plan to use this with an Svelte app.

The various popup shown can be placed outside the viewport, making them hard to view/use.

For example, a tooltip can be partially hidden if the activator is in the right of the screen, or a menu can be longer than the viewport height.

Smelte should probably provides utils to position popup on the viewport.

(by the way, thanks for your work, smelte is great :)

We enabled pylint in the project, however several code style violations already exist. There's no point in enabling rules and then not enforcing them, therefore any rule that is not already enforced is currently disabled.

One of these rules if the one you can see in the title is this issue.

How to solve
Create a pull request with 2 commits. The commits should:

1. Enable the rule in

Is your feature request related to a problem? Please describe.
Hello team.
I have a task to deploy a tiny and cute frontend, which will distribute wg configs for users of our organization. I decided to use your package, because it is 100% suitable.
We use dedicated server as a wg endpoint (VyOS cluster on vrrp), so I don't need to create peers from UI. I am populating config.json by ansible