Encore, Symfony & API Platform

Fixed by updating the package.json

{
    "browserslist": [
        "defaults"
    ],
    "devDependencies": {
        "@symfony/webpack-encore": "^0.30.0",
        "bootstrap": "^4.4.1",
        "core-js": "^3.0.0",
        "eslint": "^6.7.2",
        "eslint-config-airbnb-base": "^14.0.0",
        "eslint-plugin-import": "^2.19.1",
        "eslint-plugin-vue": "^6.0.1",
        "regenerator-runtime": "^0.13.2",
        "sass": "^1.29.0",
        "sass-loader": "^8.0.0",
        "webpack-notifier": "^1.6.0"
    },
    "license": "UNLICENSED",
    "private": true,
    "scripts": {
        "dev-server": "NODE_OPTIONS=--openssl-legacy-provider encore dev-server",
        "dev": "NODE_OPTIONS=--openssl-legacy-provider encore dev",
        "watch": "NODE_OPTIONS=--openssl-legacy-provider encore dev --watch",
        "build": "encore production --progress",
        "lint": "node_modules/.bin/eslint assets/** --ignore-pattern *.scss --ignore-pattern *.gif --ignore-pattern *.png"
    }
}

Hey @atournayre,

Thanks for sharing your solution. That issue is a headache, especially with software which has lot of updates.

Cheers!

Hey Msthzn,

Hm, did you download the course and and started from start/ directory? Did you run all the instructions from the README.md file inside? What exactly command are you running when seeing this error? Because I just ran "yarn install" and "yarn watch" and didn't see this error. Btw, it feels like a warning, so probably you can just ignore it if that's just your learning project.

Cheers!

Followed 25 episodes. So far no problems yet.

Hey Ruslan I.!

You already answered your own question, but yes, absolutely. The "start" code is identical to that. However, for Vue part 2, that won't be the case. The starting code for that is only available by downloading from the site (which is for subscribers). You CAN use the "finish" code from what you did on Vue 1... but sometimes we upgrade and tweak a few things between tutorials (I try to minimize that, but it's unavoidable to a point).

Cheers!

Hey davidmintz!

Thanks for the thoughtful message. I think war sucks in any context. The cost to innocent civilians is real, and horrible and huge. At the end of the day, we can't comment on every conflict or issue. However, *this* war is directly affecting a member of our team.

If you'd like to discuss further, I'd appreciate an email to ryan@symfonycasts.com - just so we can keep the conversation below the videos technically relevant.

Cheers!

I hear you. Also horrified that a member of your team is in the middle of it, and fervently hoping he comes out of it ok.

Hi, Maxim!

That is a very tough question to answer, as the front-end situation is not as stable as back-end where Symfony clearly dominates. Even as close as a few months ago, I would definitely answer with ReactJS or VueJS. Any of those frameworks are equally powerful and it really depends on personal choice as to what route to go for a project! But with the recent news about Symfony-ux, StimulusJS and Turbo, the entire universe seems to be shaken. I would definitely say that Stimulus + Turbo is the future of front-end, at least for Symfony projects, because this seems to be *just* what Symfony needs! (Go take a look at our Stimulus and Turbo tutorials if you whish! They are really good!)

Agh! So many (great) choices.

I have been writing Javascript since about 1998, and trust me: it's not an advantage. I adopted jQuery and jQuery-ui some years ago, stayed there for years, and it's taken me till about now to start advancing into the modern age -- and it's really fun to be learning this. Oh my, Javascript, how you've grown!

Hi David!

The JavaScript ecosystem has indeed grown and matured A LOT during the past 6 or so years. It's quite remarkable! I'm glad you find this useful! I think you will love the stimulus/turbo tutorials as well!

Hey Karl C.

Double check your database URI is set correct in your .env file and that you don't have a .env.local overriding it. Another thing to check is the database server is running and you have the PHP PDO module configured

Cheers!

Thanks. The line for pdo_mysql was commented out in the php.ini. Works now.

Hey @Aaron!

Ah, yup! There is an issue! I've been mucking around lately on some of our tutorials upgrading the dependencies a little bit so that the code would work on PHP 8. Apparently (I just discovered the same issue on a different tutorial), I ended up with a bad combination of SensioFramworkExtraBundle and Doctrine. I'm going to get this fixed up ASAP.

In the mean time, here is the fix:

compose up sensio/framework-extra-bundle doctrine/migrations

(the doctrine/migrations upgrade is only needed if you're using PHP 8 + MySQL, so I mentioned it to be safe).

Cheers!

Hey Chris L.!

Give me a little time to check into this. Historically, we have purposely fixed our code downloads at the lowest PHP version that we support - so 7.2.9 for this tutorial. That prevents Composer from downloading dependencies that might only work on higher versions (e.g. 7.3 or 8.0), which would make the tutorial not work for users on 7.2. The idea is to get the tutorial code to work for as many people as reasonably possible.

But, PHP 8 is an extra challenge :P. If we tell Composer to use PHP 7.2 when downloading the dependencies, it's highly likely (almost guaranteed) that some dependencies will be downloaded that work on PHP 7.X, but do not work on PHP 8.0. I need to think about the best way we might solve this.

However, even though it's more work than I'd want you to have to do, you're absolutely on the right track with updating the dependencies. For the specific Doctrine\Common\Persistence\ObjectManager issue, change the use statement in AppFixtures to Doctrine\Persistence\ObjectManager. There may be other changes you need to make, but that will hopefully take care of that one ;).

Cheers!

Thanks - that did indeed fix that issue but ended up with some others. What I am going to try instead is creating a blank project, adding in the required packages via composer and then copying across the code into my project to see if I can get it working that way.

Thanks once again for your help, hopefully I'll manage to get this lot working as the course looks really good.

Hey Chris!

That’s sounds like a good plan - I can’t think of anything in the code (that you’ll be copying over) that would need adjustment with slightly newer dependencies.

If you do hit any issues, let me know.

Cheers!

Hey AbelardoLG,

Hm, try these steps:
php bin/console doctrine:database:create
php bin/console doctrine:schema:create
php bin/console doctrine:fixtures:load

I.e. use "doctrine:schema:create" instead of the migration, most probably the migration is not complete on your local setup or you messed up with some migrations

Cheers!

The issue here comes from my last question you gently replied.

Cheers.

Hey AbelardoLG,

Ah, great! I'm glad it's not a problem for you anymore :)

Cheers!

Hey AbelardoLG,

Yeah, in latest major MySQL version there're some problems with root user to access the DB from PHP script. So, the easiest solution is to create a new user like you did, e.g. call it "symfony". But you have to grant all the required permissions to that new user! Please, make sure that user has permissions to create databases, etc. You can find a lot of useful resource on the internet how to do it properly. Also, use "mysql" command in your terminal to check the credentials. You can access the MySQL with the new credentials - then you should have access from the PHP script as well using valid credentials

As an alternative solution - you can consider using Docker to spin up your MySQL server in a container and expose it to your local machine.

Cheers!

Yes, I granted all permissions to "symfony".
And yes, I will use Docker in order to eliminate any headache.
Thanks for your pieces of advice, Victor. :) Best regards.

Hey AbelardoLG,

Ah, ok... I probably know the problem you have... From the DATABASE_URL you showed above I can suppose that you may have problems with the password as it contains some extra chars, most likely "$" causes this problem. Try to set a simple password with numbers and letters only, i.e. without any extra chars, e.g. "CYFzw10Am" and try again - this should work. The special chars should be probably avoided or escaped properly, easier to avoid them for the passwords you set via env variables :)

Cheers!

HOORAY!
That was the reason of my headache!

Bigtor! ;)

Haha, awesome :)

Cheers!

Hey Sjoerd!

Thanks for the note - sometimes we DO miss things like this :). We don't actually show the setup in the tutorial, but in the first chapter - https://symfonycasts.com/sc... - we mention that you should follow the README.md file in the code download to get things working. You might have just not seen that? Or was it not obvious (or was the README missing details)?

Cheers!

Hi Ryan.

I actually did find the README.md you are referring to. It is in the "finish" folder rather than the "start" folder, which I used during the tutorial.
I guess I expected it to be in start, never looked any further.

Keep up the great tutorials!

Have a great day!

Hey Sjoerd!

> I actually did find the README.md you are referring to.

Excellent!

> It is in the "finish" folder rather than the "start" folder, which I used during the tutorial.
> I guess I expected it to be in start, never looked any further.

Hmm, it should also be in the start/ directory - that's actually the MOST important spot. I just double-checked the code download, and it does appear to be there... so how knows :). Anyways, it looks like all is good now. Thanks again for reporting any potential "weirdness" that you see!

Cheers!

Thank you for your kind words, Monia! Stay tuned for part 2 of this tutorial where, at the end, we show just that! :)

Hi Gilson!

We use NodeJS under the hood in this tutorial as the technology upon which Webpack and Encore work. We also use Yarn (although npm can be used as well) as our package manager for downloading and maintaining the packages needed in the application.

Being this a Vue tutorial (where we focus on the front end in an application written in Symfony), we won't be using NodeJS to render pages server side or writing scripts ourselves.

I hope this helps clarify your question!

Hi Moulaye!

It seems you've forgotten to include your webpack aliases to the TypeScript tsconfig file. You can find documentation here:

<a href="https://www.typescriptlang.org/tsconfig#paths&quot; target="_blank">https://www.typescriptlang.org/tsconfig#paths&lt;/a&gt;

A good example of what you need to do would be:

{
   "baseUrl": "./assets",
   "paths":  {
      "@": ["js"],
      "vue_app": ["assets/vue"]

   }

}

Hope this helps!

Hi Matias, thank you for your response, I was doing something similar. But you right maybe i'm missing something in my tsconfig, I will investigate. Thank you alot