Skip to content

Commit

Permalink
minor #19369 [Encore] Update note instructing users to upgrade symfon…
Browse files Browse the repository at this point in the history
…y-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
  • Loading branch information
OskarStark committed Jan 3, 2024
2 parents 24fc2a4 + dd092c7 commit 8c4ec21
Showing 1 changed file with 2 additions and 5 deletions.
7 changes: 2 additions & 5 deletions frontend/encore/dev-server.rst
Original file line number Diff line number Diff line change
Expand Up @@ -77,12 +77,9 @@ server SSL certificate:
.. note::

If you are using Node.js 17 or newer, you have to run the ``dev-server`` command with the
``--openssl-legacy-provider`` option:
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.

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

CORS Issues
-----------
Expand Down

0 comments on commit 8c4ec21

Please sign in to comment.