Allow to disable validation of "Default condition should be last one"

[hyf0]

Related code:

oxc-resolver/src/lib.rs

Lines 1464 to 1468 in e04ca0f

	let is_default = matches!(key, ImportExportKey::CustomCondition(condition) if condition == "default");
	if i < target.len() - 1 && is_default {
	return Err(ResolveError::InvalidPackageConfigDefault(
	package_url.join("package.json"),
	));

The current behavior of oxc-resolver is correct based on the spec, but not flexable.

"default" - the generic fallback that always matches. Can be a CommonJS or ES module file. This condition should always come last. link

Though spec said the "default" should always come last, but nodejs actually doesn't do strong validation on it. If "default` shows , it will be matched once detecting it.

Context:

• Esbuild follows the actual behavior of nodejs rather the spec.
• • Test: https://github.com/evanw/esbuild/blob/83e8c7f0b86e7b627990339870c8cc68c154c77b/internal/bundler_tests/bundler_packagejson_test.go#L1566-L1597
• • Test Output: https://github.com/evanw/esbuild/blob/83e8c7f0b86e7b627990339870c8cc68c154c77b/internal/bundler_tests/snapshots/snapshots_packagejson.txt#L575-L578

Related:

• Ignore Default condition should be last one webpack/enhanced-resolve#421
• evanw/esbuild@8b16b2d

[hyf0]

I personally intend to follow the spec. But this case is tricky, nodejs itself doesn't follow the spec due to reasons I don't know. For maximum compatibility, rolldown needs to follow the esbuild's behavior.

[Boshen]

The spec never mentioned the logic where "default" must be last or it should throw an error.

Hence enhanced-resolve is the one not conforming to the spec.

---

statement for being the last: https://nodejs.org/docs/v20.13.1/api/packages.html#conditional-exports

should, not must.