deprecation warnings still exist

Just letting you know, a fresh install of @turf/turf yields:

$ npm install @turf/turf
npm WARN deprecated turf-distance@3.0.12: Turf packages are now namespaced: please use @turf/distance instead
npm WARN deprecated turf-helpers@3.0.12: Turf packages are now namespaced: please use @turf/helpers instead
npm WARN deprecated turf-bearing@3.0.12: Turf packages are now namespaced: please use @turf/bearing instead
npm WARN deprecated turf-destination@3.0.12: Turf packages are now namespaced: please use @turf/destination instead
npm WARN deprecated turf-invariant@3.0.12: 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
staeco@0.0.1 /Users/contra/Projects/staeco
└─┬ @turf/turf@3.5.2
  └─┬ @turf/line-slice-along@3.5.2
    ├─┬ turf-bearing@3.0.12
    │ └── turf-invariant@3.0.12
    ├── turf-destination@3.0.12
    ├── turf-distance@3.0.12
    └── turf-helpers@3.0.12

Updating the package.json of that module should fix all of these errors and make installs clean.

[tmcw]

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.

[tmcw]

3.5.3 published.