htmx

this is what people must feel like looking at hyperscript for the first time

```js
class {
  name = 'Wilbur';

  bind() {
    const { name } = this;
    return sheet`
      .name {
        --name: ${name};
        text: var(--name);
      }
    `;
  }
}
```

```applescript
set :name to "Wilbur"
put :name into me
```

```applescript
init make an EventTarget called :name then send change(value: "Wilbur") to it
on change(value) from :name put value into me
```

Hi! I'm having trouble with the `json-enc` extension on my form. I have added it but the request isn't sending the parameters as JSON. Any ideas what I'm doing wrong?

```html
<form hx-post="http://localhost:9000/customers" hx-ext="json-enc">
```

The request validation is failing because it's saying the request isn't a dict (JSON). I'm using Python's FastAPI

I could always change my fast api route to accept form params, I just wanted to know if it were possible to send form values as json with htmx

just to cover our bases, do you have the json-enc extension loaded

Do I have to add an additional script import? I'm using HTMX via unpkg. I thought I saw that json-enc was included

Ok, I'm just importing htmx with this
```html
        <script src="https://unpkg.com/htmx.org@1.7.0" integrity="sha384-EzBXYPt0/T6gxNp0nuPtLkmRpmDBbjg6WmCUZRLXBBwYYmwAUxzlSGej0ARHX0Bo" crossorigin="anonymous"></script>
```

`https://unpkg.com/htmx.org@1.7.0/dist/ext/json-enc.js`

Thanks man! Maybe we can add a small blurb to the documentation that in order to use the extensions they must be included via script tags? I was confused by this part.

actually what is the right way to include extensions when using a build process? I haven't had to do that yet

eventually we are going to have https://extensions.htmx.org  which will be managed entirely by <@!732737380167188501>

I'm loading dialogs "on demand" by having a `<div id="modals"></div>` at the bottom of the body, and then simply doing requests like `<img hx-get="/foo" hx-target="#modals" src="myicon.svg">`. I was wondering if there is a more elegant way to do it.

I'm not just putting the dialog directly on the original body because depending on where the user clicks, it gets populates with slightly different data (so the urls are actually more like /foo/1, /foo/2, etc)

so I don't want to include all the N potential dialogs the user might trigger