Skip to content

Commit 8c4ec21

Browse files
committed
minor #19369 [Encore] Update note instructing users to upgrade symfony-cli for node.js 17+ tls compatibility (sarim)
This PR was merged into the 5.4 branch. Discussion ---------- [Encore] Update note instructing users to upgrade symfony-cli for node.js 17+ tls compatibility This note telling users to use `--openssl-legacy-provider` flag is no longer needed with certificate generated by latest symfony-cli. Context: symfony-cli/cert#4 symfony-cli/cert#7 symfony/webpack-encore#1187 Commits ------- dd092c7 [Encore] Update note instructing users to upgrade symfony-cli for node.js 17+ tls compatibility
2 parents 24fc2a4 + dd092c7 commit 8c4ec21

File tree

1 file changed

+2
-5
lines changed

1 file changed

+2
-5
lines changed

frontend/encore/dev-server.rst

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -77,12 +77,9 @@ server SSL certificate:
7777
7878
.. note::
7979

80-
If you are using Node.js 17 or newer, you have to run the ``dev-server`` command with the
81-
``--openssl-legacy-provider`` option:
80+
If you are using Node.js 17 or newer and ``dev-server`` fails to start with TLS error, the certificate file might be generated by an old version of **symfony-cli**. Upgrade **symfony-cli** to the latest version, delete the old ``~/.symfony5/certs/default.p12`` file, and start symfony server again.
8281

83-
.. code-block:: terminal
84-
85-
$ NODE_OPTIONS=--openssl-legacy-provider npm run dev-server
82+
This generates a new ``default.p12`` file suitable for use with recent Node.js versions.
8683

8784
CORS Issues
8885
-----------

0 commit comments

Comments
 (0)