@tristen it looks like tests using Node 10 are failing, which I believe is due to the update to eslint. Do you think it would make sense to update node_js in https://github.com/mapbox/polyline/blob/master/.travis.yml to more recent versions?

@dpdiliberto that seems like a sensible change to me 👍. Maybe we can replace 10 and 12 with more recent 16 and 18 versions.

Thanks @tristen , I updated the Node versions, and also upgraded the Travis build environment (per https://travis-ci.community/t/the-command-npm-config-set-spin-false-failed-and-exited-with-1-during/12909/7), since I was running into the following build error:

$ nvm install 18
node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by node)
node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by node)
node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node)
node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by node)
node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by node)
node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node)
The command "npm config set progress false" failed and exited with 1 during .

All checks are passing now 👍 .

Thanks @dpdiliberto and @tristen , please help publish a new release to NPM.

@leslieli done! https://www.npmjs.com/package/@mapbox/polyline/v/1.2.1

Thanks @tristen .

Looks upgrading the meow to v9 doesn't fix the issue #84, it is still referencing the [email protected], not v7.5.2+

└─┬ @mapbox/[email protected]
  └─┬ [email protected]
    ├─┬ [email protected]
    │ └── [email protected]
    └─┬ [email protected]
      └─┬ [email protected]
        └─┬ [email protected]
          └── [email protected]

@tristen @dpdiliberto

👋 @leslieli want to put a pull request together that addresses the issue? I'd be happy to review and cut a new release.

@tristen I am not quite familiar with the project and would like to suggest someone in your team could help on this. If possible, could you provide the estimation - when we can expect the fix release? Thanks.