v1.3.2

Fixes

• Improved UI page entrypoint detection: Single-file JS/TS entrypoints (e.g., popup.ts) are now correctly treated as unlisted-script type, not UI pages. Only directory-based UI entrypoints (e.g., popup/main.tsx) are skipped for console forwarding injection.

• Custom entrypointsDir support: Now uses wxt.config.entrypointsDir instead of hardcoding /entrypoints/ path, supporting projects with custom entrypoint directory locations.

• Additional CSS extensions: Added support for sass, styl, and stylus file extensions when extracting entrypoint directory names.

• Windows path support: Normalized backslash handling for Windows-style paths.

Internal

• Renamed Playwright test files to .pw.ts to avoid conflicts with Bun test runner
• Added comprehensive unit tests for entrypoint detection logic (72 tests)

v1.0.0 - Initial Release

wxt-module-console-forward v1.0.0

🎉 Initial release of the WXT Console Forward module!

🚀 Features

• Console Log Forwarding: Forward console logs from web extension scripts to the WXT dev server
• Multi-context Support: Works with background scripts, content scripts, popup scripts, and more
• Development Debugging: Essential tool for debugging web extensions during development
• Easy Integration: Simple module configuration in your wxt.config.ts

📦 Installation

npm install wxt-module-console-forward

🛠️ Usage

Add to your wxt.config.ts:

import { defineConfig } from 'wxt'
import consoleForward from 'wxt-module-console-forward'

export default defineConfig({
  modules: [consoleForward]
})

📚 Documentation

See the README for complete usage instructions and configuration options.

🔗 Links

• 📦 NPM Package
• 📖 Documentation
• 🐛 Report Issues

---

Full Changelog: https://github.com/0xBigBoss/wxt-module-console-forward/commits/v1.0.0