Closed chalkpe closed 2 years ago
Thank @ChalkPE for the detailed report. It seems we forgot that the website was leveraging the CI configuration to determine the supported node version and we didn't update it after the recent changes.
I expect though that Node 12 support will be dropped once it reaches EOL at the end of this month. I'm not sure we want to work on a fix for something that is likely to disappear in 2 weeks. Do you have an opinion on this @lloydbenson?
Support plan
Context
16.14.0
node
standalone
What are you trying to achieve or the steps to reproduce?
~/static/lib/hapiInfo.json
was not found.assets/js/getModuleInfo
script, is also broken after recent changes of its external resource.jobs.test.strategy.matrix.node
inci-module.yml
is now an expression (string), not an array of node versions.What was the result you got?
npm run dev
npm run generate
:Adding
console.error(nodeYaml.data)
beforegetModuleInfo.js:122
:What result did you expect?
Required data is generated and page is built successfully.