In anticipation of the upgrade to node 10 by April 2019, we should test that npm install and the Docker deploy repo builds work with node 10.
The npm version will be the one corresponding to the specific node version in nvm.
This can probably wait until the move to Stretch is complete.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T321959 Tech Wishes - Maps service infrastructure deprecations | |||
| Open | None | T321789 Upgrade maps servers to node >= 14 | |||
| Duplicate | None | T210815 Upgrade kartotherian to latest upstream node-mapnik | |||
| Open | None | T213077 Migrate Kartotherian to node-mapnik >v4.2.1 to support libmapnik >3.1.x | |||
| Resolved | MSantos | T209990 Test Kartotherian/Tilerator with node 10 | |||
| Invalid | None | T195316 unmet peer dependency warning on kartotherian and tilerator builds | |||
| Resolved | MSantos | T188674 Upgrade node-mapnik to 3.7.x | |||
| Resolved | • Mholloway | T200284 Install mapnik 3.0.20 on Stretch | |||
| Resolved | None | T187481 Figure out Maki's Mapnik requirements |
Node 10 is only supported in node-mapnik >= 4.0.0.
https://github.com/mapnik/node-mapnik/blob/master/CHANGELOG.md#400
Last week I tested Kartotherian/Tilerator with a proper environment building mapnik pre-release master branch and node 10. The Dockerfile I created is here. I wrote a report and what I think that should be the strategy for the node 10 upgrade in another task at T213077: Migrate Kartotherian to node-mapnik >v4.2.1 to support libmapnik >3.1.x . I would say that this "investigation task" is ready for sign off.