fix: fix windows build command basign on --mode [mode] flag

[sohaieb]

• This PR fixes a small issue introduced in docs: mention native Opik tracing integration #5758 , which blocks pnpm build and pnpm build-force commands on Windows systems (due to injecting NODE_ENV variable directly in the command line.
• Replaced by Vite Modes instead.
• Removed cross-env package from the repo

[gemini-code-assist]

Summary of Changes

Hello @sohaieb, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a critical build failure on Windows environments by refactoring how environment variables are passed to Vite commands. Instead of directly injecting NODE_ENV, the project now leverages Vite's native --mode flag, ensuring consistent and reliable build and development processes across different operating systems. This change enhances the robustness of the build system and adheres to recommended Vite practices.

Highlights

• Windows Build Fix: Resolved an issue preventing pnpm build and pnpm build-force commands from working on Windows systems, which was caused by direct NODE_ENV injection.
• Vite Mode Adoption: Migrated environment variable handling from direct NODE_ENV setting to using Vite's --mode flag for build and dev scripts, improving cross-platform compatibility.
• Vite Config Update: Modified vite.config.ts to properly consume the mode parameter from defineConfig, aligning with the updated script commands.

Changelog

• packages/agentflow/package.json
  • Updated build script to use vite build --mode production instead of NODE_ENV=production vite build.
  • Updated dev script to use vite --mode development instead of NODE_ENV=development vite.
  • Updated dev:example script to use vite --config examples/vite.config.ts --mode development instead of NODE_ENV=development vite --config examples/vite.config.ts.
• packages/agentflow/vite.config.ts
  • Refactored defineConfig to accept a mode parameter.
  • Changed isDev variable assignment to derive its value from the mode parameter instead of process.env.NODE_ENV.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly resolves a build issue on Windows by adopting Vite's --mode flag instead of setting NODE_ENV directly in npm scripts. This change ensures cross-platform compatibility for the build and development commands. The vite.config.ts is also properly updated to use a function configuration, accessing the mode passed by Vite. The implementation is clean and effective.

[jocelynlin-wd]

based on the doc you shared https://vite.dev/guide/env-and-mode#modes, we don't even need to pass in mode since build script will by default be production

[sohaieb]

Hi
You are completely right @jocelynlin-wd , thank you for the catch !

Basing on the following announced remark in Vite - Env and Mode Doc:

By default, the dev server (dev command) runs in development mode and the build command runs in production mode.

I will keep the code above as we still need it to specify the sourceMap config according to the environment/mode, but I will adjust the package.json scripts instead.

[sohaieb]

Hi again @jocelynlin-wd ,
I made the updates according to our discussion,

In the meanwhile, another topic: I created another PR to add LMStudio support too and it fixes some UI issues.

I would really appreciate a lot if you review both PRs 😃
Thank you so much 🙏

[ginna-baker]

Great idea. Thanks for bringing this up and putting in a better environment check than what I had originally 🙏

[ginna-baker]

Looking great

[jocelynlin-wd]

thanks for the fix

[sohaieb]

Great idea. Thanks for bringing this up and putting in a better environment check than what I had originally 🙏

thank you very much !

thanks for the fix

It's really a pleasure to collaborate!