feat(formatter): keep parser options consistent for all formatter usages

[Dunqing]

Copy from oxfmt

oxc/apps/oxfmt/src/service.rs

Lines 45 to 54 in adda5f5

	let ret = Parser::new(&allocator, &source_text, source_type)
	.with_options(ParseOptions {
	parse_regular_expression: false,
	// Enable all syntax features
	allow_v8_intrinsics: true,
	allow_return_outside_function: true,
	// `oxc_formatter` expects this to be false
	preserve_parens: false,
	})
	.parse();

[Copilot]

Pull Request Overview

This PR ensures consistent parser options configuration across all formatter usage examples and tests by standardizing the ParseOptions struct initialization. The changes make the parser configuration explicit and consistent rather than relying on default values that might vary.

• Replaces ParseOptions::default() with explicit option values
• Adds explicit flags for parse_regular_expression, allow_v8_intrinsics, and allow_return_outside_function
• Includes helpful comments explaining the formatter's expectations

Reviewed Changes

Copilot reviewed 3 out of 5 changed files in this pull request and generated no comments.

File	Description
tasks/prettier_conformance/src/lib.rs	Updates parser options to use explicit configuration instead of defaults
tasks/benchmark/benches/formatter.rs	Standardizes parser options with explicit values for consistency
crates/oxc_formatter/examples/formatter.rs	Aligns example code with consistent parser option configuration

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Dunqing]

• feat(formatter): keep parser options consistent for all formatter usages #13884 : 2 dependent PRs (#13885 , #13892 ) 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #13884 will not alter performance

_{Comparing 09-17-feat_formatter_keep_parse_options_consistent_for_all_formatter_usages (2cead8b) with main (91c88e2)¹}

Summary

✅ 37 untouched

Footnotes

1. No successful run was found on main (2cead8b) during the generation of this report, so 91c88e2 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[leaysgur]

We will add Formatter::parser_options() one day?

[leaysgur]

Merge activity

• Sep 18, 11:13 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Sep 18, 11:19 PM UTC: leaysgur added this pull request to the Graphite merge queue.
• Sep 18, 11:24 PM UTC: Merged by the Graphite merge queue.

[Dunqing]

We will add Formatter::parser_options() one day?

Yes, It should be. Maybe we should expose a parse method or accept a file path to format?