Our webapp's frontend
Find a file
2025-05-15 15:19:46 -06:00
.vscode added vscode settings to make tabs smaller by default 2024-11-13 10:59:51 -06:00
public added manifest for staging, title actually gets set based on whiteLabel name now 2025-05-14 13:50:01 -06:00
src changing the use effect to make the call to the dispatch to change as to view as the user but is recording who they were viewing as, if they close without selecting an abject it will restore the previous team to the dispatch 2025-05-15 15:19:46 -06:00
.env added white label client ids 2025-05-12 12:03:20 -06:00
.gitignore folderized app files 2024-10-21 15:21:22 -06:00
.gitlab-ci.yml moving the variable to deploy 2025-05-07 12:54:44 -06:00
docker-compose.dev.yml added dns 2024-10-30 14:21:52 -06:00
docker-compose.prod.yml added docker-compose for production 2025-04-22 11:22:02 -06:00
docker-compose.staging.yml added staging yml file 2025-04-17 15:46:06 -06:00
Dockerfile added Dockerfile 2024-10-09 14:37:39 -06:00
eslint.config.js switched to vite instead of create-react-app to stayed updated in packages 2024-10-21 14:32:25 -06:00
index.html replacing title by id based on whiteLabel name 2025-05-14 12:41:31 -06:00
nginx.conf added nginx.conf 2024-10-09 14:42:22 -06:00
package-lock.json took out the babel core 2025-05-08 13:04:12 -06:00
package.json running staging locally now returns the staging whitelabel 2025-05-14 12:28:35 -06:00
README.md switched to vite instead of create-react-app to stayed updated in packages 2024-10-21 14:32:25 -06:00
tsconfig.app.json changed imports to remove legacy 2025-05-08 11:24:21 -06:00
tsconfig.json bins page now has the add bin button 2025-03-10 12:51:40 -06:00
tsconfig.node.json added ts config so that it could compile using absolute paths without error 2024-11-14 15:27:54 -06:00
vite.config.ts updating the target in the config to fix the transpile error for mapbox 2025-05-08 13:18:49 -06:00

React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

  • Configure the top-level parserOptions property like this:
export default tseslint.config({
  languageOptions: {
    // other options...
    parserOptions: {
      project: ['./tsconfig.node.json', './tsconfig.app.json'],
      tsconfigRootDir: import.meta.dirname,
    },
  },
})
  • Replace tseslint.configs.recommended to tseslint.configs.recommendedTypeChecked or tseslint.configs.strictTypeChecked
  • Optionally add ...tseslint.configs.stylisticTypeChecked
  • Install eslint-plugin-react and update the config:
// eslint.config.js
import react from 'eslint-plugin-react'

export default tseslint.config({
  // Set the react version
  settings: { react: { version: '18.3' } },
  plugins: {
    // Add the react plugin
    react,
  },
  rules: {
    // other rules...
    // Enable its recommended rules
    ...react.configs.recommended.rules,
    ...react.configs['jsx-runtime'].rules,
  },
})