Initially to be used by the Zotero replacement (which doesn't work with node 6). Later on other node-based apps can migrate.
This is complex to build/package and node 10 packages will only be provided for stretch-wikimedia.
MoritzMuehlenhoff | |
Aug 31 2018, 11:05 AM |
Initially to be used by the Zotero replacement (which doesn't work with node 6). Later on other node-based apps can migrate.
This is complex to build/package and node 10 packages will only be provided for stretch-wikimedia.
One notable change which is to be expected from moving to 10:
Some node modules ship binary blobs in their modules and the official node packages are build against OpenSSL 1.0.2. nodejs 10 only supports OpenSSL 1.1 (which has a different ABI/API) and then those modules fail to load or throw runtime errors
Upstream discussion is at https://github.com/nodejs/node/issues/21897, but there's no real solution
All node binary packages will need to be built for our environment and not fetched from npm (which is the clean approach anyway), so packages moved to node 10 will need to be reviewed if any of the deps is affected by this.
All node binary packages will need to be built for our environment and not fetched from npm (which is the clean approach anyway)
For most of node services we actually build binary dependencies ourselves already with a docker build script, so this shouldn't be an issue. We even switch off node-pre-gyp in some cases to explicitly avoid fetching pre-built binaries.
This is complex to build/package and node 10 packages will only be provided for stretch-wikimedia.
Will nodejs 10 packages be in a separate component for stretch-wikimedia, or will they replace the nodejs 6 packages currently in stretch-wikimedia's main?
nodejs 10 packages will be in a separate repository component, allowing applications to gradually move over. We'll continue to support nodejs 6 with security updates until all applications are migrated to 10.
Change 460787 had a related patch set uploaded (by Muehlenhoff; owner: Muehlenhoff):
[operations/puppet@production] Add component/node10 for stretch-wikimedia
Change 460787 merged by Muehlenhoff:
[operations/puppet@production] Add component/node10 for stretch-wikimedia
nodejs 10 packages for stretch-wikimedia are now available in the repository component "component/node10" for testing. I'm keeping this bug open to track possible further additions (addons etc.)
Change 482392 had a related patch set uploaded (by Krinkle; owner: Krinkle):
[integration/config@master] Create node10 image
Change 482572 had a related patch set uploaded (by Krinkle; owner: Krinkle):
[integration/config@master] Create node-10-docker job template and use for Fresnel
Change 482573 had a related patch set uploaded (by Krinkle; owner: Krinkle):
[integration/config@master] Add 'control' files for node10 images
Change 482573 merged by jenkins-bot:
[integration/config@master] Add 'control' files for node10 images
Change 482572 merged by jenkins-bot:
[integration/config@master] Create node-10-docker job template and use for Fresnel
Change 482755 had a related patch set uploaded (by Krinkle; owner: Krinkle):
[integration/config@master] Create generic npm-test job for Node 10 (and use for jsdoc/wmf-theme)