Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.

[mohammadkhanTEKenable]

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

azd up command used after deleting all resources and init fresh env downloading latest code release

### Any log messages given by the failure
>
> [email protected] build
> tsc && vite build

vite v4.1.1 building for production...
✓ 1250 modules transformed.
../backend/static/index.html                    0.47 kB
../backend/static/assets/github-fab00c2d.svg    0.96 kB
../backend/static/assets/index-2fb53ec2.css     7.44 kB │ gzip:   2.19 kB
../backend/static/assets/index-7abdfda7.js    625.74 kB │ gzip: 204.86 kB │ map: 5,054.95 kB

(!) Some chunks are larger than 500 kBs after minification. Consider:
- Using dynamic import() to code-split the application
- Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks
- Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.

Deploying services (azd deploy)

  (✓) Done: Deploying service backend

ERROR: deploying service: deploying service backend package: read /tmp/azd2956009831/backend_env/lib64: is a directory

Expected/desired behavior

Front End should build successfully

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?) Windows 10 running VS Code and Remote Container

Versions

Mention any other details that might be useful

Code was building earlier in the week i made some local changes and wanted to reset back to sample from Git Repo, since than it has stopped building. no changes made to code.

---

Thanks! We'll be in touch soon.