Closed njvb closed 1 month ago
This issue does not seem to follow the issue template. Make sure you provide all the required information.
Hey @njvb, thanks for reaching out and for providing details of what you observed. Looking through the provided information, it seems like this is a similar issue to #7747.
To keep a single line of communication, I'll be closing this as a duplicate. Could you please leave a comment or a thumbs up on the original issue. If you think this is a mistake, feel free to ask this to be reopened.
[REQUIRED] Environment info
firebase-tools: 13.22.0
Platform: macOS Monterey 12.3
[REQUIRED] Test case
This issue pertains to a deprecation warning emitted by the Firebase CLI during the deployment process. There is no specific code or test case involved.
[REQUIRED] Steps to reproduce
Ensure Environment Setup:
Run the Deployment Command:
firebase deploy --only hosting
Observe the Deprecation Warning in the Terminal Output.
[REQUIRED] Expected behavior
The Firebase CLI should deploy the project without emitting any deprecation warnings related to the `punycode` module, ensuring a clean and warning-free deployment process.
[REQUIRED] Actual behavior
During deployment, the Firebase CLI emits a deprecation warning for the `punycode` module. This warning originates from the `whatwg-url` package, which is a dependency of `firebase-tools`. The warning message is as follows:
[REQUIRED] Additional Information
Dependency Inspection:
npm ls punycode
within the project directory returns empty, indicating no direct dependencies onpunycode
.Trace Deprecation Output:
Suggested Action:
Update the
whatwg-url
dependency withinfirebase-tools
to eliminate the use of the deprecatedpunycode
module. This update will ensure compatibility with newer Node.js versions and prevent deprecation warnings during deployments.