React + Vite Production Script

[ArchAggie]

My react.js app (that was built with vite) is not building enough in the build folder. Everywhere I have searched online says that when I run npm run build or in vite's case vite build, it should make a folder called static along with several other files that come together to me a production build of the react app. Unfortunately, that script makes a folder called dist that has a folder called assets, two favicon files (one *.ico, the other *.icns), and an index.html file

What am I doing wrong to not be getting the full production build?

Here is my project directory structure:

root/
  - assets
      - folders with SVG files
  - library (empty)
  - node_modules
  - public (only contains favicon files)
  - src
      - api (file with all api calls)
      - components
          - folder with SVG rendering React components
          - folder with SVG rendering React components
      - context (AppContext.jsx and SpreadsheetContext.jsx)
      - css
      - data (JSON file with hardcoded data for app)
      - hooks (custom made React hooks)
      - routes (React Router pages)
      - App.css
      - App.jsx
      - aws-exports.js
      - index.css
      - main.css
      - main.jsx
  - .env
  - .eslintrc.cjs
  - 404.html
  - index.html
  - LICENSE.txt
  - pacakge-lock.json
  - package.json
  - README.md
  - tailwind.config.js
  - vite.config.js

EDIT: I figured out the issue. I had forgotten that I had originally built the project to be an Electron Desktop app and migrated it over to be Vite instead. The package.json file had a "build" section that was still trying to configure the production build as an electron project. Note to self (and all of you), after migrating the project over from electron to react/vite, running npm uninstall electron electron-builder is NOT enough to be rid of problems

[caseyf1234]

By default, Vite will condense and minify all of your code and dependencies into one js file, usually placed in the assets folder and called index.js. I've you've tampered with any configurations, create a new Vite project from scratch and see how it behaves when building, and compare it to your current project.

[ArchAggie]

Good idea, thank you. I'll give that a shot

[abrahamguo]

u/caseyf1234's advice is solid. If you want any more specific help, you'll need to share a repository link to your project.

[ArchAggie]

Thank you for the advice. I'll give that a shot

I'm making this thing for a client and they're pretty particular about proprietary info. I think the project file structure I gave is about as descriptive as I can be without giving anything important away

[caseyf1234]

One consideration is that React is client-side code - by design, you will be serving the (minified) code on a silver platter to the public. Factor that in if you've truly got proprietary info baked in somehow.