You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the project directory you can run the following npm scripts (current scripts are taken from `package.json`):
211
211
212
-
### `npm start`
212
+
### `npm run dev` or `npm start`
213
213
214
-
Runs the app in the development mode.\
215
-
Open [http://localhost:3000](http://localhost:3000) to view it in the browser.
214
+
Starts the development server using Vite.
215
+
Open http://localhost:5173 in your browser (Vite's default port) to view the app.
216
+
The page reloads on changes and hot module replacement (HMR) is enabled.
216
217
217
-
The page will reload if you make edits.\
218
-
You will also see any lint errors in the console.
219
-
220
-
### `npm test`
218
+
### `npm run build`
221
219
222
-
Launches the test runner in the interactive watch mode.\
223
-
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.
220
+
Creates a production build using Vite and outputs optimized files to the `dist` folder.
224
221
225
-
### `npm test -- --coverage --watchAll`
222
+
### `npm run preview`
226
223
227
-
Returns the complete test coverage rate in the form of a table for all files.
224
+
Locally previews the production build (serves the `dist` output).
228
225
226
+
### `npm test`
229
227
230
-
### `npm run build`
228
+
Runs the Jest test suite (configured to use `ts-jest` for TypeScript). This is the project's primary test command and runs tests in a single process.
231
229
232
-
Builds the app for production to the `build` folder.\
233
-
It correctly bundles React in production mode and optimizes the build for the best performance.
230
+
### `npm run test:vitest`
234
231
235
-
The build is minified and the filenames include the hashes.\
236
-
Your app is ready to be deployed!
232
+
An alias to run Vitest (optional). The project currently uses Jest by default but a Vitest configuration remains available as an alternative.
237
233
238
-
See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.
234
+
### `npm run electron-pack`
239
235
240
-
### `npm run eject`
236
+
Builds an unpacked Electron application (developer-friendly output). This uses `electron-builder` with the `--dir` option.
241
237
242
-
**Note: this is a one-way operation. Once you `eject`, you can’t go back!**
238
+
### `npm run electron-dist`
243
239
244
-
If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.
240
+
Creates distributable packages for desktop platforms (platform-specific targets like `dmg`, `nsis`, etc.) via `electron-builder`.
245
241
246
-
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
242
+
Notes
243
+
- Dev server: Vite serves on port 5173 by default. If you have a different port configured or a proxy, adjust accordingly.
244
+
- Tests: run `npm test` for Jest. If you prefer Vitest, use the `test:vitest` script, but some tests rely on Jest semantics (e.g. jest.mock hoisting).
245
+
- If you encounter engine or install warnings (EBADENGINE), consider using a stable Node LTS (18.x or 20.x) via nvm.
247
246
248
-
You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
249
247
250
248
251
249
## Used NPM Modules
252
250
According to the command npm list
253
251
You can see the deeper NPM modules used and which of these are used in the licenses.json.
0 commit comments