- Create scripts/fix-build-paths.js to convert absolute paths to relative
- Update build script to run fix-build-paths.js after plasmo build
- Add build:raw script for raw plasmo build without fix
Problem: Plasmo generates HTML with absolute paths (href="/file.css")
which causes ERR_FILE_NOT_FOUND in Chrome extensions.
Solution: Post-build script replaces /path with ./path
- Fix escaped quotes in ThreadGeneratorPanel.tsx (root cause of build error)
- Update tsconfig.json to use jsx: react-jsx instead of preserve
- Upgrade Plasmo to v0.90.5 (latest version)
- Build now succeeds in 4.7s
Root Cause: ThreadGeneratorPanel.tsx had escaped quotes (\") instead of
normal quotes ("), causing SWC parser to fail with 'Unexpected token div' error.
This was a file encoding issue, not a Plasmo version issue.
Fixes #build-error
- Remove 'engines' field from package.json (workaround for Plasmo issue #1040)
- Fix operator precedence in ChatInterface condition
- Resolves 'Failed to resolve popup.tsx' error
Note: Still encountering 'Unexpected token div' JSX error during build.
This appears to be a separate Plasmo bundler issue unrelated to our code changes.
- Add sharp@0.33.5 override to support Node.js 22
- Add sharp as direct dependency
- Upgrade plasmo to 0.90.5
- Add Node.js version constraint (>=18.0.0 <23.0.0)
- Add pnpm version constraint (>=8.0.0)
This fixes the 'Cannot find module sharp-win32-x64.node' error
reported in issue #413 when building on Node.js v22.0.0
