fix(ci): make npm package tests compatible with Node.js 12#618
Merged
joaoopereira merged 3 commits intodevelopment-add-support-for-fallback-repositoriesfrom Dec 3, 2025
Merged
Conversation
…ompatibility Co-authored-by: joaoopereira <3718704+joaoopereira@users.noreply.github.com>
Contributor
Author
|
Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Copilot
AI
changed the title
[WIP] Add support for fallback repositories
fix(ci): update Node.js to 18 for Jest compatibility
Nov 28, 2025
Member
|
@copilot can you make it compatible with node 12 instead of changing the node version? |
- Downgraded Jest from v29.7.0 to v27.5.1 (supports Node.js 12) - Downgraded axios from v1.7.9 to v0.27.2 (uses CommonJS, not ESM) - Downgraded http-proxy-agent from v7.0.2 to v5.0.0 (supports Node.js 12) - Downgraded https-proxy-agent from v7.0.5 to v5.0.1 (supports Node.js 12) - Updated proxy agent usage to use the v5.x API Co-authored-by: joaoopereira <3718704+joaoopereira@users.noreply.github.com>
Contributor
Author
Fixed in 9526b26. Changed the dependencies to versions compatible with Node.js 12:
Also updated the proxy agent API usage in postinstall.js and tests to use the v5.x API (direct exports instead of named exports). |
Copilot
AI
changed the title
fix(ci): update Node.js to 18 for Jest compatibility
fix(ci): make npm package tests compatible with Node.js 12
Nov 28, 2025
joaoopereira
merged commit 2a5b2e5
into
development-add-support-for-fallback-repositories
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CI build failing because Jest 29.7.0 and other dependencies require Node.js 14+ but workflow used Node.js 12.
Changes
29.7.0to27.5.1(last version supporting Node.js 12)1.7.9to0.27.2(last version with CommonJS exports)7.0.2to5.0.0(last version supporting Node.js 12)7.0.5to5.0.1(last version supporting Node.js 12)postinstall.jsand tests to use the v5.x API (direct exports instead of named exports)actions/setup-nodefromv2tov4for securityRoot Cause
Jest 29.7.0 uses optional chaining (
?.) which isn't supported in Node.js 12:Additionally, axios 1.x uses ESM-only exports and proxy-agent v6+ requires Node.js 14+.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.