Find a replacement for `php-parser`

[StyleShit]

It causes too many issues and seems incomplete.

See #13, #23, and:

eslint-plugin-php/src/language/php-source-code.ts

Lines 49 to 92 in 4230f6f

	findClosestKeyword(
	node: Node,
	keyword: string,
	): Omit<Location, 'source'> | null {
	const lines = this.lines;
	const nodeLoc = this.getLoc(node);
	for (let line = nodeLoc.start.line; line >= 0; line--) {
	const startColumn =
	line === nodeLoc.start.line
	? nodeLoc.start.column
	: lines[line]?.length;
	for (let column = startColumn ?? 0; column >= 0; column--) {
	const sliceStart = Math.max(0, column - keyword.length);
	const sliceEnd = sliceStart + keyword.length;
	if (lines[line]?.slice(sliceStart, sliceEnd) === keyword) {
	const locLine = line + LINE_START;
	return {
	start: {
	line: locLine,
	column: sliceStart,
	offset: this.getOffset({
	line: locLine,
	column: sliceStart,
	}),
	},
	end: {
	line: locLine,
	column: sliceEnd,
	offset: this.getOffset({
	line: locLine,
	column: sliceEnd,
	}),
	},
	};
	}
	}
	}
	return null;
	}

[StyleShit]

It won't be easy...

Just played around with @expreva/php-parser, on first glance it looks promising - works fine, and pretty fast.

The issue is that it's asynchronous, while ESLint parses the files synchronously:

https://github.com/eslint/eslint/blob/8ed32734cc22988173f99fd0703d50f94c60feb8/lib/services/parser-service.js#L32-L38

🥲🥲🥲

[StyleShit]

Tried using WASM:
WordPress/wordpress-playground#2203

Much slower, it's hard to extract comments, the locations are not ESTree compatible.

See: poc/php-parser-wasm