turf-destination versions and release history

Inspect a published release before upgrading or adding a dependency. Each version reference keeps its metadata and provider measurements pinned to that exact npm version.

Published versions15
Stable versions12
Prereleases3
Releases published in the last 90 days0
Deprecated releases12
Latest npm dist-tag3.0.12

All available releases

VersionPublishedRuntime dependenciesTypesStatus
3.0.122016-07-05T18:28:22.931Z2Not declaredTurf packages are now namespaced: please use @turf/destination instead
3.0.102016-06-15T13:11:24.054Z2Not declaredTurf packages are now namespaced: please use @turf/destination instead
3.0.7-canary.ae89c8b32016-06-14T21:47:30.840Z2Not declaredcanary
3.0.52016-05-17T19:35:45.130Z2Not declaredTurf packages are now namespaced: please use @turf/destination instead
3.0.12016-05-16T20:44:55.983Z2Not declaredTurf packages are now namespaced: please use @turf/destination instead
3.0.0-canary.7879bf6c2016-05-16T20:35:20.751Z2Not declared
3.0.0-canary.2f5f71672016-05-16T20:04:34.798Z2Not declared
1.2.12015-02-06T21:42:20.093Z1Not declaredTurf packages are now namespaced: please use @turf/destination instead
1.2.02015-01-21T21:23:29.795Z1Not declaredTurf packages are now namespaced: please use @turf/destination instead
1.1.02015-01-21T21:20:56.514Z1Not declaredTurf packages are now namespaced: please use @turf/destination instead
1.0.02014-12-11T20:30:23.503Z1Not declaredTurf packages are now namespaced: please use @turf/destination instead
0.0.52014-08-06T14:00:51.183Z1Not declaredTurf packages are now namespaced: please use @turf/destination instead
0.0.42014-08-05T21:36:46.062Z1Not declaredTurf packages are now namespaced: please use @turf/destination instead
0.0.32014-08-01T21:59:34.924Z1Not declaredTurf packages are now namespaced: please use @turf/destination instead
0.0.22014-08-01T21:46:46.077Z1Not declaredTurf packages are now namespaced: please use @turf/destination instead

Choosing a version

The latest tag is selected by the publisher and is not a guarantee of compatibility. Prerelease and deprecated status remain visible. Check your Node.js range and peer requirements on the exact version page, then review the maintainer’s release notes before upgrading.

Removed or unpublished versions may be absent. Historical download charts cover all package versions and do not show adoption of an individual release.

npm release-history source — retrieved 2026-11-07T00:52:16.492Z