test: use ESM test files

[chenjiahan]

Summary

This PR updates the Playwright tests to run with standard ESM semantics instead of relying on a test/package.json CommonJS scope. The tests now use import.meta.dirname for fixture paths and createRequire(import.meta.url) only where they need to verify the CommonJS UMD output, so Rsbuild config files are loaded under the repository's normal module scope.

Related Links

#63

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 41daf544-201f-4e18-8529-da9a375f9132

📥 Commits

Reviewing files that changed from the base of the PR and between 19f3691 and 357134b.

📒 Files selected for processing (6)

• test/basic/index.test.ts
• test/environments/index.test.ts
• test/export-array/index.test.ts
• test/export/index.test.ts
• test/package.json
• test/split-chunks/index.test.ts

💤 Files with no reviewable changes (1)

• test/package.json

---

📝 Walkthrough

Walkthrough

test/package.json drops the "type": "commonjs" declaration, allowing the test package to be treated as ESM. All five test files (basic, environments, export-array, export, split-chunks) replace __dirname with import.meta.dirname for Rsbuild cwd, loadConfig, writeFileSync, and filesystem assertion paths. Where require() is needed to load built CommonJS output, each test now creates a local require function via createRequire(import.meta.url).

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: switching test files to ESM semantics.
Description check	✅ Passed	The description accurately describes the ESM test changes and why createRequire is still needed.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/use-esm-test-files

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 357134b28f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Preserve native ESM config coverage

With this package scope removed, the fixture rsbuild.config.ts files are now loaded under the root "type": "module", but they still import the built package via the relative directory specifier ../../dist (for example, test/basic/rsbuild.config.ts). Native Node ESM rejects relative directory imports, so loadConfig()'s default auto loader falls back to jiti instead of exercising the standard ESM semantics this change is meant to test; update the fixture imports to the explicit built entry (for example ../../dist/index.js) or force the native loader so regressions in native ESM loading are actually caught.

Useful? React with 👍 / 👎.