@curly-message/parser 1.0.0-next.0 → 1.0.0-next.1

package/README.md

@@ -72,6 +72,15 @@ host's own numeric conversion makes of them: `{{v:number}}` over `{ v: '' }`
 takes the fallback chain rather than formatting a zero, and `{{v:date}}` over
 the same value takes it rather than formatting the epoch.
 
+## Installation
+
+```bash
+npm install @curly-message/parser@next
+```
+
+The package is a prerelease, published under the `next` dist-tag until a
+stable version reaches `latest`.
+
 ## Usage
 
 ```js
@@ -387,7 +396,7 @@ wants as an ordinary string value, with every backslash doubled.
 
 ## Status
 
-**Unreleased, and the public surface is unstable.**
+**Prerelease under the `next` dist-tag, and the public surface is unstable.**
 
 Nothing here references a host framework: `resolve` takes the format's own
 inputs, and an adapter that presents this parser to a host library belongs in
@@ -400,7 +409,10 @@ message resolves to rather than merely what it can do — without Intl, `number`
 `date`, `ago` and `currency` are modifier names nobody registered.
 
 The specification is normative — where this implementation and the
-specification disagree, this implementation is wrong.
+specification disagree, this implementation is wrong. The specification's
+conformance set (`@curly-message/conformance`) holds it to that: the adapter of
+section 14.3 lives in `tests/conformance/adapter.ts`, and `npm test` runs
+every case the set ships against it, at every level.
 
 ## Development
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@curly-message/parser",
-  "version": "1.0.0-next.0",
+  "version": "1.0.0-next.1",
   "description": "JavaScript implementation of the Curly Message Format.",
   "type": "module",
   "types": "./dist/index.d.ts",
@@ -48,6 +48,7 @@
   },
   "homepage": "https://github.com/curly-message/parsers/tree/main/js#readme",
   "devDependencies": {
+    "@curly-message/conformance": "^1.0.0-next.1",
     "@eslint/js": "^10.0.1",
     "@stylistic/eslint-plugin": "^5.10.0",
     "eslint": "^10.8.1",