Fix an edge case where lines where sometimes clipped incorrectly when points coincided with tile edges (by @DeZhao-Zhang) #161

Contributors

• @DeZhao-Zhang

Fix handling of features with empty coordinates — treat them the same way as features with null geometry (as per the spec).

Fix issues in some ESM setups because of an incorrect exports field in package.json.

• ⚠️ Breaking: drop CommonJS entry point and switch to ESM only for Node & bundlers + UMD bundle for browsers. #180
• ⚠️ Breaking: drop support for IE11 (you can still transpile on your end to keep it). #180
• Fix a rare edge case that could potentially lead to stack overflow by @district10 in #173 and @mlptownsend in #176
• Small performance optimizations by @vicb in #133, #132, #135
• Force getTile arguments as number by @andrewharvey in #128
• Fix a minor bug in tiling code by @CraigglesO in #130

Contributors

• @andrewharvey
• @vicb
• @CraigglesO
• @district10
• @mlptownsend

• Add generateId option for automatically filling feature id property (populating it with the index of the feature in a feature collection).
• Add promoteId option for filling feature id with a value from a specific feature property.

• Fix handling of features with id of 0. #107
• Minor fix for degenerate inputs.

Fixed a bug which caused a "max call stack size" error on certain degenerate input. #105

Fixed a bug with lineMetrics: true and MultiLineString geometries where only the first line was processed.

Fixed inconsistent clipping of features on tile boundary when buffer = 0. #102

• Added experimental lineMetrics: true option that adds mapbox_clip_start and mapbox_clip_end properties to all line features in the generated tiles, indicating which part of the original full line each feature represents.
• Turned GeoJSON-VT into a proper ES module (so you can do import geojsonvt from 'geojson-vt' in supported environments).