Skip to content

fix: deprecation warning crash when no Node.js environment available #47769

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

trop[bot]
Copy link
Contributor

@trop trop bot commented Jul 16, 2025

Backport of #47700

See that PR for details.

Notes: none.

Co-authored-by: Shelley Vohr <shelley.vohr@gmail.com>
@trop trop bot requested review from codebytere and a team July 16, 2025 10:46
@trop trop bot added 38-x-y backport This is a backport PR semver/patch backwards-compatible bug fixes labels Jul 16, 2025
@VerteDinde VerteDinde merged commit e268940 into 38-x-y Jul 16, 2025
60 of 61 checks passed
@VerteDinde VerteDinde deleted the trop/38-x-y-bp-fix-deprecation-warning-crash-when-no-node-js-environment-available-1752662767313 branch July 16, 2025 19:19
@release-clerk
Copy link

release-clerk bot commented Jul 16, 2025

No Release Notes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
38-x-y backport This is a backport PR semver/patch backwards-compatible bug fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy