fix(build): use named Parcel target to avoid exports field conflict

[cchanxzy]

Fix: Parcel build failure caused by exports field in package.json

The gh-predeploy step in the release workflow fails with:

@parcel/core: Failed to resolve 'react/jsx-runtime' from './src/examples/index.tsx'
@parcel/resolver-default: file name contained an unexpected NUL byte

Parcel v2 auto-detects certain package.json fields (main, module, types, exports) as build targets. The exports field uses a nested map structure for conditional exports (ESM/CJS), which Parcel cannot interpret as a valid build target distPath. This causes module resolution to break with a NUL byte error when resolving react/jsx-runtime.

The existing targets config already disables main, module, and types with false, but exports cannot be disabled the same way because Parcel validates its value before checking the opt-out.

Solution

Defined a named Parcel target app in the targets config with the distDir and publicUrl settings that were previously passed as CLI flags. Updated both the gh-predeploy and start scripts to use --target app, which tells Parcel to build only the explicitly named target and skip auto-detection of exports.

Changes in package.json

1. Added "app" target to targets:

   "app": {
     "distDir": "demo/examples",
     "publicUrl": "./"
   }

2. Updated gh-predeploy script:

   - "gh-predeploy": "parcel build src/examples/index.html --dist-dir demo/examples --public-url ./",
   + "gh-predeploy": "parcel build src/examples/index.html --target app",

3. Updated start script:

   - "start": "parcel src/examples/index.html --open",
   + "start": "parcel src/examples/index.html --target app --open",

[github-actions]

🎉 This PR is included in version 4.0.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀