This is an independent contribution. I am not affiliated with the project maintainers.

Summary

Fix npm start failing on Windows due to Unix-only environment variable syntax in the start:website script. The inline NEXT_PUBLIC_LOCAL_QUILL=true syntax is not recognized by Windows Command Prompt or PowerShell.

Root Cause

In package.json, the start:website script uses Unix-style inline environment variable assignment:

NEXT_PUBLIC_LOCAL_QUILL=true npm start -w website

Windows shells (cmd.exe, PowerShell) do not support VAR=value command syntax, causing error: 'NEXT_PUBLIC_LOCAL_QUILL' is not recognized as an internal or external command.

Fix

Replaced the inline environment variable with cross-env to ensure cross-platform compatibility:

cross-env NEXT_PUBLIC_LOCAL_QUILL=true npm start -w website

Added cross-env as a devDependency (^7.0.3).

Testing

• The change only affects the npm script declaration, not production code
• cross-env has 7M+ weekly downloads and is the standard solution for cross-platform environment variables in npm scripts
• Existing Unix/macOS behavior is preserved

Closes #3916