studio/meet
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
6d16bb3403f8aa6a6be106acf49ccb3f7a4645eb
meet/src/frontend/package.json

43 lines
1.2 KiB
JSON
Raw Normal View History

✨(frontend) create Vite app using npm Run the command 'npm create vite@latest' to bootstrap a new frontend project. Please note, other elements of the project still use yarn, to avoid confusion let's use npm instead. Vite was chosen over Next.Js for its simplicity; Next.Js could be kind of a black box where a lot of magics happen.
2024-06-24 15:42:01 +02:00
{
🚚(frontend) rename Impress to Meet I have updated all references of "Impress" to "Meet".
2024-07-01 14:53:23 +02:00
"name": "meet",
✨(frontend) create Vite app using npm Run the command 'npm create vite@latest' to bootstrap a new frontend project. Please note, other elements of the project still use yarn, to avoid confusion let's use npm instead. Vite was chosen over Next.Js for its simplicity; Next.Js could be kind of a black box where a lot of magics happen.
2024-06-24 15:42:01 +02:00
"private": true,
"version": "0.0.0",
"type": "module",
"scripts": {
♻️(frontend) starting a bit more structured frontend app the idea is to use react aria, panda-css, react query and wouter as a base, in addition to livekit react components this is still mostly wip but it's usable: - homepage shows a login link to create a room - before joining a room you are asked to configure your audio/video/user name - note that if you directly go to a a conference url it creates it even if you are not logged in… very secured!
2024-07-02 20:05:46 +02:00
"dev": "panda codegen && vite",
"build": "panda codegen && tsc -b && vite build",
✨(frontend) create Vite app using npm Run the command 'npm create vite@latest' to bootstrap a new frontend project. Please note, other elements of the project still use yarn, to avoid confusion let's use npm instead. Vite was chosen over Next.Js for its simplicity; Next.Js could be kind of a black box where a lot of magics happen.
2024-06-24 15:42:01 +02:00
"lint": "eslint . --ext ts,tsx --report-unused-disable-directives --max-warnings 0",
💚(frontend) do not run panda codegen on npm install/npm ci panda needs to generate types to work. We used to generate those after deps install but it's not that necessary, since we generate them before running the dev env, and before building the prod build. This fixes the `npm ci` error in the frontend docker build
2024-07-03 11:10:16 +02:00
"preview": "vite preview"
✨(frontend) create Vite app using npm Run the command 'npm create vite@latest' to bootstrap a new frontend project. Please note, other elements of the project still use yarn, to avoid confusion let's use npm instead. Vite was chosen over Next.Js for its simplicity; Next.Js could be kind of a black box where a lot of magics happen.
2024-06-24 15:42:01 +02:00
},
"dependencies": {
♻️(frontend) starting a bit more structured frontend app the idea is to use react aria, panda-css, react query and wouter as a base, in addition to livekit react components this is still mostly wip but it's usable: - homepage shows a login link to create a room - before joining a room you are asked to configure your audio/video/user name - note that if you directly go to a a conference url it creates it even if you are not logged in… very secured!
2024-07-02 20:05:46 +02:00
"@livekit/components-react": "2.3.3",
"@livekit/components-styles": "1.0.12",
"@pandacss/preset-panda": "0.41.0",
"@tanstack/react-query": "5.49.2",
"livekit-client": "2.3.1",
✨(frontend) create Vite app using npm Run the command 'npm create vite@latest' to bootstrap a new frontend project. Please note, other elements of the project still use yarn, to avoid confusion let's use npm instead. Vite was chosen over Next.Js for its simplicity; Next.Js could be kind of a black box where a lot of magics happen.
2024-06-24 15:42:01 +02:00
"react": "18.2.0",
♻️(frontend) starting a bit more structured frontend app the idea is to use react aria, panda-css, react query and wouter as a base, in addition to livekit react components this is still mostly wip but it's usable: - homepage shows a login link to create a room - before joining a room you are asked to configure your audio/video/user name - note that if you directly go to a a conference url it creates it even if you are not logged in… very secured!
2024-07-02 20:05:46 +02:00
"react-aria-components": "1.2.1",
"react-dom": "18.2.0",
📌(frontend) pin wouter dep that was forgotten following this project's choice of pinning everything, missed this one
2024-07-03 11:16:00 +02:00
"wouter": "3.3.0"
✨(frontend) create Vite app using npm Run the command 'npm create vite@latest' to bootstrap a new frontend project. Please note, other elements of the project still use yarn, to avoid confusion let's use npm instead. Vite was chosen over Next.Js for its simplicity; Next.Js could be kind of a black box where a lot of magics happen.
2024-06-24 15:42:01 +02:00
},
"devDependencies": {
♻️(frontend) starting a bit more structured frontend app the idea is to use react aria, panda-css, react query and wouter as a base, in addition to livekit react components this is still mostly wip but it's usable: - homepage shows a login link to create a room - before joining a room you are asked to configure your audio/video/user name - note that if you directly go to a a conference url it creates it even if you are not logged in… very secured!
2024-07-02 20:05:46 +02:00
"@pandacss/dev": "0.41.0",
"@tanstack/eslint-plugin-query": "5.49.1",
"@tanstack/react-query-devtools": "5.49.2",
🔧(frontend) pass host and port through environment vars Configured the frontend to use environment variables (prefixed with "VITE_") for frontend port and host configuration, which will be overridden in the Helm chart values to ensure correct values are used in different environments. Helm requires the frontend port to be 8081 and use the public host, not the default "localhost" value.
2024-07-02 17:07:17 +02:00
"@types/node": "20.14.9",
✨(frontend) create Vite app using npm Run the command 'npm create vite@latest' to bootstrap a new frontend project. Please note, other elements of the project still use yarn, to avoid confusion let's use npm instead. Vite was chosen over Next.Js for its simplicity; Next.Js could be kind of a black box where a lot of magics happen.
2024-06-24 15:42:01 +02:00
"@types/react": "18.3.3",
"@types/react-dom": "18.3.0",
"@typescript-eslint/eslint-plugin": "7.13.1",
"@typescript-eslint/parser": "7.13.1",
"@vitejs/plugin-react": "4.3.1",
"eslint": "8.57.0",
♻️(frontend) starting a bit more structured frontend app the idea is to use react aria, panda-css, react query and wouter as a base, in addition to livekit react components this is still mostly wip but it's usable: - homepage shows a login link to create a room - before joining a room you are asked to configure your audio/video/user name - note that if you directly go to a a conference url it creates it even if you are not logged in… very secured!
2024-07-02 20:05:46 +02:00
"eslint-plugin-jsx-a11y": "6.9.0",
✨(frontend) create Vite app using npm Run the command 'npm create vite@latest' to bootstrap a new frontend project. Please note, other elements of the project still use yarn, to avoid confusion let's use npm instead. Vite was chosen over Next.Js for its simplicity; Next.Js could be kind of a black box where a lot of magics happen.
2024-06-24 15:42:01 +02:00
"eslint-plugin-react-hooks": "4.6.2",
"eslint-plugin-react-refresh": "0.4.7",
♻️(frontend) starting a bit more structured frontend app the idea is to use react aria, panda-css, react query and wouter as a base, in addition to livekit react components this is still mostly wip but it's usable: - homepage shows a login link to create a room - before joining a room you are asked to configure your audio/video/user name - note that if you directly go to a a conference url it creates it even if you are not logged in… very secured!
2024-07-02 20:05:46 +02:00
"postcss": "8.4.39",
✨(frontend) create Vite app using npm Run the command 'npm create vite@latest' to bootstrap a new frontend project. Please note, other elements of the project still use yarn, to avoid confusion let's use npm instead. Vite was chosen over Next.Js for its simplicity; Next.Js could be kind of a black box where a lot of magics happen.
2024-06-24 15:42:01 +02:00
"typescript": "5.5.2",
♻️(frontend) starting a bit more structured frontend app the idea is to use react aria, panda-css, react query and wouter as a base, in addition to livekit react components this is still mostly wip but it's usable: - homepage shows a login link to create a room - before joining a room you are asked to configure your audio/video/user name - note that if you directly go to a a conference url it creates it even if you are not logged in… very secured!
2024-07-02 20:05:46 +02:00
"vite": "5.3.1",
"vite-tsconfig-paths": "4.3.2"
✨(frontend) create Vite app using npm Run the command 'npm create vite@latest' to bootstrap a new frontend project. Please note, other elements of the project still use yarn, to avoid confusion let's use npm instead. Vite was chosen over Next.Js for its simplicity; Next.Js could be kind of a black box where a lot of magics happen.
2024-06-24 15:42:01 +02:00
}
}
Reference in New Issue Copy Permalink