Description
This repository contains two things:
- The Fantasy Land specification
- The source for the
fantasy-landpackage on npm
Currently, both are subjected to the same version number: the one specified in package.json. Over the lifetime of Fantasy Land, the "major" part of this version number has been bumped whenever a breaking change in the specification occurred (the prefixing of method names, the flipping ap, etc). The major version of "Fantasy Land" has therefore always been a decent indication of what libraries are compatible with one another, and so a good means of communication and disambiguation.
With the latest major version bump, the breaking changes did not apply to the specification itself, but to the npm package. This means that all libraries conforming to Fantasy Land 3, also conform to "Fantasy Land 4". I think this might become a source of confusion.
Perhaps - if others agree that this issue needs solving, - instead of relying on the package version number for communicating the version of the specification, we could embed a formal version number in the specification document. Or alternatively, perhaps the npm package source code could be moved into its own, separately versioned, repository.