Problem with negative look-behind causing Safari to explode

[tholder]

Ziggy version

2.x

Laravel version

11

Description

I'm using Laravel with Inertia and React.

It's the (?i:BASE64|) part of the route and I believe it is because safari doesn't support a negative look-behind. Before I discovered the offending route (as safari is such a pain to debug in), I did manage to eliminate it with an amend on atomica-software#1

Fix is easy enough for me, but this is a nasty safari only problem that could catch people out.

Some references:

https://stackoverflow.com/questions/51568821/works-in-chrome-but-breaks-in-safari-invalid-regular-expression-invalid-group
https://caniuse.com/js-regexp-lookbehind

Ziggy call and context

Simple call to route().params.team

Could potentially just be useRoute() call. Had some issue determining this.

Ziggy configuration

"image.avatar": {
            "uri": "image/{type}/{id}/{hash}/{format?}",
            "methods": [
                "GET",
                "HEAD"
            ],
            "wheres": {
                "id": "[0-9]+|[0-9a-f\\-]+",
                "type": "user|contact",
                "format": "(?i:BASE64)|"
            },
            "parameters": [
                "type",
                "id",
                "hash",
                "format"
            ]
        },

Trimmed for sensitivity but this is the route causing a problem.

Route definition

Route::get('/image/{type}/{id}/{hash}/{format?}', [ImageResourceController::class, 'show'])
    ->name('image.avatar')
    ->where('type', 'user|contact')
    ->where('id', '[0-9]+|[0-9a-f\-]+')
    ->where('format', '(?i:BASE64)|')
    ->withoutMiddleware(['web']);

[bakerkretzmar]

What exactly is the error you're getting? Does it happen everywhere in your app when Ziggy loads or only when you're making specific calls using that route? Is it something inside Ziggy in combination with your route causing this error or is it just the (?i:...) that Safari can't handle?

[tholder]

It blows up the entire app, the call to route().params I believe is what does it. Here is the console in Safari when I finally worked out what the issue was.

Not saying this is something that necessarily needs fixing because my route is not good and it was an easy fix, but, it took me days to debug this (mainly because Safari is a POS!).

The error was "SyntaxError: Invalid regular expression: unrecognized character after (?"

Thanks!