@verbaly/vue 0.69.0 → 0.69.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 (2) hide show
  1. package/README.md +1 -1
  2. package/package.json +3 -3
package/README.md CHANGED
@@ -39,7 +39,7 @@ app.use(verbalyPlugin(verbaly));
39
39
  </template>
40
40
  ```
41
41
 
42
- **Keys are typed.** `useT()` checks every key and its params against your source catalog, through the types Verbaly generates (`src/verbaly.d.ts` in a Vite app, `.nuxt/verbaly.d.ts` in Nuxt): a key no catalog has does not compile. A key that comes from data is declared with `defineKeys` from `virtual:verbaly`.
42
+ **Keys are typed.** `useT()` checks every key and its params against your source catalog, through the types Verbaly generates (`src/verbaly.d.ts` in a Vite app, `.nuxt/verbaly.d.ts` in Nuxt): a key no catalog has does not compile. A key that comes from data, like `t(item.key)`, passes as it is; declare it with `defineKeys` from `virtual:verbaly` when you want `check` to verify it exists.
43
43
 
44
44
  Or skip the keys entirely: write the source text in place and the compiler extracts it, right in your `.vue` files (script and template):
45
45
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@verbaly/vue",
3
- "version": "0.69.0",
3
+ "version": "0.69.1",
4
4
  "description": "Vue 3 bindings for Verbaly: composables over the reactive core.",
5
5
  "keywords": [
6
6
  "i18n",
@@ -47,12 +47,12 @@
47
47
  "access": "public"
48
48
  },
49
49
  "peerDependencies": {
50
- "verbaly": "^0.69.0",
50
+ "verbaly": "^0.69.1",
51
51
  "vue": "^3.4.0"
52
52
  },
53
53
  "devDependencies": {
54
54
  "happy-dom": "^20.14.5",
55
- "verbaly": "^0.69.0",
55
+ "verbaly": "^0.69.1",
56
56
  "vue": "^3.5.43"
57
57
  },
58
58
  "scripts": {