@jsenv/navi 0.29.189 → 0.29.190

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.
package/docs/i18n.md CHANGED
@@ -163,7 +163,10 @@ naviI18n.addLangKeys("ja", { "button.close": "閉じる" });
163
163
  ```
164
164
 
165
165
  Its JSDoc lists the key namespaces; the exhaustive list of keys and defaults is
166
- the registration block in `src/text/navi_i18n.js`, which is meant to be read.
166
+ the registration block in `src/text/navi_i18n.js`, which is meant to be read —
167
+ plus `src/i18n/humanize_i18n.js` in `@jsenv/humanize` for the `time.*` wording
168
+ the formatters use. Both register into the one registry `naviI18n` is, so
169
+ overriding either goes through the same call.
167
170
 
168
171
  Do not put application texts in `naviI18n`. Key collisions aside, the two have
169
172
  different lifecycles: navi's keys come with the package version, the app's come
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jsenv/navi",
3
- "version": "0.29.189",
3
+ "version": "0.29.190",
4
4
  "type": "module",
5
5
  "description": "Library of components including navigation to create frontend applications",
6
6
  "repository": {
@@ -19,10 +19,6 @@
19
19
  "development": "./dist/dev/jsenv_navi.js",
20
20
  "default": "./dist/jsenv_navi.js"
21
21
  },
22
- "./format_time": {
23
- "dev:jsenv": "./src/text/format_time.js",
24
- "default": "./dist/jsenv_navi_format_time.js"
25
- },
26
22
  "./*": "./*"
27
23
  },
28
24
  "files": [
@@ -35,7 +31,7 @@
35
31
  },
36
32
  "dependencies": {
37
33
  "@jsenv/dom": "0.17.45",
38
- "@jsenv/humanize": "1.7.8",
34
+ "@jsenv/humanize": "1.8.0",
39
35
  "@jsenv/validity": "0.4.3"
40
36
  },
41
37
  "devDependencies": {