Skip to content

Deprecation Warning with Node.js Versions Above 20.11.1 in bash-language-server #1119

Open
@Stephen291299

Description

@Stephen291299

Code editor

No response

Platform

ubuntu

Version

5.1.2

What steps will reproduce the bug?

Steps to Reproduce:

1)Install bash-language-server using npm.
2)Run the binary of bash-language-server in the terminal using Node.js version 21.5.0.
3)Observe the deprecation warning related to the punycode module.

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior?

Expected Behavior:

The bash-language-server should run without any deprecation warnings with Node.js version 21.5.0.

What do you see instead?

When running the binary of the bash-language-server with Node.js versions above 20.11.1, I expect the following:

1)The bash-language-server should run without any deprecation warnings related to the punycode module.
2)The functionality of the bash-language-server should not be affected by the deprecation warning, ensuring smooth operation and compatibility with newer versions of Node.js.
This expected behavior would ensure that developers can use the latest Node.js versions seamlessly with the bash-language-server without encountering deprecation warnings or compatibility issues.

Additional information

Issue Description:

I encountered a deprecation warning related to the punycode module when running the binary of the bash-language-server with Node.js version 21.5.0. The warning message is as follows:

(node:3351812) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

Additional Information:

1)Node.js version lower than 20.11.1 works correctly without any deprecation warnings.
2)Node.js version 21.5.0 is produce the deprecation warning related to the punycode module.
3)I think Node versions above 20.11.1 have faced this issue.

This issue seems to be specific to Node.js versions above 20.11.1. Any insights or suggestions on how to resolve this issue would be greatly appreciated. Thank you!

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions