As of today, PureScript has started publishing prereleases of every post-merge build we run to npm, under the
These prerelease builds are like the ‘nightly’ builds of larger projects—they are automated and not subject to the level of human scrutiny and manual testing that we give to our full releases. We can and will change and revert features made available in these builds with no notice. Furthermore, we don’t yet know how long each individual build may remain available—at some point, GitHub (which hosts the actual binaries, not npm) may ask us to start deleting older prereleases. For all of these reasons, we don’t recommend having production projects depend on
purescript@next or on specific prerelease versions for more than just testing or release prep purposes.
However, if you’d like to test whether a recently-merged PR resolves an issue for you, get a preview of a new feature, or get a head start on the next big migration, all without building PureScript from source yourself, you can now do this with
npm install purescript@next [--no-save|--save-dev|--global]! We are still interested in bug reports from any recent version of PureScript, prerelease or not, so please let us know if you encounter anything unexpected.
If you aren’t interested in being a guinea pig, know that these prerelease builds are versioned with numbers like 0.15.1-2, and npm recognizes that the hyphen means the package is a prerelease and not to be included in ranges like
"^0.15.0". And the
@latest tag will continue to refer to the latest full release. So these builds shouldn’t accidentally work their way into anyone’s dependencies, even if you haven’t pinned to a single release version.