Updated add-api.md to suit React Vite users as well

[rvrama]

Made changes in 2 places for React Vite users to use dist folder instead of build. While building and while running with swa command locally. PLEASE IGNORE MY PREVIOUS COMMIT as this has complete change.

[prmerger-automator]

@rvrama : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit b1e877a:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
articles/static-web-apps/add-api.md	⚠️Warning		Details

articles/static-web-apps/add-api.md

• Line 260, Column 1: [Warning: invalid-tab-group - See documentation] Tab group with different tab id set.
• Line 307, Column 5: [Warning: invalid-tab-group - See documentation] Tab group with different tab id set.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[Copilot]

Pull Request Overview

Updates the documentation for adding APIs to Static Web Apps to include specific instructions for React Vite users, who use the dist folder instead of the build folder for their build output.

• Adds a new tab section for React (Vite) with proper build command and folder references
• Updates both the build instructions and local development commands to accommodate Vite's dist output folder

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The build command npm run dist is incorrect for React Vite projects. The standard Vite build command is npm run build, which outputs to the dist folder by default.

Suggested change

	npm run dist
	npm run build

[ttorble]

@v1212

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team