Fix frontend vite config

[toviszsolt]

Why

Use { shell: true } for execFile because yarn is often a shell script or a batch file (especially on Windows), and execFile requires a direct executable path unless a shell is provided to interpret the command.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Code refactoring
• API changes
• Performance improvement
• Test addition or update

AI Usage

• AI was used to write this
• AI was used to review this

[Copilot]

Pull request overview

This PR updates the frontend Vite dev-server startup hook that runs locale-related Yarn scripts, aiming to improve cross-platform (especially Windows) behavior when invoking yarn via Node’s execFile.

Changes:

• Run yarn locale-compile and yarn locale-sort using execFile with shell execution enabled.
• Normalize plugin name quoting to match the file’s double-quote style.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[toviszsolt]

The PR resolves the issue of running execFile Yarn scripts on the Windows platform for the Vite dev server.

[nginxproxymanagerci]

Docker Image for build 2 is available on DockerHub:

nginxproxymanager/nginx-proxy-manager-dev:pr-5680

Note

Ensure you backup your NPM instance before testing this image! Especially if there are database changes.
This is a different docker image namespace than the official image.

Warning

Changes and additions to DNS Providers require verification by at least 2 members of the community!