¿Un mundo sin sistemas de construcción?

In case anyone else gets an error about the environment variable GITHUB_TOKEN not being set: It's stored in a secret and Symfony's secrets require the PHP extension "sodium" to be loaded.

Neither composer check-platform-reqs nor symfony local:check:requirements mentions the extension. Maybe add it to composer.json of the course code?

Hey Marius,

Thanks for this tip! Please, correct me if I'm wrong, but I don't see we use Symfony secrets in this course. Is it something that you use internally for your project?

Cheers!

Hey Victor,

It's not being used in the course, but the downloadable code contains a secret called GITHUB_TOKEN (with the value "CHANGEME" in dev). I guess it's the one from chapter 21 in the "Symfony 6 Fundamentals: Services, Config & Environments" course.

Not a big deal, especially if you go through the courses in order. I just happened to do the courses on different computers and this one didn't have sodium installed yet.

Yea... this is a good tip - for some reason, some PHP installs still don't have Sodium. And, as you said, it's not actually needed. I think we can comment-out its usage to avoid the error entirely.

Hello!
And first of all, thank you for you course, once again it's a charm to follow it.

I have a question that I didn't find any help for:

let's say that I come from a good old webpack encore project. Nothing fancy here, I think it's a good candidate for a assetmapper conversion. My app.js is like this:

import './styles/globals.css';
import './styles/table.css';
import './styles/organisms/header.css';
import './styles/molecules/_header_navigation_menu.css';
import './styles/molecules/_header_authentication_menu.css';
import './styles/atoms/_header_link.css';
import './styles/atoms/_header_button.css';
import './styles/molecules/_header_popover.css';
import './styles/organisms/replay_research_form.css';
import './styles/organisms/replay_form.css';
import './styles/molecules/_replay_filters.css';
import './styles/molecules/_replay_searchPreview.css';
import './styles/molecules/_call_to_action.css';
import './styles/organisms/_ranking_table.css';

import './bootstrap.js'; // start the Stimulus application

As we can see, beside stimulus (I will handle its removal with your chapter 12!), it's just a bunch of css files (classic atomic design pattern). But, there is so any css files that I wonder if it's a good idea to add plain html <link tas for each of them? or is there a way to avoid having so many tags? Actually, the compilation is not that bad to allow dev to separate components CSS in a file per each.

What would you do in such a a situation? Stop having 15 .css files? Keep webpack? Put them all with assetmapper? Or do I miss a trick for this usecase?

Thank you in advance! Have a lovely day,

Hey @Nayte91!

I think this is a VERY legitimate question :). Somehow, though it feels totally normal to have 15 import statements for CSS files, it feels weird to have 15 link tags for those same 15 CSS files :). But I think we should not feel weird about this: we need to list all 15 CSS files somewhere, there's not really any difference between doing it as import statements of link tags :).

However, I think you might be referring more to the possible issue that 15 link tags means 15 requests for those CSS files, vs the 1 that this would compile to in Webpack. With HTTP/2, this is largely not a concern. However, there is certainly SOME upper limit where it is a problem (e.g. imagine you have 1000 CSS files), but I'm not sure where that is. My advice is to put those as 15 links tags and run Lighthouse on it to be sure it's not a problem. You could even - as we do in the last chapter - send a preload header to hint even EARLIER that these file are needed - https://symfonycasts.com/screencast/asset-mapper/preloading#preloading-via-a-header

My guess is that putting 15 link tags is a non-issue, but I get that it feels weird :). Time will tell whether this is something that we al "get used to" or if, perhaps, so many people find it weird for some reason that we add a layer to combine the files. But I'm hoping it doesn't come to that: that's the point of HTTP/2, it removes that need for combining files (so I hope we won't need to re-add it for some reason).

Cheers!

Hi guys:
If I understood correctly in the first video, I would not need Webpack Encore if I use AssetMapper? At least in most of the cases I mean
I am asking just to be sure.
Cesar

yep it is SO, when you are using modern browser, honestly pretty unbelievable, I remember the times of IE6 and now you can just write modern JS and it will work.... awesome thing!

Cheers!

"Symfony Gazette", excellent :D.