@alpinejs/docs 3.9.1-revision.1 → 3.9.2-revision.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/package.json +1 -1
  2. package/src/en/directives/modelable.md +3 -4
  3. package/src/en/essentials/installation.md +1 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@alpinejs/docs",
3
- "version": "3.9.1-revision.1",
3
+ "version": "3.9.2-revision.1",
4
4
  "description": "The documentation for Alpine",
5
5
  "author": "Caleb Porzio",
6
6
  "license": "MIT"
package/src/en/directives/modelable.md CHANGED
@@ -5,9 +5,7 @@ title: modelable
5
5
 
6
6
  # x-modelable
7
7
 
8
- `x-modelable` allows you to expose any value by name as the target of the `x-model` directive.
9
-
10
- Typically this feature would be used in conjunction with a backend templating framework like Laravel Blade. It's useful for abstracting away Alpine components into backend templates and exposing state to the outside through `x-model` as if it were a native input.
8
+ `x-modelable` allows you to expose any Alpine property as the target of the `x-model` directive.
11
9
 
12
10
  Here's a simple example of using `x-modelable` to expose a variable for binding with `x-model`.
13
11
 
@@ -17,7 +15,7 @@ Here's a simple example of using `x-modelable` to expose a variable for binding
17
15
  <button @click="count++">Increment</button>
18
16
  </div>
19
17
 
20
- Some Number: <span x-text="number"></span>
18
+ Number: <span x-text="number"></span>
21
19
  </div>
22
20
  ```
23
21
 
@@ -35,3 +33,4 @@ Here's a simple example of using `x-modelable` to expose a variable for binding
35
33
 
36
34
  As you can see the outer scope property "number" is now bound to the inner scope property "count".
37
35
 
36
+ Typically this feature would be used in conjunction with a backend templating framework like Laravel Blade. It's useful for abstracting away Alpine components into backend templates and exposing state to the outside through `x-model` as if it were a native input.
package/src/en/essentials/installation.md CHANGED
@@ -33,7 +33,7 @@ This is by far the simplest way to get started with Alpine. Include the followin
33
33
  Notice the `@3.x.x` in the provided CDN link. This will pull the latest version of Alpine version 3. For stability in production, it's recommended that you hardcode the latest version in the CDN link.
34
34
 
35
35
  ```alpine
36
- <script defer src="https://unpkg.com/alpinejs@3.9.1/dist/cdn.min.js"></script>
36
+ <script defer src="https://unpkg.com/alpinejs@3.9.2/dist/cdn.min.js"></script>
37
37
  ```
38
38
 
39
39
  That's it! Alpine is now available for use inside your page.