TYPO3 Core

Import map resolution without a cache-bust suffix (note: this is
currently not used in TYPO3 backend as we do not have cache-bust
prefixes yet), missed to join a previously splitted path-string
via slashes, when a prefix based import-declaration was used to
calculate the resulting URL of an import (usecase: calculate the
URL of a bare module specifier for usage in a `<script src="">`
tag, where bare module specifiers (`@typo3/backend/foo.js`) can
not be used.

Note that this bug is not exposed when the import-map paths are
recursively pre-calculated in `computeImportMaps()`, only if
package versions are hashed into public resource paths. That
means this fix is a preparation for #98481.