I am facing the same issue, my "resolution" was to remove a comment from the \vendor\api-platform\symfony\Bundle\Resources\public\graphiql\graphiql.min.js file.

This line contains a code example with import('./path/to/domAnimations').

Yep, this code is commented out.

// Asynchronous loading
/**
 * Used in conjunction with the `m` component to reduce bundle size.
 *
 * `m` is a version of the `motion` component that only loads functionality
 * critical for the initial render.
 *
 * `LazyMotion` can then be used to either synchronously or asynchronously
 * load animation and gesture support.
 *
 * ```jsx
 * // Synchronous loading
 * import { LazyMotion, m, domAnimations } from "framer-motion"
 *
 * function App() {
 *   return (
 *     <LazyMotion features={domAnimations}>
 *       <m.div animate={{ scale: 2 }} />
 *     </LazyMotion>
 *   )
 * }
 *
 * // Asynchronous loading
 * import { LazyMotion, m } from "framer-motion"
 *
 * function App() {
 *   return (
 *     <LazyMotion features={() => import('./path/to/domAnimations')}>
 *       <m.div animate={{ scale: 2 }} />
 *     </LazyMotion>
 *   )
 * }
 * ```
 *
 * @public
 */

Since assetmapper is not a javascript parser, it gets the paths it needs to resolve with a regex.

Perhaps this commit?
symfony/asset-mapper@21fe29b

Although that probably wasn't it because it just added unicode support.

Until recently, this issue threw a warning in the javascript console, but now it won't even load.

The regex grabs it, then

symfony/asset-mapper@21fe29b#diff-a6269ebc4116f5cfab61b63c4af5131c884e3f2267e442333760e1589de4b4eaR144-R169

I'll try to prepare a test maps some sort of fix.

I added a test, and am now attempting to fix the isCommentedOut method.

    public static function provideCompileTests(): iterable
    {
        yield 'import_in_multiline_comment' => [
            'input' => <<<EOF
// Asynchronous loading
/**
 *
 * function App() {
 *   return (
 *     <LazyMotion features={() => import('./path/to/domAnimations')}>
 *       <m.div animate={{ scale: 2 }} />
 *     </LazyMotion>
 *   )
 * }
 * ```
 *
 * @public
 */
EOF
            ,
            'expectedJavaScriptImports' => [],
        ];

So it turned out to be a change in the asset-mapper recipe to make import strict in development.

So it turned out to be a change in the asset-mapper recipe to make import strict in development.

The recipe update was the issue for me as well. Configuring this back to warn or ignore helped for now.

As @adrianrudnik said, the problem is the asset mapper, I removed this line from composer.json
"symfony/asset-mapper": "7.2.*"

And then I did run composer update

No, that's not the right solution, because the application may need asset-mapper. Instead, change

# config/packages/asset_mapper.yaml

framework:
    asset_mapper:
        # The paths to make available to the asset mapper.
        paths:
            - assets/
        missing_import_mode: warn

The problem is that the original recipe had the missing_import_mode set to strict.