vite build error: "type" is not exported by "__vite-browser-external"

[microsoft]

vite build error: "type" is not exported by "__vite-browser-external"

[lon-tierney]

Re-opening as @neaorin encountered this issue on new deploy. 'make build' resolved the issue as shown above. Please look in to this @asbanger

[justin-napolitano]

Update:

I think this issue is caused by node running out of memory during the build process in my github code space environment.
Exit Code 134 relates to a SIGTERM. Stopping the environment and starting fresh seems to clear the buffer enabling me to run the build. See current system settings below.

I will try increasing the amount of ram in the virtual machine to attempt a fix. OP might want to try the same.

Original:
I am still experiencing the same issue in a codespace environment on subsequent build attempts.

[dayland]

Resolved in 0.3 Gamma release. Please update to the Gamma release.

[dayland]

@fitchtravis , I was unable to reproduce this scenario... I did the following:

• Created a new GitHub CodeSpace from main branch (latest)
• Setup local.env
• run make build (this is the first command inside make deploy)

As you can see those warnings are present but did not block the npm build from succeeding.

I am on the same commit as you shared above:

commit b5dc8b368758b479b4f94b061b43c4b8ac94cb00 (HEAD -> main, origin/main, origin/HEAD)
Merge: ca99857 797ff84
Author: dayland <[email protected]>
Date:   Fri Jun 23 08:11:16 2023 +0000

    Merge pull request #101 from microsoft/dayland/5707-missing-search-indexer-property
    
    add "allowSkillsetToReadFileData" property to search indexer

Did you have issue #113 to start? If not I suggest running that command and then try make deploy again.

[fitchtravis]

@dayland, thanks for this .. Doing a make build first, got me past that point.

I'm now getting stuck on the deployment stage. Before I raise another issue. Do this demo only work in specific Azure regions?

[dayland]

Azure OpenAI is only supported in a few regions. (West Europe, France Central, UK South, East US, South Central US). The remaining Azure Services are more broadly supported. If you want to deploy in a specific region where Azure OpenAI isn't available, you simply deploy an instance of Azure OpenAI manually and then use the parameters in local.env to point to that instance of Azure OpenAI while the other services will be deployed in the region you provide in the LOCATION parameter.

For information on regional availabilty of Azure Services please see https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/

[fitchtravis]

Closing now.

[bprerad]

<update>
restarted everything and make deploy went through.

<original message>
Getting the same error. Tried make build first, as suggested and the result is the same.

Environment set: local.
Loading environment variables for local.
Loading environment variables for Language: en-US.

🎯 Target Resource Group: infoasst-bop-ws


up to date, audited 174 packages in 934ms

12 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

> [email protected] build
> tsc && vite build

vite v4.4.7 building for production...
node_modules/@azure/storage-blob/dist-esm/storage-blob/src/TelemetryPolicyFactory.js (32:70) "type" is not exported by "__vite-browser-external", imported by "node_modules/@azure/storage-blob/dist-esm/storage-blob/src/TelemetryPolicyFactory.js".
node_modules/@azure/storage-blob/dist-esm/storage-blob/src/TelemetryPolicyFactory.js (32:83) "release" is not exported by "__vite-browser-external", imported by "node_modules/@azure/storage-blob/dist-esm/storage-blob/src/TelemetryPolicyFactory.js".
✓ 1786 modules transformed.
Terminated
make: *** [Makefile:15: build] Error 143

---

commit b589e6e1130209d8d3e6a21b2c1c26e1d178a268 (HEAD -> main, origin/main, origin/HEAD)
Merge: 8b60821 6c94751
Author: dayland <[email protected]>
Date:   Thu Jul 20 21:19:08 2023 +0000

    Merge pull request #139 from microsoft/aparmar/5875-ThouroughResponseBug
    
    Hot fix for Response length.

[lon-tierney]

@justin-napolitano did the restart resolve your issue, or is this persisting?

[youngr6m]

I had the same issue using make deploy initially, but I've been using the codespace within VS Code on my local desktop. Switching to the web hosted codespace, make build worked as expected (no 143 error).

[asbanger]

When you are deploying using codespace, we strongly recommend to you vscode dekstop