Скачать или смотреть Resolving the ERR_OSSL_EVP_UNSUPPORTED Error in Node.js with Webpack

Learn how to troubleshoot the `ERR_OSSL_EVP_UNSUPPORTED` error in Node.js and Webpack while developing your applications on Windows. Discover effective solutions to configure your package.json properly.
---
This video is based on the question https://stackoverflow.com/q/76361634/ asked by the user 'Siri How' ( https://stackoverflow.com/u/3094578/ ) and on the answer https://stackoverflow.com/a/76362238/ provided by the user 'dave_thompson_085' ( https://stackoverflow.com/u/2868801/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Node.js Webpack ERR_OSSL_EVP_UNSUPPORTED

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding and Fixing the ERR_OSSL_EVP_UNSUPPORTED Error in Node.js

As developers, we all know the frustration of running into errors that seem to appear out of nowhere, especially when working in environments like Node.js with tools like Webpack. Recently, many Node.js users have encountered SSL-related errors, notably ERR_OSSL_EVP_UNSUPPORTED. If you've found yourself stuck with this issue while trying to launch your application, don’t worry. In this guide, we'll explore this error, its possible causes, and how to resolve it seamlessly.

The Problem: What is ERR_OSSL_EVP_UNSUPPORTED?

This error typically indicates a problem related to cryptographic functions that rely on OpenSSL when using Node.js. It’s worth noting that if your application was running perfectly before, one may wonder why these errors have suddenly cropped up. Here are common questions developers have about this situation:

Why did SSL issues arise suddenly?

Many developers on Node.js version 18 (like v18.14.0) are experiencing this problem because this version uses OpenSSL 3.0, which includes stricter policies on cryptographic algorithms. It may seem as though something has changed on your machine, but it's possible that a recent change in your code or the dependencies could be triggering the legacy crypto algorithms that the new OpenSSL restrictions block.

Why do I need to set NODE_OPTIONS every time?

When you run certain commands, you might have to specify that your environment should allow the legacy provider for OpenSSL. Failing to set this could lead to the ERR_OSSL_EVP_UNSUPPORTED error reappearing.

Solution: Configuring Your Environment to Avoid the Error

Temporary Fix via Command Prompt

The quickest way to get your application running again is to use the terminal command:

[[See Video to Reveal this Text or Code Snippet]]

Running this command allows your app to launch without the SSL error, but it can be tedious to type it each time you start your development server.

A Permanent Fix in package.json

To eliminate the redundancy, you can modify your package.json file's scripts section. However, keep in mind that configuring this on Windows requires a different approach due to how environment variables are handled.

Current Configuration Attempt

Here’s the current structure you might have been trying to implement:

[[See Video to Reveal this Text or Code Snippet]]

The issue with this command is that it may cause process.env.NODE_ENV to become undefined.

Correct Syntax for Windows

On Windows, you can't set multiple environment variables in one line. Instead, you should separate them with multiple set commands. Here’s how you can rewrite the watch script correctly:

[[See Video to Reveal this Text or Code Snippet]]

This way, the NODE_ENV variable remains defined, and you can run your app without encountering SSL errors every time.

Conclusion

Running into the ERR_OSSL_EVP_UNSUPPORTED error can be disruptive, but understanding the reason behind it and configuring your environment properly can help you overcome this hurdle. By using the provided command in the command prompt or updating your package.json, you can ensure that your Node.js applications run smoothly on your Windows machine.

If you encounter further issues or have questions on related topics, feel free to reach out! Happy coding!