Turbo: Drive, Frames & Streams!

Hey @jmsche!

It works ok for me on node 19 - just doing a composer install, yarn install, and yarn watch all happen without any error on start/ and finish/ dir. It wouldn't surprise me if the build stopped working in newer Node versions (at least without updating your node deps), but I didn't hit any issues. Do you remember the problem you hit?

Cheers!

Hi Ryan,

Ran commands using node 18.10.0 here (retrieved via nvm IIRC, not sure if that matters).

Here is the error I get when I run yarn watch in the start folder:

yarn watch
yarn run v1.22.19
$ encore dev --watch
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db

Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
Running webpack ...

node:internal/crypto/hash:71
  this[kHandle] = new _Hash(algorithm, xofLen);
                  ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:71:19)
    at Object.createHash (node:crypto:133:10)
    at BulkUpdateDecorator.hashFactory (/home/jmsche/Downloads/start/node_modules/webpack/lib/util/createHash.js:145:18)
    at BulkUpdateDecorator.digest (/home/jmsche/Downloads/start/node_modules/webpack/lib/util/createHash.js:80:21)
    at NormalModule._initBuildHash (/home/jmsche/Downloads/start/node_modules/webpack/lib/NormalModule.js:874:53)
    at /home/jmsche/Downloads/start/node_modules/webpack/lib/NormalModule.js:914:10
    at processResult (/home/jmsche/Downloads/start/node_modules/webpack/lib/NormalModule.js:710:12)
    at /home/jmsche/Downloads/start/node_modules/webpack/lib/NormalModule.js:809:5
    at /home/jmsche/Downloads/start/node_modules/loader-runner/lib/LoaderRunner.js:399:11
    at /home/jmsche/Downloads/start/node_modules/loader-runner/lib/LoaderRunner.js:251:18 {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v18.10.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

The error seems to be the same for the finish directory.

I had the same problem with node v20.11.1 I ran export NODE_OPTIONS=--openssl-legacy-provider after that I can run yarn watch

Hey Yevhen,

Thanks for sharing it with others!

Cheers!

I had the same problem:

• Tried with v18.16.0 exactly the same problem
• Switched on v16.20.0 and worked and compiled

Hey Waldifubu,

Thanks for confirming it helped to you :)

Cheers!

Hey Jmsche,

Thanks for mentioning this! It might be helpful for others. I think we need to add a note about it in the course

Cheers!

Hey Stuart,

I suppose you're talking about this comment? https://symfonycasts.com/screencast/turbo/intro#comment-33200

Thanks for sharing your solution with others.

Cheers!

yes sorry

Change docker-compose.yaml to :

version: '3.7'
services:
    database:
        image: 'arm64v8/mysql:latest'
        environment:
            MYSQL_ROOT_PASSWORD: password
        ports:
            # To allow the host machine to access the ports below, modify the lines below.
            # For example, to allow the host to connect to port 3306 on the container, you would change
            # "3306" to "3306:3306". Where the first port is exposed to the host and the second is the container port.
            # See https://docs.docker.com/compose/compose-file/#ports for more information.
            - '3306'

Change .env file and use:
DATABASE_URL="mysql://root:password@127.0.0.1:3306/root?serverVersion=8.0.32"

then
docker-compose up -d

next
symfony console doctrine:database:create
symfony console doctrine:schema:update --force
symfony console doctrine:fixtures:load

next
symfony serve -d

next
export NODE_OPTIONS=--openssl-legacy-provider && yarn watch

this is how the installation is working on MacBook Air M2 / nodejs LTS (18.5.0 at the time of writing) / Docker Desktop Mac

would be nice if this help someone else to save 1 hour or so....

thx

The following change:
image: 'arm64v8/mysql:latest'
should not be done on an intel machine.
And thanks for the great tips!

Hey Staatzstreich,

Thank you for such a detailed tip!

Cheers!

Hey 👋
You are welcome and i like your courses!!!

Best,
Michael

Hey staatzstreich,

Thank you! We're delighted to hear such feedback, it makes our day ❤️
Stay tuned for more content soon ;)

Cheers!

Hey @kousaja1!

Thanks for posting this clear note! If you use the Docker database setup we describe in the README, you won't need this. But if you use your own MySQL instance without Docker (which is totally fine), then you're 100% correct 👍

Cheers!

Hi @weaverryan!

The thing is that the docker-compose provided (when you download the course code) uses mysql database, but the app is expecting posgresql database, so you need to change the .env file yourself.

Hey kousaja1!

If you're using the symfony binary, it'll detect the database container running and expose the DATABASE_URL for you. So if you have this setup, the DATABASE_URL value isn't used. But if you don't use the symfony binary, then you'll definitely need to tweak that. We mention that in the README, but it might not be clear enough.

Cheers!

Oh, that's lovely! I didn't know that the symfony binary is that smart! Thank you for the additional explanation. My bad.

Haha, no worries - it's a bit magic! And you were still right about needing to change .env if you don't use the full Docker AND symfony binary setup :).