Typoscript is the wrong way for an integrator, to solve this problem. You can use fluid for this.

A Integrator will have access to the TYPO3-Template:
1. Use headerAssets
https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/8.6/Feature-79409-AutorenderAssetSectionsInFluidTemplateWithController.html
2. use Viewhelper uri.resource
https://docs.typo3.org/other/typo3/view-helper-reference/9.5/en-us/typo3/fluid/latest/Uri/Resource.html

If you really want to use typoscript, use the split-Function and the stdWrap to manually build your string
https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/Functions/Split.html

Remark: It is often a good suggestion to ask something like this in the slack-channel first.

sorry for contradicting you: There are enough scenarios where you want to do this with TypoScript. You can not only think of "normal websites" with Fluid.

You mentioned split-Function. Beside that, that this approach could just be a workaround: How do you get the final resulting cryptic public path for your file?

Dieter Porth wrote in #note-1:

Remark: It is often a good suggestion to ask something like this in the slack-channel first.

I already discussed this with a core team member.

It is already possible today. I am using this with typo3/cms-composer-installers v4 in TYPO3 v11 installations:

page.headerData.10 = TEXT
page.headerData.10 {
  value = <link rel="preload" href="{path : EXT:site/Resources/Public/Fonts/Roboto.woff2}" as="font" type="font/woff2" crossorigin="anonymous">
  insertData = 1
}

I provided also a PR to the docs to make it more clear on how to use:
https://github.com/TYPO3-Documentation/TYPO3CMS-Reference-Typoscript/pull/646

While it works with "path:" and for bc should continue to work for a while, neither the code, nor the documentation is clear, what exactly this "path" is meant for. Historically, when all files of a TYPO3 installation were public, this "function" returned a path relative to the TYPO3 installation. Now though, things are a bit more diverse.

Therefore I suggest to add a new function called "url:" that only accepts EXT: syntax and as a clear result, which is a public URL to this file (or an exception when a pubic URL to this file can not be created)

This works currently:

page.headerData {
  5 = TEXT
  5 {
    typolink {
      parameter = file:EXT:site/Resources/Public/Fonts/iconfont.woff2
      forceAbsoluteUrl = 1
      returnLast = url
    }
    wrap = <link rel="preload" as="font" type="font/woff2" href="|" crossorigin>
  }
}

See also \TYPO3\CMS\Core\LinkHandling\LegacyLinkNotationConverter::resolve()

Using typolink to resolve file urls is fine in my eyes, but what i really miss with it, is the possibility to add a cache buster since icon font files can change. The files sha1 would be perfect.

What do you think about adding a new Content Object that should ease preloads:

page.headerData.10 = PRELOAD
page.headerData.10.file = EXT:site/Resources/Public/fonts/iconfont.woff2

# or 

page.headerData.10 = PRELOAD
page.headerData.10.file = fonts/iconfont.woff2
page.headerData.10.extension = site

It would add all the the necessary attributes automatically + a cachebuster, if it's a local file

I also like your url example, because it's very short. Maybe "resourceUri" instead url, that always adds a cache buster?

page.headerData.10 = TEXT
page.headerData.10 {
  value = <link rel="preload" href="{resourceUri : EXT:site/Resources/Public/Fonts/Roboto.woff2}" as="font" type="font/woff2" crossorigin="anonymous">
  insertData = 1
}

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 4 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 5 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 6 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Just found this by searching for preload...
My problem is, that I want to add preload assets to the head by Fluid Template and not by TypoScript.
Why?
95% of my template that I realized formerly with TypoScript moved to Fluid Template and Fluid Templates of my content elements.
I can already use the f:asset.script and f:asset.css ViewHelper to add most of my resources to the site.
There is <f:section name="HeaderAssets"> to add more uncommon content to the head, but only once per Controller/Action context and not for example for many content elements on the same site.

I have to add multiple images for different screens per content element to the head to preload the right one.
https://web.dev/preload-responsive-images/

Jan, I think your problem is unrelated to this.
This was about providing the <f:resource.uri> functionality for TypoScript.
You are looking for a way to push stuff into <head> from Content Element templates.

Hi Jonas, thanks for your reply. My problem is not the exact same as in the post but has the same background.
I have to add resources to the head that have static paths `{f:uri.resource}` or generated `{f:uri.image}`.
Some maybe with a cache busting parameter like versionNumberInFilename.
As it feels more natural to me to use Fluid to add frontend resources, I just wanted to make sure it wasn't forgotten during implementation of such a feature.

Patch set 7 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 8 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 9 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 10 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 11 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 12 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 13 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 14 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 15 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 16 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 17 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 18 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 19 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 20 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 21 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 22 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 23 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 24 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 25 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 26 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 27 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 28 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 29 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018

Patch set 30 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018