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

52 lines
1.6 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,
🔖(minor) bump release to 0.1.3
2024-08-05 22:38:20 +02:00
"version": "0.1.3",
✨(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
"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) init i18next - dynamically load locale files for smaller footprint - have a namespace for each feature. At first I'd figured I'd put each namespace in its correct feature folder but it's kinda cumbersome to manage if we want to link that to i18n management services like crowdin…
2024-07-18 13:59:50 +02:00
"preview": "vite preview",
🌐(crowdin) make crowdin work with frontend translations - upload local translation files on push - make crowdin create a pull request when new translations are made through the crowdin website (webhook configured on crowdin-end)
2024-07-19 12:27:51 +02:00
"i18n:extract": "npx i18next -c i18next-parser.config.json"
✨(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",
💄(home) have a cleaner homepage layout - try a new layout for the homepage, making it easier to join a meeting - add a new Dialog component to easily build dialogs
2024-07-22 00:44:02 +02:00
"@remixicon/react": "4.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
"@tanstack/react-query": "5.49.2",
🌐(frontend) init i18next - dynamically load locale files for smaller footprint - have a namespace for each feature. At first I'd figured I'd put each namespace in its correct feature folder but it's kinda cumbersome to manage if we want to link that to i18n management services like crowdin…
2024-07-18 13:59:50 +02:00
"hoofd": "1.7.1",
"i18next": "23.12.1",
"i18next-browser-languagedetector": "8.0.0",
"i18next-parser": "9.0.0",
"i18next-resources-to-backend": "1.2.1",
♻️(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-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) init i18next - dynamically load locale files for smaller footprint - have a namespace for each feature. At first I'd figured I'd put each namespace in its correct feature folder but it's kinda cumbersome to manage if we want to link that to i18n management services like crowdin…
2024-07-18 13:59:50 +02:00
"react-i18next": "14.1.3",
♻️(frontend) rework how we handle screens and layout code Previously each route rendered its whole layout from a to z. Now each route updates a single common wrapper when the layout changes between pages. Also the Loading, Error, UserFetched, QueryAware code is more explicit and understandable. This introduces valtio as dependency, allowing us to deal with global state easily in a svelte/vue way (reactive mutable state). This limits the boilerplaty-ness of immutable state lib approaches, while keeping rendering optimization better than homemade react contexts.
2024-07-29 18:32:56 +02:00
"valtio": "1.13.2",
📌(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