Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Latest release not available at posted endpoint

See original GitHub issue

In Turf docs, under https://turfjs.org/getting-started, it indicates that one can require Turf from the following endpoint: https://npmcdn.com/@turf/turf@6.2.0-alpha.1/turf.min.js

At present, that endpoint returns: Cannot find "/turf.min.js" in @turf/turf@6.2.0-alpha.1

Issue Analytics

State:
Created 3 years ago
Comments:9 (5 by maintainers)

Top GitHub Comments

1reaction

rowanwinscommented, Mar 27, 2020

Hi @kuanb & @vincentsarago

We’ve amended the npm package so that the latest points back to the older version but doesn’t change the dist directory so all old CDN links should now work again.

1reaction

rowanwinscommented, Mar 27, 2020

Hey @vincentsarago

Sorry about that, we’ve just gotten a new contributor on board and this was our first release in years!

Unfortunately with those cdn links if you don’t use a named release just picks out the most recent release, and because we changed the location of turf.min.js it has freaked.

The old version you’ve would’ve been hitting is still available at https://unpkg.com/@turf/turf@5.1.6/turf.min.js

@mfedderly - we’ll need to have a think about this because this is breaking change. Perhaps even as a temporary measure we can put the compiled output back in the root dir as well.

Cheers Rowan