Use stricter dependency version requirements for 0.x.y releases

[rsek]

Datasworn may receive breaking changes on any version change (consistent with its 0.x.y semver). However, the semver notation in package.json indicates compatibility with anything of the same major (0), so NodeJS dependency resolution behaves in unintended ways.

It'd be better to require an exact version match, which would at least provide a useful error message rather than silently resolving to functionally incompatible versions of various datasworn packages.

[edbrannin]

Counterpoint:

Doesn’t this discourage rapid development and fast iteration?

Major version zero is all about rapid development. If you’re changing the API every day you should either still be in version 0.y.z or on a separate development branch working on the next major version.