Just letting you know, a fresh install of @turf/turf yields:
$ npm install @turf/turf
npm WARN deprecated [email protected]: Turf packages are now namespaced: please use @turf/distance instead
npm WARN deprecated [email protected]: Turf packages are now namespaced: please use @turf/helpers instead
npm WARN deprecated [email protected]: Turf packages are now namespaced: please use @turf/bearing instead
npm WARN deprecated [email protected]: Turf packages are now namespaced: please use @turf/destination instead
npm WARN deprecated [email protected]: Turf packages are now namespaced: please use @turf/invariant instead
They all seem to be coming from one dep, turf-line-slice-along.
$ npm ls turf-helpers turf-distance turf-bearing turf-destination turf-invariant
[email protected] /Users/contra/Projects/staeco
โโโฌ @turf/[email protected]
โโโฌ @turf/[email protected]
โโโฌ [email protected]
โ โโโ [email protected]
โโโ [email protected]
โโโ [email protected]
โโโ [email protected]
Updating the package.json of that module should fix all of these errors and make installs clean.
I have a PR to come that deal with those deps to 3.0.x (except maybe turf-isolines dependency to turf-grid 1.0.1)
@ath0mas Thanks!
Re-opening Issue: Still might have a few more warnings from @ath0mas comment.
Fix #501 removing deps to v3.0.x modules
Still have a dep to "turf-grid" in turf-isolines though (vs turf-point-grid 3.0.x / @turf/point-grid 3.5.x ?)
These warning are still present:
npm WARN deprecated [email protected]: Turf packages are now namespaced: please use @turf/bearing instead
npm WARN deprecated [email protected]: Turf packages are now namespaced: please use @turf/destination instead
npm WARN deprecated [email protected]: Turf packages are now namespaced: please use @turf/distance instead
npm WARN deprecated [email protected]: Turf packages are now namespaced: please use @turf/helpers instead
npm WARN deprecated [email protected]: Turf packages are now namespaced: please use @turf/invariant instead
This is fixed on the master branch, just need to release a patch 3.5.3 or minor 3.6.0 release and these will go away.
Close for now since this is fixed.
I'll roll a release and add you to the npm owners group!
3.5.3 published.
I'll roll a release and add you to the npm owners group!
Instead of handling release manually, I highly recommend looking into https://github.com/semantic-release/semantic-release. It just saves so much time. As an example, I am using it here https://github.com/gajus/swing
I'm afraid that'd be an abstraction on an abstraction: turf.js already uses lerna to organize its versions and sub-versions dependently. semantic-release looks quite nice, but doesn't look like it's geared for or tolerant of monorepos.
If you are feeling adventures, it is quite straightforward to implement a version of semantic-release using shell scripts, e.g. https://github.com/gajus/gitinfo/blob/master/.scripts/release.sh
Hi,
Apparently there are again deprecated "issues" with turf
npm WARN deprecated [email protected]: This module is now under the @mapbox namespace: install @mapbox/geojson-area instead
npm WARN deprecated [email protected]: This module is now under the @mapbox namespace: install @mapbox/geojson-normalize instead
$ npm ls geojson-area geojson-normalize
`-- @turf/[email protected]
+-- @turf/[email protected]
| `-- [email protected]
`-- @turf/[email protected]
`-- [email protected]
mapbox changed it some week ago. Those are the only warning from a clean install. Latest 3.7.0 turf version
npm install --save @turf/turf
npm WARN deprecated [email protected]: Turf packages are now namespaced: please use @turf/area instead
npm WARN deprecated [email protected]: Turf packages are now namespaced: please use @turf/helpers instead
npm WARN deprecated [email protected]: Turf packages are now namespaced: please use @turf/within instead
npm WARN deprecated [email protected]: This module is now under the @mapbox namespace: install @mapbox/geojson-area instead
npm WARN deprecated [email protected]: Turf packages are now namespaced: please use @turf/inside instead
npm WARN deprecated [email protected]: Turf packages are now namespaced: please use @turf/invariant instead
issue still persist on a fresh install of turf 3.14.1
@privateOmega I don't seem to get any deprecated warning messages using npm or yarn.
Also no messages are showing up in the travis build.
Is anyone else getting warning messages?
@DenisCarriere I was hoping someone could help me with this.
Most helpful comment
I'm afraid that'd be an abstraction on an abstraction: turf.js already uses lerna to organize its versions and sub-versions dependently. semantic-release looks quite nice, but doesn't look like it's geared for or tolerant of monorepos.