Fix workflow: drop --openssl-legacy-provider flag (Node 16 incompatible)#163
Merged
Merged
Conversation
That flag is only valid on Node 17+ (where OpenSSL 3 broke older build tools). With Node 16 — which is what the workflow uses — Node refuses to start with the flag and exits with code 9, breaking the deploy. Node 16 already ships OpenSSL 1.1, so webpack 4 and node-sass work without any compatibility flags. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
Summary
PR #162's deploy run failed at the install step:
The `--openssl-legacy-provider` flag was added defensively for Node 17+ (where OpenSSL 3 broke older build tools). It doesn't exist on Node 16 — Node refuses to start. Removing it.
Node 16 ships OpenSSL 1.1, so Webpack 4 / node-sass build cleanly without any flags.
Test plan
🤖 Generated with Claude Code