TYPO3 Core

Benni Mack wrote in #note-2:

Hello Christian,

do you want to get the inline code BEFORE the included external file?

for this example yes, but not only for inline-code.

Wouldn't maybe using "defer" for the external script solve this? Then the inline javascript would get parsed first.

Personally I don't think adding an order to javascripts is a solution that should be recommended (even though I understand the need).

Nowadays I would rather like to recommend building isolated javascript files that have no influence/dependency on each other. If they do, they should IMO be bundled, possibly by independent tooling (webpack, vite, etc.). What do you think?

@Garvin Hicking
hmm, I'm a fan of simple things, which doesn't exactly include all those package managers like webpack. :)
It would also be easier for beginners to understand, I would think ;)
Besides, I think it's possible in TypoScript, so why not in FLUID?
I don't know exactly how the FLUID is assembled at this point, if all the scripts / src'es are in an array before the HTML rendering, it shouldn't be a big problem to run a ksort() via the “identifier”. Maybe an additional TypoScript option / flag to switch the sorting on and off?

Fair enough :)

I haven't checked in on how TS vs. fluid handles prioritization. Since it hasn't gained traction to get addressed in 4 years I'm not sure we will find someone to look into it, so I just wanted to offer an alternative other than "waiting for godot". ;)