Not sure whether to make the schema version the same as the module version number in package.json.
If the schema version is the same as the package.json version then:
If the module version major bumps and the schema hasn't changed then older module versions won't parse a message even though they theoretically could. But that could be handled in the schema using oneOf the two valid version number patterns.
If the schema changes in such a way as to force a major version bump then it forces a bump of the module version. Which I think makes sense.
It makes it easier to find a parser for a given version of a message. If we know the schema version number, we know what module version should work.
If the schema version is not the same as the package.json version then:
maintainers must think carefully about how module version changes and schema version changes relate to each other.
Not sure whether to make the schema version the same as the module version number in package.json.
If the schema version is the same as the package.json version then:
oneOfthe two valid version number patterns.If the schema version is not the same as the package.json version then: