Build command from Netlify app wrong destination folder

Hi guys,
I’m building an nodejs web application on netlify but i got an error after build successfully complete.
When i check build log, i think the problem maybe around here - that the builded file in wrong location

...
11:07:26 AM: dist/assets/zh-CN.22892adf.js            37.20 KiB / gzip: 12.28 KiB
11:07:26 AM: dist/assets/bg-BG.304f5766.js            94.68 KiB / gzip: 16.28 KiB
11:07:26 AM: dist/assets/zh-TW.291a7185.js            38.01 KiB / gzip: 12.43 KiB
11:07:26 AM: dist/assets/Security.a3731fc5.js         35.00 KiB / gzip: 12.57 KiB
11:07:26 AM: dist/assets/index.200fa922.css           282.95 KiB / gzip: 41.40 KiB
11:07:26 AM: dist/assets/PingChart.df17de47.js        227.42 KiB / gzip: 79.67 KiB
11:07:26 AM: dist/assets/index.4979bb56.js            1060.57 KiB / gzip: 319.32 KiB
11:07:26 AM: 
11:07:26 AM: (!) Some chunks are larger than 500 KiB after minification. Consider:
11:07:26 AM: - Using dynamic import() to code-split the application
11:07:26 AM: - Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/guide/en/#outputmanualchunks
11:07:26 AM: - Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
11:07:27 AM: ✨ [vite-plugin-compression]:algorithm=gzip - compressed file successfully:
11:07:27 AM: dist//opt/build/repo/assets/Notifications.e10a476d.js.gz          3.61kb / gzip: 1.50kb
11:07:27 AM: dist//opt/build/repo/assets/Notifications-legacy.7f3540de.js.gz   4.44kb / gzip: 1.74kb
11:07:27 AM: dist//opt/build/repo/assets/PingChart.6d029c3b.css.gz             1.21kb / gzip: 0.42kb
11:07:27 AM: dist//opt/build/repo/assets/Settings-legacy.c20832d2.js.gz        5.01kb / gzip: 1.86kb
11:07:27 AM: dist//opt/build/repo/assets/Settings.3388b3f6.css.gz              1.79kb / gzip: 0.52kb
11:07:27 AM: dist//opt/build/repo/assets/Settings.6fb65762.js.gz               2.87kb / gzip: 1.27kb
...

Please help to clarify this point.

  • Site name: knock-me-up.netlify.app
  • Full build log: Netlify App
  • Build settings:

Base directory: Not set
Build command: npm run build
Publish directory: dist
Deploy log visibility: Logs are public
Build status: Active

Hi, @hongha1412. It appears an incorrect publish directory location was being used. It looks like you we able to resolve the issue be changing the publish directory.

If there are other questions or concerns, please let us know.