You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Make periodic pre-release builds available on npm #1882
I believe the only outstanding question we had here was how to do this in a way that people who didn't specify a version number in their package.json didn't automatically upgrade to some possibly-unstable TypeScript build.
Assuming you'll use prerelease tags (eg 1.5.0-prerelease.2015.02.02.abcd) npm will never choose this to install unless the requested version also contains a prerelease tag. See https://github.com/npm/node-semver#prerelease-tags for details.
Prerelease tags are also considered less than their corresponding release, so the above would be less than 1.5.0 when it's actually released. From the semver spec:
Activity
RyanCavanaugh commentedon Feb 2, 2015
I believe the only outstanding question we had here was how to do this in a way that people who didn't specify a version number in their package.json didn't automatically upgrade to some possibly-unstable TypeScript build.
Arnavion commentedon Feb 2, 2015
Assuming you'll use prerelease tags (eg
1.5.0-prerelease.2015.02.02.abcd) npm will never choose this to install unless the requested version also contains a prerelease tag. See https://github.com/npm/node-semver#prerelease-tags for details.Prerelease tags are also considered less than their corresponding release, so the above would be less than 1.5.0 when it's actually released. From the semver spec:
Can you detail what version format you're going to use for the prereleases?
danielearwicker commentedon Mar 13, 2015
👍 very keen to have this!
RyanCavanaugh commentedon May 19, 2015
Let's figure out what the right way to do this is.
DanielRosenwasser commentedon Jun 18, 2015
This appears to be a duplicate of #964.