lookbehind not supported on safari < 17 about anchorme.js

[rhysburnie]

I'm no regExp expert I was just going by this for rough equiv of look behind https://stackoverflow.com/a/74994273/738957
This was crashing our entire app, if this fix has a side effect on some anchorme links its preferable over an entire crash.
However if there is a better fix would be good to know.

[alexcorvi]

Please check the latest version 3.0.7

[lionel-rowe]

Current fix gives wrong capture group results, as there are more capture groups in the lookaround-supporting regex than there are in the compat-mode regex:

const OriginalRegExp = globalThis.RegExp;

class SafariRegExp extends OriginalRegExp {
    constructor(pattern, flags) {
        super(pattern, flags)
        if (String(pattern).includes('(?<=')) {
            throw new SyntaxError('idk what (?<= even means')
        }
    }
}

globalThis.RegExp = SafariRegExp

const anchorme = (await import('https://esm.sh/v135/[email protected]')).default
console.info(
    anchorme.list(
        `https://example.xyz example.com [email protected] file:///filename.txt 192.168.1.1`,
        false,
    )
)

// expected:
[
	{ start: 0, end: 19, string: 'https://example.xyz', isURL: true, protocol: 'https://', /* ... */ },
	{ start: 20, end: 31, string: 'example.com', isURL: true, protocol: undefined, /* ... */ },
	{ start: 32, end: 46, string: '[email protected]', isEmail: true, local: 'user', /* ... */ },
	{ start: 47, end: 67, string: 'file:///filename.txt', isFile: true, protocol: 'file:///', /* ... */ },
	{ start: 68, end: 79, string: '192.168.1.1', isURL: true, protocol: undefined, /* ... */ },	
]
// actual:
[
	{ start: 0, end: 19, string: 'https://example.xyz', reason: 'unknown' },
	{ start: 20, end: 31, string: 'example.com', reason: 'unknown' },
	{ start: 32, end: 46, string: '[email protected]', reason: 'unknown' },
	{ start: 47, end: 67, string: 'file:///filename.txt', isURL: true, protocol: undefined, /* ... */ },
	{ start: 68, end: 79, string: '192.168.1.1', reason: 'unknown' },	
]

I'll have a PR up with a fix shortly — I think with the fix, reason: "unknown" can also be removed entirely as it should never occur.