Fail to run command npm start --workspace=webapp when using a different backend

[jianingwang123]

Describe the issue:
When using a different backend according to the README , run command npm start --workspace=webapp , the error is as follows:

Repro Steps:

1. Deploy this repository
2. Open the alternative backend repository your want to use, for example: https://github.com/Azure-Samples/azure-search-openai-demo
3. Set the frontend URL as an allowed origin with azd env set ALLOWED_ORIGIN http://localhost:5173
4. Follow the steps to deploy the Python backend.
5. Once the Python backend is fully deployed, get the backend URL with azd env get-values | grep BACKEND_URI
6. Set the backend URL in this repo, running azd env set BACKEND_URI <your_backend_url>
7. Run export BACKEND_URI=<your_backend_url>
8. Run npm start --workspace=webapp

Environment:

• Azd version: azd version 1.9.5 (commit cd2b7af9995d358aab33c782614f801ac1997dde)
• OS: Dev Containers ,Windows and Codespaces.

Expected behavior:
Run command npm start --workspace=webapp successfully.

@jongio and @sinedied for notification.

[sinedied]

Seems like the docs need to be updated.

Try npm run dev --workspace=webapp instead

[jianingwang123]

@sinedied After using the command npm run dev --workspace=webapp instead, the current issue no longer recurs, but when chatting on the frontend page, the following error occurs:

[sinedied]

For the second issue, the python backend has migrated to the latest AI Chat protocol using different endpoints, so it's currently not compatible. I'll create a separate issue for this.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this issue will be closed.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity.

[jianingwang123]

@sinedied This issue doesn't seem to be fixed, could you please reopen it?

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this issue will be closed.

[jianingwang123]

This issue seems to be unresolved, and this comment is to prevent the issue from being closed.

[sinedied]

@jianingwang123 The issue here is due to the divergence in protocol used in the Python sample, I created #216 to track this so I'll close this one to avoid having duplicate issues