Skip to content

Fix workflow: drop --openssl-legacy-provider flag (Node 16 incompatible)#163

Merged
lukaskywalk merged 1 commit into
UBIKhr:masterfrom
lukaskywalk:fix-node-options
Apr 29, 2026
Merged

Fix workflow: drop --openssl-legacy-provider flag (Node 16 incompatible)#163
lukaskywalk merged 1 commit into
UBIKhr:masterfrom
lukaskywalk:fix-node-options

Conversation

@lukaskywalk
Copy link
Copy Markdown
Collaborator

Summary

PR #162's deploy run failed at the install step:

`node: --openssl-legacy-provider is not allowed in NODE_OPTIONS`
`Process completed with exit code 9.`

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

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>
@lukaskywalk lukaskywalk merged commit 9586c03 into UBIKhr:master Apr 29, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant