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

10634 lines
384 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",
🔖(patch) bump release to 0.1.12 Release a fix while calling Docs backend API.
2024-12-18 22:33:42 +01:00
"version": "0.1.12",
✨(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
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
🚚(frontend) rename Impress to Meet I have updated all references of "Impress" to "Meet".
2024-07-01 14:53:23 +02:00
"name": "meet",
🔖(patch) bump release to 0.1.12 Release a fix while calling Docs backend API.
2024-12-18 22:33:42 +01:00
"version": "0.1.12",
✨(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": {
⬆️(dependencies) update js dependencies
2025-01-27 14:32:11 +00:00
"@livekit/components-react": "2.8.1",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@livekit/components-styles": "1.1.4",
⬆️(frontend) bump LiveKit-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-16 18:42:31 +01:00
"@livekit/track-processors": "0.3.3",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@pandacss/preset-panda": "0.51.1",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/toast": "3.0.0-beta.19",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@remixicon/react": "4.6.0",
⬆️(frontend) bump react-query-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:00:48 +01:00
"@tanstack/react-query": "5.64.2",
➕(frontend) add crisp-sdk-web dependency La Suite uses Crisp for Chat support. Added their react sdk.
2024-09-23 19:51:24 +02:00
"crisp-sdk-web": "1.0.25",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"hoofd": "1.7.3",
⬆️(dependencies) update js dependencies
2025-01-27 14:32:11 +00:00
"i18next": "24.2.2",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"i18next-browser-languagedetector": "8.0.2",
"i18next-parser": "9.1.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
"i18next-resources-to-backend": "1.2.1",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"livekit-client": "2.8.1",
⬆️(dependencies) update js dependencies
2025-01-27 14:32:11 +00:00
"posthog-js": "1.210.2",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"react": "18.3.1",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react-aria-components": "1.6.0",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"react-dom": "18.3.1",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react-i18next": "15.1.1",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"use-sound": "4.0.3",
⬆️(dependencies) update js dependencies
2025-01-27 14:32:11 +00:00
"valtio": "2.1.3",
"wouter": "3.4.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": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@pandacss/dev": "0.51.1",
⬆️(frontend) bump react-query-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:00:48 +01:00
"@tanstack/eslint-plugin-query": "5.64.2",
"@tanstack/react-query-devtools": "5.64.2",
⬆️(dependencies) update js dependencies
2025-01-27 14:32:11 +00:00
"@types/node": "22.10.10",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@types/react": "18.3.12",
"@types/react-dom": "18.3.1",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@typescript-eslint/eslint-plugin": "8.21.0",
"@typescript-eslint/parser": "8.21.0",
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@vitejs/plugin-react": "4.3.4",
✨(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": "8.57.0",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"eslint-config-prettier": "10.0.1",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"eslint-plugin-jsx-a11y": "6.10.2",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"eslint-plugin-react-hooks": "5.1.0",
"eslint-plugin-react-refresh": "0.4.18",
"postcss": "8.5.1",
"prettier": "3.4.2",
"typescript": "5.7.3",
⬆️(dependencies) update js dependencies
2025-01-27 14:32:11 +00:00
"vite": "6.0.11",
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"vite-tsconfig-paths": "5.1.4"
✨(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
}
},
"node_modules/@ampproject/remapping": {
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/@ampproject/remapping/-/remapping-2.3.0.tgz",
"integrity": "sha512-30iZtAPgz+LTIYoeivqYo853f02jBYSd5uGnGpkFV0M3xOt9aN73erkgYAmZU43x4VfqcnLxW9Kpg3R5LC4YYw==",
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "Apache-2.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
"dependencies": {
"@jridgewell/gen-mapping": "^0.3.5",
"@jridgewell/trace-mapping": "^0.3.24"
},
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/@babel/code-frame": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.26.2",
"resolved": "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.26.2.tgz",
"integrity": "sha512-RJlIHRueQgwWitWgF8OdFYGZX328Ax5BCemNGlqHfplnRT9ESi8JkFlvaVYbS+UubVY6dpv87Fs2u5M29iNFVQ==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@babel/helper-validator-identifier": "^7.25.9",
"js-tokens": "^4.0.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
"picocolors": "^1.0.0"
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/compat-data": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.26.5",
"resolved": "https://registry.npmjs.org/@babel/compat-data/-/compat-data-7.26.5.tgz",
"integrity": "sha512-XvcZi1KWf88RVbF9wn8MN6tYFloU5qX8KjuF3E1PVBmJ9eypXfs4GRiJwLuTZL0iSnJUKn1BFPa5BPZZJyFzPg==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/core": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.26.0",
"resolved": "https://registry.npmjs.org/@babel/core/-/core-7.26.0.tgz",
"integrity": "sha512-i1SLeK+DzNnQ3LL/CswPCa/E5u4lh1k6IAEphON8F+cXt0t9euTshDru0q7/IqMa1PMPz5RnHuHscF8/ZJsStg==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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": {
"@ampproject/remapping": "^2.2.0",
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@babel/code-frame": "^7.26.0",
"@babel/generator": "^7.26.0",
"@babel/helper-compilation-targets": "^7.25.9",
"@babel/helper-module-transforms": "^7.26.0",
"@babel/helpers": "^7.26.0",
"@babel/parser": "^7.26.0",
"@babel/template": "^7.25.9",
"@babel/traverse": "^7.25.9",
"@babel/types": "^7.26.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
"convert-source-map": "^2.0.0",
"debug": "^4.1.0",
"gensync": "^1.0.0-beta.2",
"json5": "^2.2.3",
"semver": "^6.3.1"
},
"engines": {
"node": ">=6.9.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/babel"
}
},
"node_modules/@babel/core/node_modules/semver": {
"version": "6.3.1",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz",
"integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==",
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "ISC",
✨(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
"bin": {
"semver": "bin/semver.js"
}
},
"node_modules/@babel/generator": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.26.5",
"resolved": "https://registry.npmjs.org/@babel/generator/-/generator-7.26.5.tgz",
"integrity": "sha512-2caSP6fN9I7HOe6nqhtft7V4g7/V/gfDsC3Ag4W7kEzzvRGKqiv0pu0HogPiZ3KaVSoNDhUws6IJjDjpfmYIXw==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@babel/parser": "^7.26.5",
"@babel/types": "^7.26.5",
✨(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
"@jridgewell/gen-mapping": "^0.3.5",
"@jridgewell/trace-mapping": "^0.3.25",
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"jsesc": "^3.0.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
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-compilation-targets": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.26.5",
"resolved": "https://registry.npmjs.org/@babel/helper-compilation-targets/-/helper-compilation-targets-7.26.5.tgz",
"integrity": "sha512-IXuyn5EkouFJscIDuFF5EsiSolseme1s0CZB+QxVugqJLYmKdxI1VfIBOst0SUu4rnk2Z7kqTwmoO1lp3HIfnA==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@babel/compat-data": "^7.26.5",
"@babel/helper-validator-option": "^7.25.9",
"browserslist": "^4.24.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
"lru-cache": "^5.1.1",
"semver": "^6.3.1"
},
"engines": {
"node": ">=6.9.0"
}
},
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node_modules/@babel/helper-compilation-targets/node_modules/browserslist": {
"version": "4.24.4",
"resolved": "https://registry.npmjs.org/browserslist/-/browserslist-4.24.4.tgz",
"integrity": "sha512-KDi1Ny1gSePi1vm0q4oxSF8b4DR44GF4BbmS2YdhPLOEqd8pDviZOGH/GsmRwoWJ2+5Lr085X7naowMwKHDG1A==",
"dev": true,
"funding": [
{
"type": "opencollective",
"url": "https://opencollective.com/browserslist"
},
{
"type": "tidelift",
"url": "https://tidelift.com/funding/github/npm/browserslist"
},
{
"type": "github",
"url": "https://github.com/sponsors/ai"
}
],
"license": "MIT",
"dependencies": {
"caniuse-lite": "^1.0.30001688",
"electron-to-chromium": "^1.5.73",
"node-releases": "^2.0.19",
"update-browserslist-db": "^1.1.1"
},
"bin": {
"browserslist": "cli.js"
},
"engines": {
"node": "^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7"
}
},
✨(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
"node_modules/@babel/helper-compilation-targets/node_modules/semver": {
"version": "6.3.1",
"resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz",
"integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==",
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "ISC",
✨(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
"bin": {
"semver": "bin/semver.js"
}
},
"node_modules/@babel/helper-module-imports": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.25.9",
"resolved": "https://registry.npmjs.org/@babel/helper-module-imports/-/helper-module-imports-7.25.9.tgz",
"integrity": "sha512-tnUA4RsrmflIM6W6RFTLFSXITtl0wKjgpnLgXyowocVPrbYrLUXSBXDgTs8BlbmIzIdlBySRQjINYs2BAkiLtw==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@babel/traverse": "^7.25.9",
"@babel/types": "^7.25.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
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-module-transforms": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.26.0",
"resolved": "https://registry.npmjs.org/@babel/helper-module-transforms/-/helper-module-transforms-7.26.0.tgz",
"integrity": "sha512-xO+xu6B5K2czEnQye6BHA7DolFFmS3LB7stHZFaOLb1pAwO1HWLS8fXA+eh0A2yIvltPVmx3eNNDBJA2SLHXFw==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@babel/helper-module-imports": "^7.25.9",
"@babel/helper-validator-identifier": "^7.25.9",
"@babel/traverse": "^7.25.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
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0"
}
},
"node_modules/@babel/helper-plugin-utils": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.26.5",
"resolved": "https://registry.npmjs.org/@babel/helper-plugin-utils/-/helper-plugin-utils-7.26.5.tgz",
"integrity": "sha512-RS+jZcRdZdRFzMyr+wcsaqOmld1/EqTghfaBGQQd/WnRdzdlvSZ//kF7U8VQTxf1ynZ4cjUcYgjVGx13ewNPMg==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-string-parser": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.25.9",
"resolved": "https://registry.npmjs.org/@babel/helper-string-parser/-/helper-string-parser-7.25.9.tgz",
"integrity": "sha512-4A/SCr/2KLd5jrtOMFzaKjVtAei3+2r/NChoBNoZ3EyP/+GlhoaEGoWOZUmFmoITP7zOJyHIMm+DYRd8o3PvHA==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-validator-identifier": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.25.9",
"resolved": "https://registry.npmjs.org/@babel/helper-validator-identifier/-/helper-validator-identifier-7.25.9.tgz",
"integrity": "sha512-Ed61U6XJc3CVRfkERJWDz4dJwKe7iLmmJsbOGu9wSloNSFttHV0I8g6UAgb7qnK5ly5bGLPd4oXZlxCdANBOWQ==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helper-validator-option": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.25.9",
"resolved": "https://registry.npmjs.org/@babel/helper-validator-option/-/helper-validator-option-7.25.9.tgz",
"integrity": "sha512-e/zv1co8pp55dNdEcCynfj9X7nyUKUXoUEwfXqaZt0omVOmDe9oOTdKStH4GmAw6zxMFs50ZayuMfHDKlO7Tfw==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/helpers": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.26.0",
"resolved": "https://registry.npmjs.org/@babel/helpers/-/helpers-7.26.0.tgz",
"integrity": "sha512-tbhNuIxNcVb21pInl3ZSjksLCvgdZy9KwJ8brv993QtIVKJBBkYXz4q4ZbAv31GdnC+R90np23L5FbEBlthAEw==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@babel/template": "^7.25.9",
"@babel/types": "^7.26.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
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/parser": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.26.5",
"resolved": "https://registry.npmjs.org/@babel/parser/-/parser-7.26.5.tgz",
"integrity": "sha512-SRJ4jYmXRqV1/Xc+TIVG84WjHBXKlxO9sHQnA2Pf12QQEAp1LOh6kDzNHXcUnbH1QI0FDoPPVOt+vyUDucxpaw==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@babel/types": "^7.26.5"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
},
✨(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
"bin": {
"parser": "bin/babel-parser.js"
},
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/@babel/plugin-transform-react-jsx-self": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.25.9",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-react-jsx-self/-/plugin-transform-react-jsx-self-7.25.9.tgz",
"integrity": "sha512-y8quW6p0WHkEhmErnfe58r7x0A70uKphQm8Sp8cV7tjNQwK56sNVK0M73LK3WuYmsuyrftut4xAkjjgU0twaMg==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@babel/helper-plugin-utils": "^7.25.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
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-0"
}
},
"node_modules/@babel/plugin-transform-react-jsx-source": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.25.9",
"resolved": "https://registry.npmjs.org/@babel/plugin-transform-react-jsx-source/-/plugin-transform-react-jsx-source-7.25.9.tgz",
"integrity": "sha512-+iqjT8xmXhhYv4/uiYd8FNQsraMFZIfxVSqxxVSZP0WbbSAWvBXAul0m/zu+7Vv4O/3WtApy9pmaTMiumEZgfg==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@babel/helper-plugin-utils": "^7.25.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
},
"engines": {
"node": ">=6.9.0"
},
"peerDependencies": {
"@babel/core": "^7.0.0-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
"node_modules/@babel/runtime": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "7.25.6",
"resolved": "https://registry.npmjs.org/@babel/runtime/-/runtime-7.25.6.tgz",
"integrity": "sha512-VBj9MYyDb9tuLq7yzqjgzt6Q+IBQLrGZfdjOekyEirZPHxXWoTSGUTMrpsfi58Up73d13NfYLv8HT9vmznjzhQ==",
🌐(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
"dependencies": {
"regenerator-runtime": "^0.14.0"
},
"engines": {
"node": ">=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
"node_modules/@babel/template": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.25.9",
"resolved": "https://registry.npmjs.org/@babel/template/-/template-7.25.9.tgz",
"integrity": "sha512-9DGttpmPvIxBb/2uwpVo3dqJ+O6RooAFOS+lB+xDqoE2PVCE8nfoHMdZLpfCQRLwvohzXISPZcgxt80xLfsuwg==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@babel/code-frame": "^7.25.9",
"@babel/parser": "^7.25.9",
"@babel/types": "^7.25.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
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/traverse": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.26.5",
"resolved": "https://registry.npmjs.org/@babel/traverse/-/traverse-7.26.5.tgz",
"integrity": "sha512-rkOSPOw+AXbgtwUga3U4u8RpoK9FEFWBNAlTpcnkLFjL5CT+oyHNuUUC/xx6XefEJ16r38r8Bc/lfp6rYuHeJQ==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@babel/code-frame": "^7.26.2",
"@babel/generator": "^7.26.5",
"@babel/parser": "^7.26.5",
"@babel/template": "^7.25.9",
"@babel/types": "^7.26.5",
✨(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
"debug": "^4.3.1",
"globals": "^11.1.0"
},
"engines": {
"node": ">=6.9.0"
}
},
"node_modules/@babel/types": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "7.26.5",
"resolved": "https://registry.npmjs.org/@babel/types/-/types-7.26.5.tgz",
"integrity": "sha512-L6mZmwFDK6Cjh1nRCLXpa6no13ZIioJDz7mdkzHv399pThrTa/k0nUlNaenOeh2kWu/iaOQYElEpKPUswUa9Vg==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@babel/helper-string-parser": "^7.25.9",
"@babel/helper-validator-identifier": "^7.25.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
},
"engines": {
"node": ">=6.9.0"
}
},
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"node_modules/@bufbuild/protobuf": {
"version": "1.10.0",
"resolved": "https://registry.npmjs.org/@bufbuild/protobuf/-/protobuf-1.10.0.tgz",
⬆️(frontend) bump LiveKit-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-16 18:42:31 +01:00
"integrity": "sha512-QDdVFLoN93Zjg36NoQPZfsVH9tZew7wKDKyV5qRdj8ntT4wQCOradQjRaTdwMhWUYsgKsvCINKKm87FdEk96Ag==",
"license": "(Apache-2.0 AND BSD-3-Clause)"
♻️(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
},
"node_modules/@clack/core": {
"version": "0.3.4",
"resolved": "https://registry.npmjs.org/@clack/core/-/core-0.3.4.tgz",
"integrity": "sha512-H4hxZDXgHtWTwV3RAVenqcC4VbJZNegbBjlPvzOzCouXtS2y3sDvlO3IsbrPNWuLWPPlYVYPghQdSF64683Ldw==",
"dev": true,
"dependencies": {
"picocolors": "^1.0.0",
"sisteransi": "^1.0.5"
}
},
"node_modules/@clack/prompts": {
"version": "0.7.0",
"resolved": "https://registry.npmjs.org/@clack/prompts/-/prompts-0.7.0.tgz",
"integrity": "sha512-0MhX9/B4iL6Re04jPrttDm+BsP8y6mS7byuv0BvXgdXhbV5PdlsHt55dvNsuBCPZ7xq1oTAOOuotR9NFbQyMSA==",
"bundleDependencies": [
"is-unicode-supported"
],
"dev": true,
"dependencies": {
"@clack/core": "^0.3.3",
"is-unicode-supported": "*",
"picocolors": "^1.0.0",
"sisteransi": "^1.0.5"
}
},
"node_modules/@clack/prompts/node_modules/is-unicode-supported": {
"version": "1.3.0",
⬆️(dependencies) update js dependencies
2025-01-27 14:32:11 +00:00
"dev": true,
♻️(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
"inBundle": true,
"license": "MIT",
"engines": {
"node": ">=12"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/@csstools/postcss-cascade-layers": {
"version": "4.0.6",
"resolved": "https://registry.npmjs.org/@csstools/postcss-cascade-layers/-/postcss-cascade-layers-4.0.6.tgz",
"integrity": "sha512-Xt00qGAQyqAODFiFEJNkTpSUz5VfYqnDLECdlA/Vv17nl/OIV5QfTRHGAXrBGG5YcJyHpJ+GF9gF/RZvOQz4oA==",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/csstools"
},
{
"type": "opencollective",
"url": "https://opencollective.com/csstools"
}
],
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT-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
"dependencies": {
"@csstools/selector-specificity": "^3.1.1",
"postcss-selector-parser": "^6.0.13"
},
"engines": {
"node": "^14 || ^16 || >=18"
},
"peerDependencies": {
"postcss": "^8.4"
}
},
"node_modules/@csstools/selector-specificity": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/@csstools/selector-specificity/-/selector-specificity-3.1.1.tgz",
"integrity": "sha512-a7cxGcJ2wIlMFLlh8z2ONm+715QkPHiyJcxwQlKOz/03GPw1COpfhcmC9wm4xlZfp//jWHNNMwzjtqHXVWU9KA==",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/csstools"
},
{
"type": "opencollective",
"url": "https://opencollective.com/csstools"
}
],
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT-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
"engines": {
"node": "^14 || ^16 || >=18"
},
"peerDependencies": {
"postcss-selector-parser": "^6.0.13"
}
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
},
✨(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
"node_modules/@esbuild/aix-ppc64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/aix-ppc64/-/aix-ppc64-0.20.2.tgz",
"integrity": "sha512-D+EBOJHXdNZcLJRBkhENNG8Wji2kgc9AZ9KiPr1JuZjsNtyHzrsfLRrY0tk2H2aoFu6RANO1y1iPPUCDYWkb5g==",
✨(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
"cpu": [
"ppc64"
],
"dev": true,
"optional": true,
"os": [
"aix"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/android-arm": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/android-arm/-/android-arm-0.20.2.tgz",
"integrity": "sha512-t98Ra6pw2VaDhqNWO2Oph2LXbz/EJcnLmKLGBJwEwXX/JAN83Fym1rU8l0JUWK6HkIbWONCSSatf4sf2NBRx/w==",
✨(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
"cpu": [
"arm"
],
"dev": true,
"optional": true,
"os": [
"android"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/android-arm64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/android-arm64/-/android-arm64-0.20.2.tgz",
"integrity": "sha512-mRzjLacRtl/tWU0SvD8lUEwb61yP9cqQo6noDZP/O8VkwafSYwZ4yWy24kan8jE/IMERpYncRt2dw438LP3Xmg==",
✨(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
"cpu": [
"arm64"
],
"dev": true,
"optional": true,
"os": [
"android"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/android-x64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/android-x64/-/android-x64-0.20.2.tgz",
"integrity": "sha512-btzExgV+/lMGDDa194CcUQm53ncxzeBrWJcncOBxuC6ndBkKxnHdFJn86mCIgTELsooUmwUm9FkhSp5HYu00Rg==",
✨(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
"cpu": [
"x64"
],
"dev": true,
"optional": true,
"os": [
"android"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/darwin-arm64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/darwin-arm64/-/darwin-arm64-0.20.2.tgz",
"integrity": "sha512-4J6IRT+10J3aJH3l1yzEg9y3wkTDgDk7TSDFX+wKFiWjqWp/iCfLIYzGyasx9l0SAFPT1HwSCR+0w/h1ES/MjA==",
✨(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
"cpu": [
"arm64"
],
"dev": true,
"optional": true,
"os": [
"darwin"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/darwin-x64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/darwin-x64/-/darwin-x64-0.20.2.tgz",
"integrity": "sha512-tBcXp9KNphnNH0dfhv8KYkZhjc+H3XBkF5DKtswJblV7KlT9EI2+jeA8DgBjp908WEuYll6pF+UStUCfEpdysA==",
✨(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
"cpu": [
"x64"
],
"dev": true,
"optional": true,
"os": [
"darwin"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/freebsd-arm64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/freebsd-arm64/-/freebsd-arm64-0.20.2.tgz",
"integrity": "sha512-d3qI41G4SuLiCGCFGUrKsSeTXyWG6yem1KcGZVS+3FYlYhtNoNgYrWcvkOoaqMhwXSMrZRl69ArHsGJ9mYdbbw==",
✨(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
"cpu": [
"arm64"
],
"dev": true,
"optional": true,
"os": [
"freebsd"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/freebsd-x64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/freebsd-x64/-/freebsd-x64-0.20.2.tgz",
"integrity": "sha512-d+DipyvHRuqEeM5zDivKV1KuXn9WeRX6vqSqIDgwIfPQtwMP4jaDsQsDncjTDDsExT4lR/91OLjRo8bmC1e+Cw==",
✨(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
"cpu": [
"x64"
],
"dev": true,
"optional": true,
"os": [
"freebsd"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/linux-arm": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-arm/-/linux-arm-0.20.2.tgz",
"integrity": "sha512-VhLPeR8HTMPccbuWWcEUD1Az68TqaTYyj6nfE4QByZIQEQVWBB8vup8PpR7y1QHL3CpcF6xd5WVBU/+SBEvGTg==",
✨(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
"cpu": [
"arm"
],
"dev": true,
"optional": true,
"os": [
"linux"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/linux-arm64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-arm64/-/linux-arm64-0.20.2.tgz",
"integrity": "sha512-9pb6rBjGvTFNira2FLIWqDk/uaf42sSyLE8j1rnUpuzsODBq7FvpwHYZxQ/It/8b+QOS1RYfqgGFNLRI+qlq2A==",
✨(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
"cpu": [
"arm64"
],
"dev": true,
"optional": true,
"os": [
"linux"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/linux-ia32": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-ia32/-/linux-ia32-0.20.2.tgz",
"integrity": "sha512-o10utieEkNPFDZFQm9CoP7Tvb33UutoJqg3qKf1PWVeeJhJw0Q347PxMvBgVVFgouYLGIhFYG0UGdBumROyiig==",
✨(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
"cpu": [
"ia32"
],
"dev": true,
"optional": true,
"os": [
"linux"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/linux-loong64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-loong64/-/linux-loong64-0.20.2.tgz",
"integrity": "sha512-PR7sp6R/UC4CFVomVINKJ80pMFlfDfMQMYynX7t1tNTeivQ6XdX5r2XovMmha/VjR1YN/HgHWsVcTRIMkymrgQ==",
✨(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
"cpu": [
"loong64"
],
"dev": true,
"optional": true,
"os": [
"linux"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/linux-mips64el": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-mips64el/-/linux-mips64el-0.20.2.tgz",
"integrity": "sha512-4BlTqeutE/KnOiTG5Y6Sb/Hw6hsBOZapOVF6njAESHInhlQAghVVZL1ZpIctBOoTFbQyGW+LsVYZ8lSSB3wkjA==",
✨(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
"cpu": [
"mips64el"
],
"dev": true,
"optional": true,
"os": [
"linux"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/linux-ppc64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-ppc64/-/linux-ppc64-0.20.2.tgz",
"integrity": "sha512-rD3KsaDprDcfajSKdn25ooz5J5/fWBylaaXkuotBDGnMnDP1Uv5DLAN/45qfnf3JDYyJv/ytGHQaziHUdyzaAg==",
✨(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
"cpu": [
"ppc64"
],
"dev": true,
"optional": true,
"os": [
"linux"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/linux-riscv64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-riscv64/-/linux-riscv64-0.20.2.tgz",
"integrity": "sha512-snwmBKacKmwTMmhLlz/3aH1Q9T8v45bKYGE3j26TsaOVtjIag4wLfWSiZykXzXuE1kbCE+zJRmwp+ZbIHinnVg==",
✨(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
"cpu": [
"riscv64"
],
"dev": true,
"optional": true,
"os": [
"linux"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/linux-s390x": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-s390x/-/linux-s390x-0.20.2.tgz",
"integrity": "sha512-wcWISOobRWNm3cezm5HOZcYz1sKoHLd8VL1dl309DiixxVFoFe/o8HnwuIwn6sXre88Nwj+VwZUvJf4AFxkyrQ==",
✨(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
"cpu": [
"s390x"
],
"dev": true,
"optional": true,
"os": [
"linux"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/linux-x64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-x64/-/linux-x64-0.20.2.tgz",
"integrity": "sha512-1MdwI6OOTsfQfek8sLwgyjOXAu+wKhLEoaOLTjbijk6E2WONYpH9ZU2mNtR+lZ2B4uwr+usqGuVfFT9tMtGvGw==",
✨(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
"cpu": [
"x64"
],
"dev": true,
"optional": true,
"os": [
"linux"
],
"engines": {
"node": ">=12"
}
},
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node_modules/@esbuild/netbsd-arm64": {
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/netbsd-arm64/-/netbsd-arm64-0.24.2.tgz",
"integrity": "sha512-wuLK/VztRRpMt9zyHSazyCVdCXlpHkKm34WUyinD2lzK07FAHTq0KQvZZlXikNWkDGoT6x3TD51jKQ7gMVpopw==",
"cpu": [
"arm64"
],
"license": "MIT",
"optional": true,
"os": [
"netbsd"
],
"engines": {
"node": ">=18"
}
},
✨(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
"node_modules/@esbuild/netbsd-x64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/netbsd-x64/-/netbsd-x64-0.20.2.tgz",
"integrity": "sha512-K8/DhBxcVQkzYc43yJXDSyjlFeHQJBiowJ0uVL6Tor3jGQfSGHNNJcWxNbOI8v5k82prYqzPuwkzHt3J1T1iZQ==",
✨(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
"cpu": [
"x64"
],
"dev": true,
"optional": true,
"os": [
"netbsd"
],
"engines": {
"node": ">=12"
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/@esbuild/openbsd-arm64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/openbsd-arm64/-/openbsd-arm64-0.24.2.tgz",
"integrity": "sha512-YQbi46SBct6iKnszhSvdluqDmxCJA+Pu280Av9WICNwQmMxV7nLRHZfjQzwbPs3jeWnuAhE9Jy0NrnJ12Oz+0A==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"arm64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"openbsd"
],
"engines": {
"node": ">=18"
}
},
✨(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
"node_modules/@esbuild/openbsd-x64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/openbsd-x64/-/openbsd-x64-0.20.2.tgz",
"integrity": "sha512-eMpKlV0SThJmmJgiVyN9jTPJ2VBPquf6Kt/nAoo6DgHAoN57K15ZghiHaMvqjCye/uU4X5u3YSMgVBI1h3vKrQ==",
✨(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
"cpu": [
"x64"
],
"dev": true,
"optional": true,
"os": [
"openbsd"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/sunos-x64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/sunos-x64/-/sunos-x64-0.20.2.tgz",
"integrity": "sha512-2UyFtRC6cXLyejf/YEld4Hajo7UHILetzE1vsRcGL3earZEW77JxrFjH4Ez2qaTiEfMgAXxfAZCm1fvM/G/o8w==",
✨(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
"cpu": [
"x64"
],
"dev": true,
"optional": true,
"os": [
"sunos"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/win32-arm64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/win32-arm64/-/win32-arm64-0.20.2.tgz",
"integrity": "sha512-GRibxoawM9ZCnDxnP3usoUDO9vUkpAxIIZ6GQI+IlVmr5kP3zUq+l17xELTHMWTWzjxa2guPNyrpq1GWmPvcGQ==",
✨(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
"cpu": [
"arm64"
],
"dev": true,
"optional": true,
"os": [
"win32"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/win32-ia32": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/win32-ia32/-/win32-ia32-0.20.2.tgz",
"integrity": "sha512-HfLOfn9YWmkSKRQqovpnITazdtquEW8/SoHW7pWpuEeguaZI4QnCRW6b+oZTztdBnZOS2hqJ6im/D5cPzBTTlQ==",
✨(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
"cpu": [
"ia32"
],
"dev": true,
"optional": true,
"os": [
"win32"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@esbuild/win32-x64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/@esbuild/win32-x64/-/win32-x64-0.20.2.tgz",
"integrity": "sha512-N49X4lJX27+l9jbLKSqZ6bKNjzQvHaT8IIFUy+YIqmXQdjYCToGWwOItDrfby14c78aDd5NHQl29xingXfCdLQ==",
✨(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
"cpu": [
"x64"
],
"dev": true,
"optional": true,
"os": [
"win32"
],
"engines": {
"node": ">=12"
}
},
"node_modules/@eslint-community/eslint-utils": {
"version": "4.4.0",
"resolved": "https://registry.npmjs.org/@eslint-community/eslint-utils/-/eslint-utils-4.4.0.tgz",
"integrity": "sha512-1/sA4dwrzBAyeUoQ6oxahHKmrZvsnLCg4RfxW3ZFGGmQkSNQPFNLV9CUEFQP1x9EYXHTo5p6xdhZM1Ne9p/AfA==",
"dev": true,
"dependencies": {
"eslint-visitor-keys": "^3.3.0"
},
"engines": {
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
},
"peerDependencies": {
"eslint": "^6.0.0 || ^7.0.0 || >=8.0.0"
}
},
"node_modules/@eslint-community/regexpp": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "4.11.1",
"resolved": "https://registry.npmjs.org/@eslint-community/regexpp/-/regexpp-4.11.1.tgz",
"integrity": "sha512-m4DVN9ZqskZoLU5GlWZadwDnYo3vAEydiUayB9widCl9ffWx2IvPnp6n3on5rJmziJSw9Bv+Z3ChDVdMwXCY8Q==",
✨(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
"dev": true,
"engines": {
"node": "^12.0.0 || ^14.0.0 || >=16.0.0"
}
},
"node_modules/@eslint/eslintrc": {
"version": "2.1.4",
"resolved": "https://registry.npmjs.org/@eslint/eslintrc/-/eslintrc-2.1.4.tgz",
"integrity": "sha512-269Z39MS6wVJtsoUl10L60WdkhJVdPG24Q4eZTH3nnF6lpvSShEK3wQjDX9JRWAUPvPh7COouPpU9IrqaZFvtQ==",
"dev": true,
"dependencies": {
"ajv": "^6.12.4",
"debug": "^4.3.2",
"espree": "^9.6.0",
"globals": "^13.19.0",
"ignore": "^5.2.0",
"import-fresh": "^3.2.1",
"js-yaml": "^4.1.0",
"minimatch": "^3.1.2",
"strip-json-comments": "^3.1.1"
},
"engines": {
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
},
"funding": {
"url": "https://opencollective.com/eslint"
}
},
"node_modules/@eslint/eslintrc/node_modules/brace-expansion": {
"version": "1.1.11",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz",
"integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==",
"dev": true,
"dependencies": {
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
}
},
"node_modules/@eslint/eslintrc/node_modules/globals": {
"version": "13.24.0",
"resolved": "https://registry.npmjs.org/globals/-/globals-13.24.0.tgz",
"integrity": "sha512-AhO5QUcj8llrbG09iWhPU2B204J1xnPeL8kQmVorSsy+Sjj1sk8gIyh6cUocGmH4L0UuhAJy+hJMRA4mgA4mFQ==",
"dev": true,
"dependencies": {
"type-fest": "^0.20.2"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/@eslint/eslintrc/node_modules/minimatch": {
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz",
"integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==",
"dev": true,
"dependencies": {
"brace-expansion": "^1.1.7"
},
"engines": {
"node": "*"
}
},
"node_modules/@eslint/js": {
"version": "8.57.0",
"resolved": "https://registry.npmjs.org/@eslint/js/-/js-8.57.0.tgz",
"integrity": "sha512-Ys+3g2TaW7gADOJzPt83SJtCDhMjndcDMFVQ/Tj9iA1BfJzFKD9mAUXT3OenpuPHbI6P/myECxRJrofUsDx/5g==",
"dev": true,
"engines": {
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
}
},
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"node_modules/@floating-ui/core": {
⬆️(frontend) bump LiveKit-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-16 18:42:31 +01:00
"version": "1.6.9",
"resolved": "https://registry.npmjs.org/@floating-ui/core/-/core-1.6.9.tgz",
"integrity": "sha512-uMXCuQ3BItDUbAMhIXw7UPXRfAlOAvZzdK9BWpE60MCn+Svt3aLn9jsPTi/WNGlRUu2uI0v5S7JiIUsbsvh3fw==",
"license": "MIT",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"dependencies": {
⬆️(frontend) bump LiveKit-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-16 18:42:31 +01:00
"@floating-ui/utils": "^0.2.9"
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
}
},
"node_modules/@floating-ui/dom": {
⬆️(frontend) fix persistent choices nesting issue Upgraded to livekit/components-react v2.5.4, fixing a bug in v2.5.3 that caused repeated nesting of persistent user choices, exhausting the quota. Thanks to Lukas for the quick fix.
2024-09-17 19:41:07 +02:00
"version": "1.6.11",
"resolved": "https://registry.npmjs.org/@floating-ui/dom/-/dom-1.6.11.tgz",
"integrity": "sha512-qkMCxSR24v2vGkhYDo/UzxfJN3D4syqSjyuTFz6C7XcpU1pASPRieNI0Kj5VP3/503mOfYiGY891ugBX1GlABQ==",
⬆️(frontend) bump LiveKit-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-16 18:42:31 +01:00
"license": "MIT",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"@floating-ui/core": "^1.6.0",
⬆️(frontend) fix persistent choices nesting issue Upgraded to livekit/components-react v2.5.4, fixing a bug in v2.5.3 that caused repeated nesting of persistent user choices, exhausting the quota. Thanks to Lukas for the quick fix.
2024-09-17 19:41:07 +02:00
"@floating-ui/utils": "^0.2.8"
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
}
},
"node_modules/@floating-ui/utils": {
⬆️(frontend) bump LiveKit-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-16 18:42:31 +01:00
"version": "0.2.9",
"resolved": "https://registry.npmjs.org/@floating-ui/utils/-/utils-0.2.9.tgz",
"integrity": "sha512-MDWhGtE+eHw5JW7lq4qhc5yRLS11ERl1c7Z6Xd0a58DozHES6EnNNwUWbMiG4J9Cgj053Bhk8zvlhFYKVhULwg==",
"license": "MIT"
♻️(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
},
"node_modules/@formatjs/ecma402-abstract": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "2.3.2",
"resolved": "https://registry.npmjs.org/@formatjs/ecma402-abstract/-/ecma402-abstract-2.3.2.tgz",
"integrity": "sha512-6sE5nyvDloULiyOMbOTJEEgWL32w+VHkZQs8S02Lnn8Y/O5aQhjOEXwWzvR7SsBE/exxlSpY2EsWZgqHbtLatg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@formatjs/fast-memoize": "2.2.6",
"@formatjs/intl-localematcher": "0.5.10",
"decimal.js": "10",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"tslib": "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
}
},
"node_modules/@formatjs/fast-memoize": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "2.2.6",
"resolved": "https://registry.npmjs.org/@formatjs/fast-memoize/-/fast-memoize-2.2.6.tgz",
"integrity": "sha512-luIXeE2LJbQnnzotY1f2U2m7xuQNj2DA8Vq4ce1BY9ebRZaoPB1+8eZ6nXpLzsxuW5spQxr7LdCg+CApZwkqkw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"tslib": "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
}
},
"node_modules/@formatjs/icu-messageformat-parser": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "2.11.0",
"resolved": "https://registry.npmjs.org/@formatjs/icu-messageformat-parser/-/icu-messageformat-parser-2.11.0.tgz",
"integrity": "sha512-Hp81uTjjdTk3FLh/dggU5NK7EIsVWc5/ZDWrIldmf2rBuPejuZ13CZ/wpVE2SToyi4EiroPTQ1XJcJuZFIxTtw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@formatjs/ecma402-abstract": "2.3.2",
"@formatjs/icu-skeleton-parser": "1.8.12",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"tslib": "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
}
},
"node_modules/@formatjs/icu-skeleton-parser": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "1.8.12",
"resolved": "https://registry.npmjs.org/@formatjs/icu-skeleton-parser/-/icu-skeleton-parser-1.8.12.tgz",
"integrity": "sha512-QRAY2jC1BomFQHYDMcZtClqHR55EEnB96V7Xbk/UiBodsuFc5kujybzt87+qj1KqmJozFhk6n4KiT1HKwAkcfg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@formatjs/ecma402-abstract": "2.3.2",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"tslib": "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
}
},
"node_modules/@formatjs/intl-localematcher": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "0.5.10",
"resolved": "https://registry.npmjs.org/@formatjs/intl-localematcher/-/intl-localematcher-0.5.10.tgz",
"integrity": "sha512-af3qATX+m4Rnd9+wHcjJ4w2ijq+rAVP3CCinJQvFv1kgSu1W6jypUmvleJxcewdxmutM8dmIRZFxO/IQBZmP2Q==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"tslib": "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
}
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
},
🌐(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
"node_modules/@gulpjs/to-absolute-glob": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/@gulpjs/to-absolute-glob/-/to-absolute-glob-4.0.0.tgz",
"integrity": "sha512-kjotm7XJrJ6v+7knhPaRgaT6q8F8K2jiafwYdNHLzmV0uGLuZY43FK6smNSHUPrhq5kX2slCUy+RGG/xGqmIKA==",
"dependencies": {
"is-negated-glob": "^1.0.0"
},
"engines": {
"node": ">=10.13.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
"node_modules/@humanwhocodes/config-array": {
"version": "0.11.14",
"resolved": "https://registry.npmjs.org/@humanwhocodes/config-array/-/config-array-0.11.14.tgz",
"integrity": "sha512-3T8LkOmg45BV5FICb15QQMsyUSWrQ8AygVfC7ZG32zOalnqrilm018ZVCw0eapXux8FtA33q8PSRSstjee3jSg==",
"deprecated": "Use @eslint/config-array instead",
"dev": true,
"dependencies": {
"@humanwhocodes/object-schema": "^2.0.2",
"debug": "^4.3.1",
"minimatch": "^3.0.5"
},
"engines": {
"node": ">=10.10.0"
}
},
"node_modules/@humanwhocodes/config-array/node_modules/brace-expansion": {
"version": "1.1.11",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz",
"integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==",
"dev": true,
"dependencies": {
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
}
},
"node_modules/@humanwhocodes/config-array/node_modules/minimatch": {
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz",
"integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==",
"dev": true,
"dependencies": {
"brace-expansion": "^1.1.7"
},
"engines": {
"node": "*"
}
},
"node_modules/@humanwhocodes/module-importer": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/@humanwhocodes/module-importer/-/module-importer-1.0.1.tgz",
"integrity": "sha512-bxveV4V8v5Yb4ncFTT3rPSgZBOpCkjfK0y4oVVVJwIuDVBRMDXrPyXRL988i5ap9m9bnyEEjWfm5WkBmtffLfA==",
"dev": true,
"engines": {
"node": ">=12.22"
},
"funding": {
"type": "github",
"url": "https://github.com/sponsors/nzakas"
}
},
"node_modules/@humanwhocodes/object-schema": {
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/@humanwhocodes/object-schema/-/object-schema-2.0.3.tgz",
"integrity": "sha512-93zYdMES/c1D69yZiKDBj0V24vqNzB/koF26KPaagAfd3P/4gUlh3Dys5ogAK+Exi9QyzlD8x/08Zt7wIKcDcA==",
"deprecated": "Use @eslint/object-schema instead",
"dev": true
},
♻️(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
"node_modules/@internationalized/date": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.7.0",
"resolved": "https://registry.npmjs.org/@internationalized/date/-/date-3.7.0.tgz",
"integrity": "sha512-VJ5WS3fcVx0bejE/YHfbDKR/yawZgKqn/if+oEeLqNwBtPzVB06olkfcnojTmEMX+gTpH+FlQ69SHNitJ8/erQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
"@swc/helpers": "^0.5.0"
}
},
"node_modules/@internationalized/message": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "3.1.6",
"resolved": "https://registry.npmjs.org/@internationalized/message/-/message-3.1.6.tgz",
"integrity": "sha512-JxbK3iAcTIeNr1p0WIFg/wQJjIzJt9l/2KNY/48vXV7GRGZSv3zMxJsce008fZclk2cDC8y0Ig3odceHO7EfNQ==",
"license": "Apache-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
"dependencies": {
"@swc/helpers": "^0.5.0",
"intl-messageformat": "^10.1.0"
}
},
"node_modules/@internationalized/number": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "3.6.0",
"resolved": "https://registry.npmjs.org/@internationalized/number/-/number-3.6.0.tgz",
"integrity": "sha512-PtrRcJVy7nw++wn4W2OuePQQfTqDzfusSuY1QTtui4wa7r+rGVtR75pO8CyKvHvzyQYi3Q1uO5sY0AsB4e65Bw==",
"license": "Apache-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
"dependencies": {
"@swc/helpers": "^0.5.0"
}
},
"node_modules/@internationalized/string": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "3.2.5",
"resolved": "https://registry.npmjs.org/@internationalized/string/-/string-3.2.5.tgz",
"integrity": "sha512-rKs71Zvl2OKOHM+mzAFMIyqR5hI1d1O6BBkMK2/lkfg3fkmVh9Eeg0awcA8W2WqYqDOv6a86DIOlFpggwLtbuw==",
"license": "Apache-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
"dependencies": {
"@swc/helpers": "^0.5.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
"node_modules/@jridgewell/gen-mapping": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.3.8",
"resolved": "https://registry.npmjs.org/@jridgewell/gen-mapping/-/gen-mapping-0.3.8.tgz",
"integrity": "sha512-imAbBGkb+ebQyxKgzv5Hu2nmROxoDOXHh80evxdoXNOrvAnVx7zimzc1Oo5h9RlfV4vPXaE2iM5pOFbvOCClWA==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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": {
"@jridgewell/set-array": "^1.2.1",
"@jridgewell/sourcemap-codec": "^1.4.10",
"@jridgewell/trace-mapping": "^0.3.24"
},
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/@jridgewell/resolve-uri": {
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/@jridgewell/resolve-uri/-/resolve-uri-3.1.2.tgz",
"integrity": "sha512-bRISgCIjP20/tbWSPWMEi54QVPRZExkuD9lJL+UIxUKtwVJA8wW1Trb1jMs1RFXo1CBTNZ/5hpC9QvmKWdopKw==",
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/@jridgewell/set-array": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/@jridgewell/set-array/-/set-array-1.2.1.tgz",
"integrity": "sha512-R8gLRTZeyp03ymzP/6Lil/28tGeGEzhx1q2k703KGWRAI1VdvPIXdG70VJc2pAMw3NA6JKL5hhFu1sJX0Mnn/A==",
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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
"engines": {
"node": ">=6.0.0"
}
},
"node_modules/@jridgewell/sourcemap-codec": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "1.5.0",
"resolved": "https://registry.npmjs.org/@jridgewell/sourcemap-codec/-/sourcemap-codec-1.5.0.tgz",
"integrity": "sha512-gv3ZRaISU3fjPAgNsriBRqGWQL6quFx04YMPW/zD8XMLsU32mhCCbfbO6KZFLjvYpCZ8zyDEgqsgf+PwPaM7GQ==",
✨(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
"dev": true
},
"node_modules/@jridgewell/trace-mapping": {
"version": "0.3.25",
"resolved": "https://registry.npmjs.org/@jridgewell/trace-mapping/-/trace-mapping-0.3.25.tgz",
"integrity": "sha512-vNk6aEwybGtawWmy/PzwnGDOjCkLWSD2wqvjGGAgOAwCGWySYXfYoxt00IJkTF+8Lb57DwOb3Aa0o9CApepiYQ==",
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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": {
"@jridgewell/resolve-uri": "^3.1.0",
"@jridgewell/sourcemap-codec": "^1.4.14"
}
},
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"node_modules/@livekit/components-core": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.12.1",
"resolved": "https://registry.npmjs.org/@livekit/components-core/-/components-core-0.12.1.tgz",
"integrity": "sha512-R7qWoVzPckOYxEHZgP3Kp8u+amu+isnTptgoZV7+bpmLRBHI7mWnaD+0uDWlyIMjI1pBbK3wHg0ILKa5UytI+A==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"dependencies": {
⬆️(frontend) fix persistent choices nesting issue Upgraded to livekit/components-react v2.5.4, fixing a bug in v2.5.3 that caused repeated nesting of persistent user choices, exhausting the quota. Thanks to Lukas for the quick fix.
2024-09-17 19:41:07 +02:00
"@floating-ui/dom": "1.6.11",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"loglevel": "1.9.1",
"rxjs": "7.8.1"
},
"engines": {
"node": ">=18"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"livekit-client": "^2.8.1",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"tslib": "^2.6.2"
}
},
"node_modules/@livekit/components-react": {
⬆️(dependencies) update js dependencies
2025-01-27 14:32:11 +00:00
"version": "2.8.1",
"resolved": "https://registry.npmjs.org/@livekit/components-react/-/components-react-2.8.1.tgz",
"integrity": "sha512-XpuDu7iDMcN4pkV8CYNzHf9hLNdYOeEtbmCr7Zesy6Au3BxUl4aS1Ajmg0b75Rx7zTlkyCJt9Lm4VrEqbJCI6Q==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@livekit/components-core": "0.12.1",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"clsx": "2.1.1",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"usehooks-ts": "3.1.0"
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
},
"engines": {
"node": ">=18"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"@livekit/krisp-noise-filter": "^0.2.12",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"livekit-client": "^2.8.1",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"react": ">=18",
"react-dom": ">=18",
"tslib": "^2.6.2"
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
},
"peerDependenciesMeta": {
"@livekit/krisp-noise-filter": {
"optional": true
}
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
}
},
"node_modules/@livekit/components-styles": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/@livekit/components-styles/-/components-styles-1.1.4.tgz",
"integrity": "sha512-QCupn7tQ/dy/WZclrfsgtDe8peiGYS6Ied1IGkKOysaXo04l90t62SIUTKyxgd0dNDhUDC0p34qCggGZs/44lQ==",
"license": "Apache-2.0",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"engines": {
"node": ">=18"
}
},
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"node_modules/@livekit/mutex": {
⬆️(frontend) bump LiveKit-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-16 18:42:31 +01:00
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/@livekit/mutex/-/mutex-1.1.1.tgz",
"integrity": "sha512-EsshAucklmpuUAfkABPxJNhzj9v2sG7JuzFDL4ML1oJQSV14sqrpTYnsaOudMAw9yOaW53NU3QQTlUQoRs4czw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0"
},
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"node_modules/@livekit/protocol": {
⬆️(frontend) bump LiveKit-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-16 18:42:31 +01:00
"version": "1.30.0",
"resolved": "https://registry.npmjs.org/@livekit/protocol/-/protocol-1.30.0.tgz",
"integrity": "sha512-SDI9ShVKj8N3oOSinr8inaxD3FXgmgoJlqN35uU/Yx1sdoDeQbzAuBFox7bYjM+VhnZ1V22ivIDjAsKr00H+XQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"@bufbuild/protobuf": "^1.10.0"
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
}
},
➕(frontend) install track-processors-js from LiveKit Recommended dependency to process video tracks, to add a virtual background, or a blurring effect. Created and maintained by the core LiveKit's team. Please note, few issues are known. track-processors-js relies on MediaPipe (by Google), which is not supported on Firefox … Quick-win to ship a first draft.
2024-09-16 18:13:04 +02:00
"node_modules/@livekit/track-processors": {
⬆️(frontend) bump LiveKit-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-16 18:42:31 +01:00
"version": "0.3.3",
"resolved": "https://registry.npmjs.org/@livekit/track-processors/-/track-processors-0.3.3.tgz",
"integrity": "sha512-C5mBWe34ie0pfhCf9zAD65D26ZytzW/xGrj8Zc1BGh5kLISFDVQlefO78LZWw9K5saTamk60O4fzSCKqWMPMLA==",
"license": "Apache-2.0",
➕(frontend) install track-processors-js from LiveKit Recommended dependency to process video tracks, to add a virtual background, or a blurring effect. Created and maintained by the core LiveKit's team. Please note, few issues are known. track-processors-js relies on MediaPipe (by Google), which is not supported on Firefox … Quick-win to ship a first draft.
2024-09-16 18:13:04 +02:00
"dependencies": {
"@mediapipe/holistic": "0.5.1675471629",
"@mediapipe/tasks-vision": "0.10.9"
},
"peerDependencies": {
"livekit-client": "^1.12.0 || ^2.1.0"
}
},
"node_modules/@mediapipe/holistic": {
"version": "0.5.1675471629",
"resolved": "https://registry.npmjs.org/@mediapipe/holistic/-/holistic-0.5.1675471629.tgz",
"integrity": "sha512-qY+cxtDeSOvVtevrLgnodiwXYaAtPi7dHZtNv/bUCGEjFicAOYtMmrZSqMmbPkTB2+4jLnPF1vgshkAqQRSYAw=="
},
"node_modules/@mediapipe/tasks-vision": {
"version": "0.10.9",
"resolved": "https://registry.npmjs.org/@mediapipe/tasks-vision/-/tasks-vision-0.10.9.tgz",
"integrity": "sha512-/gFguyJm1ng4Qr7VVH2vKO+zZcQd8wc3YafUfvBuYFX0Y5+CvrV+VNPEVkl5W/gUZF5KNKNZAiaHPULGPCIjyQ=="
},
✨(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
"node_modules/@nodelib/fs.scandir": {
"version": "2.1.5",
"resolved": "https://registry.npmjs.org/@nodelib/fs.scandir/-/fs.scandir-2.1.5.tgz",
"integrity": "sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==",
"dev": true,
"dependencies": {
"@nodelib/fs.stat": "2.0.5",
"run-parallel": "^1.1.9"
},
"engines": {
"node": ">= 8"
}
},
"node_modules/@nodelib/fs.stat": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/@nodelib/fs.stat/-/fs.stat-2.0.5.tgz",
"integrity": "sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==",
"dev": true,
"engines": {
"node": ">= 8"
}
},
"node_modules/@nodelib/fs.walk": {
"version": "1.2.8",
"resolved": "https://registry.npmjs.org/@nodelib/fs.walk/-/fs.walk-1.2.8.tgz",
"integrity": "sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==",
"dev": true,
"dependencies": {
"@nodelib/fs.scandir": "2.1.5",
"fastq": "^1.6.0"
},
"engines": {
"node": ">= 8"
}
},
♻️(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
"node_modules/@pandacss/config": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.51.1",
"resolved": "https://registry.npmjs.org/@pandacss/config/-/config-0.51.1.tgz",
"integrity": "sha512-ncERWlnXAY+D4BC9TaMTD7xL3SLn8+2ky0RZgVbXEJCM5ivnuCCVEVahKWz/9m7nfQ06ZWg3VLY3LR/gs3g+cQ==",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"dev": true,
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@pandacss/logger": "0.51.1",
"@pandacss/preset-base": "0.51.1",
"@pandacss/preset-panda": "0.51.1",
"@pandacss/shared": "0.51.1",
"@pandacss/types": "0.51.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
"bundle-n-require": "1.1.1",
"escalade": "3.1.2",
"merge-anything": "5.1.7",
"microdiff": "1.3.2",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"typescript": "5.6.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
}
},
"node_modules/@pandacss/config/node_modules/typescript": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "5.6.2",
"resolved": "https://registry.npmjs.org/typescript/-/typescript-5.6.2.tgz",
"integrity": "sha512-NW8ByodCSNCwZeghjN3o+JX5OFH0Ojg6sadjEKY4huZ52TqbJTJnDo5+Tw98lSy63NZvi4n+ez5m2u5d4PkZyw==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "Apache-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
"bin": {
"tsc": "bin/tsc",
"tsserver": "bin/tsserver"
},
"engines": {
"node": ">=14.17"
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
}
},
♻️(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
"node_modules/@pandacss/core": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.51.1",
"resolved": "https://registry.npmjs.org/@pandacss/core/-/core-0.51.1.tgz",
"integrity": "sha512-XJYKAGje9XJnc4Mgtc3ZPQbYUmJC6kLWcLtsHbhr8v0pLoZetcCet9Hbs1yt8EERwIxkStpKNff51N1IA6uhgA==",
✨(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
"dev": true,
♻️(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
"dependencies": {
"@csstools/postcss-cascade-layers": "4.0.6",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@pandacss/is-valid-prop": "^0.51.1",
"@pandacss/logger": "0.51.1",
"@pandacss/shared": "0.51.1",
"@pandacss/token-dictionary": "0.51.1",
"@pandacss/types": "0.51.1",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"browserslist": "4.23.3",
♻️(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
"hookable": "5.5.3",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"lightningcss": "1.25.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
"lodash.merge": "4.6.2",
"outdent": "0.8.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"postcss": "8.4.49",
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"postcss-discard-duplicates": "7.0.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
"postcss-discard-empty": "7.0.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"postcss-merge-rules": "7.0.4",
"postcss-minify-selectors": "7.0.4",
♻️(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-nested": "6.0.1",
"postcss-normalize-whitespace": "7.0.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"postcss-selector-parser": "6.1.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
"ts-pattern": "5.0.8"
}
},
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"node_modules/@pandacss/core/node_modules/postcss": {
"version": "8.4.49",
"resolved": "https://registry.npmjs.org/postcss/-/postcss-8.4.49.tgz",
"integrity": "sha512-OCVPnIObs4N29kxTjzLfUryOkvZEq+pf8jTF0lg8E7uETuWHA+v7j3c/xJmiqpX450191LlmZfUKkXxkTry7nA==",
"dev": true,
"funding": [
{
"type": "opencollective",
"url": "https://opencollective.com/postcss/"
},
{
"type": "tidelift",
"url": "https://tidelift.com/funding/github/npm/postcss"
},
{
"type": "github",
"url": "https://github.com/sponsors/ai"
}
],
"license": "MIT",
"dependencies": {
"nanoid": "^3.3.7",
"picocolors": "^1.1.1",
"source-map-js": "^1.2.1"
},
"engines": {
"node": "^10 || ^12 || >=14"
}
},
♻️(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
"node_modules/@pandacss/dev": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.51.1",
"resolved": "https://registry.npmjs.org/@pandacss/dev/-/dev-0.51.1.tgz",
"integrity": "sha512-CSZur9PwEVTJuZ8MabScei7bt3c1WLoQ15L8umiSij1Us7AHsLLnIjed5Gzw7r7gfIWiztGeY9bniNYRo8qg1w==",
✨(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
"dev": true,
♻️(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
"dependencies": {
"@clack/prompts": "0.7.0",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@pandacss/config": "0.51.1",
"@pandacss/logger": "0.51.1",
"@pandacss/node": "0.51.1",
"@pandacss/postcss": "0.51.1",
"@pandacss/preset-panda": "0.51.1",
"@pandacss/shared": "0.51.1",
"@pandacss/token-dictionary": "0.51.1",
"@pandacss/types": "0.51.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
"cac": "6.7.14"
},
"bin": {
"panda": "bin.js",
"pandacss": "bin.js"
}
✨(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) 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
"node_modules/@pandacss/extractor": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.51.1",
"resolved": "https://registry.npmjs.org/@pandacss/extractor/-/extractor-0.51.1.tgz",
"integrity": "sha512-Ke/RKmi0fVHUHJxWmGGcSYAwwsFf1q/p8kRa+IqQAT3mt9j8jXDrHWns0PI6J+sh6oZr0bCOvmpID9BO0ZPmMA==",
✨(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
"dev": true,
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@pandacss/shared": "0.51.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
"ts-evaluator": "1.2.0",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"ts-morph": "24.0.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
}
✨(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) 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
"node_modules/@pandacss/generator": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.51.1",
"resolved": "https://registry.npmjs.org/@pandacss/generator/-/generator-0.51.1.tgz",
"integrity": "sha512-Q1oePSwtSBgfbaCEUwGT8rugtpKkPb+UVuUeiSPJNDiMGMyHOYeKsPPJ+U7SNg5/FBgaYg3kLFN5dKGW+4mm8A==",
✨(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
"dev": true,
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@pandacss/core": "0.51.1",
"@pandacss/is-valid-prop": "^0.51.1",
"@pandacss/logger": "0.51.1",
"@pandacss/shared": "0.51.1",
"@pandacss/token-dictionary": "0.51.1",
"@pandacss/types": "0.51.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
"javascript-stringify": "2.1.0",
"outdent": " ^0.8.0",
"pluralize": "8.0.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"postcss": "8.4.49",
♻️(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
"ts-pattern": "5.0.8"
}
},
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"node_modules/@pandacss/generator/node_modules/postcss": {
"version": "8.4.49",
"resolved": "https://registry.npmjs.org/postcss/-/postcss-8.4.49.tgz",
"integrity": "sha512-OCVPnIObs4N29kxTjzLfUryOkvZEq+pf8jTF0lg8E7uETuWHA+v7j3c/xJmiqpX450191LlmZfUKkXxkTry7nA==",
"dev": true,
"funding": [
{
"type": "opencollective",
"url": "https://opencollective.com/postcss/"
},
{
"type": "tidelift",
"url": "https://tidelift.com/funding/github/npm/postcss"
},
{
"type": "github",
"url": "https://github.com/sponsors/ai"
}
],
"license": "MIT",
"dependencies": {
"nanoid": "^3.3.7",
"picocolors": "^1.1.1",
"source-map-js": "^1.2.1"
},
"engines": {
"node": "^10 || ^12 || >=14"
}
},
♻️(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
"node_modules/@pandacss/is-valid-prop": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.51.1",
"resolved": "https://registry.npmjs.org/@pandacss/is-valid-prop/-/is-valid-prop-0.51.1.tgz",
"integrity": "sha512-Tcp90KEhW3AuHyaI5Ndsk/s92/F0E2WReS+7eS3VUP3cUbajU4F56G6MZCp0nW+QgFdfUCMBO17rgtTxhKqdOg==",
♻️(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": true
✨(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) 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
"node_modules/@pandacss/logger": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.51.1",
"resolved": "https://registry.npmjs.org/@pandacss/logger/-/logger-0.51.1.tgz",
"integrity": "sha512-YgfS6q6BXCOBbskIOXmDa8bJkJ61NKgoJlUucs9/A1OJwPGzWIFl8gXVcJF+sLHTXAIFMT9MhaHJVOcHPNGJ0Q==",
✨(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
"dev": true,
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@pandacss/types": "0.51.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
"kleur": "4.1.5"
}
✨(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) 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
"node_modules/@pandacss/node": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.51.1",
"resolved": "https://registry.npmjs.org/@pandacss/node/-/node-0.51.1.tgz",
"integrity": "sha512-9biA5rXYWCfL7u4Jw9Hmepqyt+sDAGUh6rw3njM2k3DhtI9hTHeGvdCbrFaaYfDehvRaGHUEAPwW0DJTeOzXsg==",
"dev": true,
"dependencies": {
"@pandacss/config": "0.51.1",
"@pandacss/core": "0.51.1",
"@pandacss/generator": "0.51.1",
"@pandacss/logger": "0.51.1",
"@pandacss/parser": "0.51.1",
"@pandacss/reporter": "0.51.1",
"@pandacss/shared": "0.51.1",
"@pandacss/token-dictionary": "0.51.1",
"@pandacss/types": "0.51.1",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"browserslist": "4.23.3",
♻️(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
"chokidar": "3.6.0",
"fast-glob": "3.3.2",
"fs-extra": "11.2.0",
"glob-parent": "6.0.2",
"is-glob": "4.0.3",
"lodash.merge": "4.6.2",
"look-it-up": "2.1.0",
"outdent": " ^0.8.0",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"package-manager-detector": "0.1.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
"perfect-debounce": "1.0.0",
"pkg-types": "1.0.3",
"pluralize": "8.0.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"postcss": "8.4.49",
♻️(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
"prettier": "3.2.5",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"ts-morph": "24.0.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
"ts-pattern": "5.0.8",
"tsconfck": "3.0.2"
}
},
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"node_modules/@pandacss/node/node_modules/postcss": {
"version": "8.4.49",
"resolved": "https://registry.npmjs.org/postcss/-/postcss-8.4.49.tgz",
"integrity": "sha512-OCVPnIObs4N29kxTjzLfUryOkvZEq+pf8jTF0lg8E7uETuWHA+v7j3c/xJmiqpX450191LlmZfUKkXxkTry7nA==",
"dev": true,
"funding": [
{
"type": "opencollective",
"url": "https://opencollective.com/postcss/"
},
{
"type": "tidelift",
"url": "https://tidelift.com/funding/github/npm/postcss"
},
{
"type": "github",
"url": "https://github.com/sponsors/ai"
}
],
"license": "MIT",
"dependencies": {
"nanoid": "^3.3.7",
"picocolors": "^1.1.1",
"source-map-js": "^1.2.1"
},
"engines": {
"node": "^10 || ^12 || >=14"
}
},
🔧(frontend) configure Prettier and ESLint Set up Prettier with minimal configuration. Installed eslint-config-prettier to prevent conflicts between ESLint and Prettier.
2024-08-06 11:06:16 +02:00
"node_modules/@pandacss/node/node_modules/prettier": {
"version": "3.2.5",
"resolved": "https://registry.npmjs.org/prettier/-/prettier-3.2.5.tgz",
"integrity": "sha512-3/GWa9aOC0YeD7LUfvOG2NiDyhOWRvt1k+rcKhOuYnMY24iiCphgneUfJDyFXd6rZCAnuLBv6UeAULtrhT/F4A==",
"dev": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
🔧(frontend) configure Prettier and ESLint Set up Prettier with minimal configuration. Installed eslint-config-prettier to prevent conflicts between ESLint and Prettier.
2024-08-06 11:06:16 +02:00
"bin": {
"prettier": "bin/prettier.cjs"
},
"engines": {
"node": ">=14"
},
"funding": {
"url": "https://github.com/prettier/prettier?sponsor=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
"node_modules/@pandacss/parser": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.51.1",
"resolved": "https://registry.npmjs.org/@pandacss/parser/-/parser-0.51.1.tgz",
"integrity": "sha512-tkCUL3B+hkCqNOD/imSQJUz1WlfkRTYMhk9vmjs5YbR0OaK3ufCw8rQH3QEgOcGpMJUiIoq3jIkWbfhuDxrjKQ==",
✨(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
"dev": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@pandacss/config": "^0.51.1",
"@pandacss/core": "^0.51.1",
"@pandacss/extractor": "0.51.1",
"@pandacss/logger": "0.51.1",
"@pandacss/shared": "0.51.1",
"@pandacss/types": "0.51.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
"@vue/compiler-sfc": "3.4.19",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"magic-string": "0.30.17",
"ts-morph": "24.0.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
"ts-pattern": "5.0.8"
}
},
"node_modules/@pandacss/postcss": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.51.1",
"resolved": "https://registry.npmjs.org/@pandacss/postcss/-/postcss-0.51.1.tgz",
"integrity": "sha512-NOvqqur/VW8qQegWXB2CqDn56Nkreyrk9yuRzwgwad1cthr8oDUS85y7D/dDT3tFloFYG0GPtQ6zsOSs1Cnkbw==",
✨(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
"dev": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@pandacss/node": "0.51.1",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"postcss": "8.4.49"
✨(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) update js dependencies
2025-01-20 21:47:59 +00:00
"node_modules/@pandacss/postcss/node_modules/postcss": {
"version": "8.4.49",
"resolved": "https://registry.npmjs.org/postcss/-/postcss-8.4.49.tgz",
"integrity": "sha512-OCVPnIObs4N29kxTjzLfUryOkvZEq+pf8jTF0lg8E7uETuWHA+v7j3c/xJmiqpX450191LlmZfUKkXxkTry7nA==",
"dev": true,
"funding": [
{
"type": "opencollective",
"url": "https://opencollective.com/postcss/"
},
{
"type": "tidelift",
"url": "https://tidelift.com/funding/github/npm/postcss"
},
{
"type": "github",
"url": "https://github.com/sponsors/ai"
}
],
"license": "MIT",
"dependencies": {
"nanoid": "^3.3.7",
"picocolors": "^1.1.1",
"source-map-js": "^1.2.1"
},
"engines": {
"node": "^10 || ^12 || >=14"
}
},
♻️(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
"node_modules/@pandacss/preset-base": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.51.1",
"resolved": "https://registry.npmjs.org/@pandacss/preset-base/-/preset-base-0.51.1.tgz",
"integrity": "sha512-w5cq1VEq1rYOTgg7sfM2kQu+R09Vs6vGmS5rg9CyNHSuuBwxfo2WbEtnILpKR/dcU5HmFYQz6Mt0qYU3uEKenQ==",
✨(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
"dev": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@pandacss/types": "0.51.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
}
},
♻️(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
"node_modules/@pandacss/preset-panda": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.51.1",
"resolved": "https://registry.npmjs.org/@pandacss/preset-panda/-/preset-panda-0.51.1.tgz",
"integrity": "sha512-K5j0cHbPqmWp0v2a4z1B1eG21c4TFeIG7aHZGPL/p4y6s+2D14OhSRo9WZWGXcx9PqcgFAt9wEk9z9j2OXhtQw==",
"dependencies": {
"@pandacss/types": "0.51.1"
}
},
"node_modules/@pandacss/reporter": {
"version": "0.51.1",
"resolved": "https://registry.npmjs.org/@pandacss/reporter/-/reporter-0.51.1.tgz",
"integrity": "sha512-T1IxsKwCA+Ud23ocr1dS1wCpfT3yW1QXPhSFiR75BvyYYM7BXKzxG/mTEsSnLs+rwPc0JFbL7NsYuZQJzLtXYg==",
"dev": true,
✨(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": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@pandacss/core": "0.51.1",
"@pandacss/generator": "0.51.1",
"@pandacss/logger": "0.51.1",
"@pandacss/shared": "0.51.1",
"@pandacss/types": "0.51.1",
"table": "6.9.0",
"wordwrapjs": "5.1.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
}
},
♻️(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
"node_modules/@pandacss/shared": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.51.1",
"resolved": "https://registry.npmjs.org/@pandacss/shared/-/shared-0.51.1.tgz",
"integrity": "sha512-jlzRIqY1FxZVBqaM7D9CIqzRyk0EJMu4m/doW/7X+6EBYuWtwhurba88C3DEZN4sE18+CbEe5Ece2azFVBFcNg==",
✨(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
"dev": true
},
♻️(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
"node_modules/@pandacss/token-dictionary": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.51.1",
"resolved": "https://registry.npmjs.org/@pandacss/token-dictionary/-/token-dictionary-0.51.1.tgz",
"integrity": "sha512-fBfW3/6xZ+UvSMooRHJNVSl9H0BYce5PuNm5wOq1WpTxIyR4TITFMOy35GMPqotWCcmZppBRw22on3IoGhxoog==",
🔧(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
"dev": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@pandacss/logger": "^0.51.1",
"@pandacss/shared": "0.51.1",
"@pandacss/types": "0.51.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
"ts-pattern": "5.0.8"
🔧(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
}
},
♻️(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
"node_modules/@pandacss/types": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.51.1",
"resolved": "https://registry.npmjs.org/@pandacss/types/-/types-0.51.1.tgz",
"integrity": "sha512-yy8wr6LjdwRZUaid37CE/TxJyxkD1cyTj8OQfwSFxwfxSLsupzX00/IoNw4OJyfm/inTCmcj7DfSVmRrAsi4Bw=="
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
},
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"node_modules/@react-aria/autocomplete": {
"version": "3.0.0-alpha.37",
"resolved": "https://registry.npmjs.org/@react-aria/autocomplete/-/autocomplete-3.0.0-alpha.37.tgz",
"integrity": "sha512-a7awFG3hshJ/kX7Qti/cJAKOG0XU5F/XW6fQffKGfEge7PmiWIvaLTrT5her79/v8v/bRBykIkpEgDCFE7WGzg==",
"license": "Apache-2.0",
"dependencies": {
"@react-aria/combobox": "^3.11.1",
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
"@react-aria/listbox": "^3.14.0",
"@react-aria/searchfield": "^3.8.0",
"@react-aria/textfield": "^3.16.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/autocomplete": "3.0.0-alpha.0",
"@react-stately/combobox": "^3.10.2",
"@react-types/autocomplete": "3.0.0-alpha.28",
"@react-types/button": "^3.10.2",
"@react-types/shared": "^3.27.0",
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
"node_modules/@react-aria/breadcrumbs": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.5.20",
"resolved": "https://registry.npmjs.org/@react-aria/breadcrumbs/-/breadcrumbs-3.5.20.tgz",
"integrity": "sha512-xqVSSDPpQuUFpJyIXMQv8L7zumk5CeGX7qTzo4XRvqm5T9qnNAX4XpYEMdktnLrQRY/OemCBScbx7SEwr0B3Kg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/i18n": "^3.12.5",
"@react-aria/link": "^3.7.8",
"@react-aria/utils": "^3.27.0",
"@react-types/breadcrumbs": "^3.7.10",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
♻️(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
"node_modules/@react-aria/button": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.11.1",
"resolved": "https://registry.npmjs.org/@react-aria/button/-/button-3.11.1.tgz",
"integrity": "sha512-NSs2HxHSSPSuYy5bN+PMJzsCNDVsbm1fZ/nrWM2WWWHTBrx9OqyrEXZVV9ebzQCN9q0nzhwpf6D42zHIivWtJA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/interactions": "^3.23.0",
"@react-aria/toolbar": "3.0.0-beta.12",
"@react-aria/utils": "^3.27.0",
"@react-stately/toggle": "^3.8.1",
"@react-types/button": "^3.10.2",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
♻️(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
"node_modules/@react-aria/calendar": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.7.0",
"resolved": "https://registry.npmjs.org/@react-aria/calendar/-/calendar-3.7.0.tgz",
"integrity": "sha512-9YUbgcox7cQgvZfQtL2BLLRsIuX4mJeclk9HkFoOsAu3RGO5HNsteah8FV54W8BMjm/bNRXIPUxtjTTP+1L6jg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@internationalized/date": "^3.7.0",
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-aria/live-announcer": "^3.4.1",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/utils": "^3.27.0",
"@react-stately/calendar": "^3.7.0",
"@react-types/button": "^3.10.2",
"@react-types/calendar": "^3.6.0",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/checkbox": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.15.1",
"resolved": "https://registry.npmjs.org/@react-aria/checkbox/-/checkbox-3.15.1.tgz",
"integrity": "sha512-ETgsMDZ0IZzRXy/OVlGkazm8T+PcMHoTvsxp0c+U82c8iqdITA+VJ615eBPOQh6OkkYIIn4cRn/e+69RmGzXng==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/form": "^3.0.12",
"@react-aria/interactions": "^3.23.0",
"@react-aria/label": "^3.7.14",
"@react-aria/toggle": "^3.10.11",
"@react-aria/utils": "^3.27.0",
"@react-stately/checkbox": "^3.6.11",
"@react-stately/form": "^3.1.1",
"@react-stately/toggle": "^3.8.1",
"@react-types/checkbox": "^3.9.1",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/@react-aria/collections": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.0.0-alpha.7",
"resolved": "https://registry.npmjs.org/@react-aria/collections/-/collections-3.0.0-alpha.7.tgz",
"integrity": "sha512-JR2Ro33Chlf26NM12zJsK+MOs5/k+PQallT5+4YawndYmbxqlDLADcoFdcORJqh0pKf9OnluWtANobCkQGd0aQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-aria/ssr": "^3.9.7",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/utils": "^3.27.0",
"@react-types/shared": "^3.27.0",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"@swc/helpers": "^0.5.0",
"use-sync-external-store": "^1.2.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/color": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/@react-aria/color/-/color-3.0.3.tgz",
"integrity": "sha512-DDVma2107VHBfSuEnnmy+KJvXvxEXWSAooii2vlHHmQNb5x4rv4YTk+dP5GZl/7MgT8OgPTB9UHoC83bXFMDRA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
"@react-aria/numberfield": "^3.11.10",
"@react-aria/slider": "^3.7.15",
"@react-aria/spinbutton": "^3.6.11",
"@react-aria/textfield": "^3.16.0",
"@react-aria/utils": "^3.27.0",
"@react-aria/visually-hidden": "^3.8.19",
"@react-stately/color": "^3.8.2",
"@react-stately/form": "^3.1.1",
"@react-types/color": "^3.0.2",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/combobox": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.11.1",
"resolved": "https://registry.npmjs.org/@react-aria/combobox/-/combobox-3.11.1.tgz",
"integrity": "sha512-TTNbGhUuqxzPcJzd6hufOxuHzX0UARkw+0bl+TuCwNPQnqrcPf20EoOZvd3MHZwGq6GCP4QV+qo0uGx83RpUvA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/i18n": "^3.12.5",
"@react-aria/listbox": "^3.14.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-aria/live-announcer": "^3.4.1",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/menu": "^3.17.0",
"@react-aria/overlays": "^3.25.0",
"@react-aria/selection": "^3.22.0",
"@react-aria/textfield": "^3.16.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/collections": "^3.12.1",
"@react-stately/combobox": "^3.10.2",
"@react-stately/form": "^3.1.1",
"@react-types/button": "^3.10.2",
"@react-types/combobox": "^3.13.2",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/datepicker": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.13.0",
"resolved": "https://registry.npmjs.org/@react-aria/datepicker/-/datepicker-3.13.0.tgz",
"integrity": "sha512-TmJan65P3Vk7VDBNW5rH9Z25cAn0vk8TEtaP3boCs8wJFE+HbEuB8EqLxBFu47khtuKTEqDP3dTlUh2Vt/f7Xw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@internationalized/date": "^3.7.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@internationalized/number": "^3.6.0",
"@internationalized/string": "^3.2.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/form": "^3.0.12",
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
"@react-aria/label": "^3.7.14",
"@react-aria/spinbutton": "^3.6.11",
"@react-aria/utils": "^3.27.0",
"@react-stately/datepicker": "^3.12.0",
"@react-stately/form": "^3.1.1",
"@react-types/button": "^3.10.2",
"@react-types/calendar": "^3.6.0",
"@react-types/datepicker": "^3.10.0",
"@react-types/dialog": "^3.5.15",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/dialog": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.5.21",
"resolved": "https://registry.npmjs.org/@react-aria/dialog/-/dialog-3.5.21.tgz",
"integrity": "sha512-tBsn9swBhcptJ9QIm0+ur0PVR799N6qmGguva3rUdd+gfitknFScyT08d7AoMr9AbXYdJ+2R9XNSZ3H3uIWQMw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/overlays": "^3.25.0",
"@react-aria/utils": "^3.27.0",
"@react-types/dialog": "^3.5.15",
"@react-types/shared": "^3.27.0",
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1"
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
}
},
"node_modules/@react-aria/disclosure": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/@react-aria/disclosure/-/disclosure-3.0.1.tgz",
"integrity": "sha512-rNH8RFcePoAQizcqB7KuHbBOr7sPsysFKCUwbVSOXLPgvCfXKafIhjgFJVqekfsbn5zWvkcTupnzGVJj/F9p+g==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
"@react-aria/ssr": "^3.9.7",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/utils": "^3.27.0",
"@react-stately/disclosure": "^3.0.1",
"@react-types/button": "^3.10.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/dnd": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.8.1",
"resolved": "https://registry.npmjs.org/@react-aria/dnd/-/dnd-3.8.1.tgz",
"integrity": "sha512-FoXYQ4z33E9YBzIGRJM1B1oZep6CvEWgXvjCZGURatjr3qG7vf95mOqA5kVd9bjLL7QK4w0ujJWEBfog3WmufA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
"@internationalized/string": "^3.2.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-aria/live-announcer": "^3.4.1",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/overlays": "^3.25.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/dnd": "^3.5.1",
"@react-types/button": "^3.10.2",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/focus": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.19.1",
"resolved": "https://registry.npmjs.org/@react-aria/focus/-/focus-3.19.1.tgz",
"integrity": "sha512-bix9Bu1Ue7RPcYmjwcjhB14BMu2qzfJ3tMQLqDc9pweJA66nOw8DThy3IfVr8Z7j2PHktOLf9kcbiZpydKHqzg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/interactions": "^3.23.0",
"@react-aria/utils": "^3.27.0",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0",
"clsx": "^2.0.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/form": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.0.12",
"resolved": "https://registry.npmjs.org/@react-aria/form/-/form-3.0.12.tgz",
"integrity": "sha512-8uvPYEd3GDyGt5NRJIzdWW1Ry5HLZq37vzRZKUW8alZ2upFMH3KJJG55L9GP59KiF6zBrYBebvI/YK1Ye1PE1g==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/interactions": "^3.23.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/form": "^3.1.1",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/grid": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.11.1",
"resolved": "https://registry.npmjs.org/@react-aria/grid/-/grid-3.11.1.tgz",
"integrity": "sha512-Wg8m68RtNWfkhP3Qjrrsl1q1et8QCjXPMRsYgKBahYRS0kq2MDcQ+UBdG1fiCQn/MfNImhTUGVeQX276dy1lww==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-aria/live-announcer": "^3.4.1",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/selection": "^3.22.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/collections": "^3.12.1",
"@react-stately/grid": "^3.10.1",
"@react-stately/selection": "^3.19.0",
"@react-types/checkbox": "^3.9.1",
"@react-types/grid": "^3.2.11",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/gridlist": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.10.1",
"resolved": "https://registry.npmjs.org/@react-aria/gridlist/-/gridlist-3.10.1.tgz",
"integrity": "sha512-11FlupBg5C9ehs7R6OjqMPWEOLK/4IuSrq7D1xU+Hnm7ZYI/KKcCXvNMjMmnOz/gGzOmfgVwz5PIKaY9aZarEg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/grid": "^3.11.1",
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
"@react-aria/selection": "^3.22.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/collections": "^3.12.1",
"@react-stately/list": "^3.11.2",
"@react-stately/tree": "^3.8.7",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/i18n": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.12.5",
"resolved": "https://registry.npmjs.org/@react-aria/i18n/-/i18n-3.12.5.tgz",
"integrity": "sha512-ooeop2pTG94PuaHoN2OTk2hpkqVuoqgEYxRvnc1t7DVAtsskfhS/gVOTqyWGsxvwAvRi7m/CnDu6FYdeQ/bK5w==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@internationalized/date": "^3.7.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@internationalized/message": "^3.1.6",
"@internationalized/number": "^3.6.0",
"@internationalized/string": "^3.2.5",
"@react-aria/ssr": "^3.9.7",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/utils": "^3.27.0",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/interactions": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.23.0",
"resolved": "https://registry.npmjs.org/@react-aria/interactions/-/interactions-3.23.0.tgz",
"integrity": "sha512-0qR1atBIWrb7FzQ+Tmr3s8uH5mQdyRH78n0krYaG8tng9+u1JlSi8DGRSaC9ezKyNB84m7vHT207xnHXGeJ3Fg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-aria/ssr": "^3.9.7",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/utils": "^3.27.0",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/label": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.7.14",
"resolved": "https://registry.npmjs.org/@react-aria/label/-/label-3.7.14.tgz",
"integrity": "sha512-EN1Md2YvcC4sMqBoggsGYUEGlTNqUfJZWzduSt29fbQp1rKU2KlybTe+TWxKq/r2fFd+4JsRXxMeJiwB3w2AQA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/utils": "^3.27.0",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
➕(frontend) install react-toast in beta Absolutely needed some toasts to handle in app notifications, or feedbacks. React Aria is working on it, and has released a first beta. No component is available, only hooks.
2024-09-09 18:54:57 +02:00
"node_modules/@react-aria/landmark": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.0.0-beta.18",
"resolved": "https://registry.npmjs.org/@react-aria/landmark/-/landmark-3.0.0-beta.18.tgz",
"integrity": "sha512-jFtWL7TYZrKucWNDx6ppUkGSqS2itkjhyLo9MIFqEg2mi4Lc2EoUjI/Gw9xMT+IJgebTcdQeXJpPskspl3Pojg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
➕(frontend) install react-toast in beta Absolutely needed some toasts to handle in app notifications, or feedbacks. React Aria is working on it, and has released a first beta. No component is available, only hooks.
2024-09-09 18:54:57 +02:00
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/utils": "^3.27.0",
"@react-types/shared": "^3.27.0",
➕(frontend) install react-toast in beta Absolutely needed some toasts to handle in app notifications, or feedbacks. React Aria is working on it, and has released a first beta. No component is available, only hooks.
2024-09-09 18:54:57 +02:00
"@swc/helpers": "^0.5.0",
"use-sync-external-store": "^1.2.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1"
➕(frontend) install react-toast in beta Absolutely needed some toasts to handle in app notifications, or feedbacks. React Aria is working on it, and has released a first beta. No component is available, only hooks.
2024-09-09 18:54:57 +02:00
}
},
♻️(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
"node_modules/@react-aria/link": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.7.8",
"resolved": "https://registry.npmjs.org/@react-aria/link/-/link-3.7.8.tgz",
"integrity": "sha512-oiXUPQLZmf9Q9Xehb/sG1QRxfo28NFKdh9w+unD12sHI6NdLMETl5MA4CYyTgI0dfMtTjtfrF68GCnWfc7JvXQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/interactions": "^3.23.0",
"@react-aria/utils": "^3.27.0",
"@react-types/link": "^3.5.10",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/listbox": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.14.0",
"resolved": "https://registry.npmjs.org/@react-aria/listbox/-/listbox-3.14.0.tgz",
"integrity": "sha512-pyVbKavh8N8iyiwOx6I3JIcICvAzFXkKSFni1yarfgngJsJV3KSyOkzLomOfN9UhbjcV4sX61/fccwJuvlurlA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/interactions": "^3.23.0",
"@react-aria/label": "^3.7.14",
"@react-aria/selection": "^3.22.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/collections": "^3.12.1",
"@react-stately/list": "^3.11.2",
"@react-types/listbox": "^3.5.4",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/live-announcer": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "3.4.1",
"resolved": "https://registry.npmjs.org/@react-aria/live-announcer/-/live-announcer-3.4.1.tgz",
"integrity": "sha512-4X2mcxgqLvvkqxv2l1n00jTzUxxe0kkLiapBGH1LHX/CxA1oQcHDqv8etJ2ZOwmS/MSBBiWnv3DwYHDOF6ubig==",
"license": "Apache-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
"dependencies": {
"@swc/helpers": "^0.5.0"
}
},
"node_modules/@react-aria/menu": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.17.0",
"resolved": "https://registry.npmjs.org/@react-aria/menu/-/menu-3.17.0.tgz",
"integrity": "sha512-aiFvSv3G1YvPC0klJQ/9quB05xIDZzJ5Lt6/CykP0UwGK5i8GCqm6/cyFLwEXsS5ooUPxS3bqmdOsgdADSSgqg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
"@react-aria/overlays": "^3.25.0",
"@react-aria/selection": "^3.22.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/collections": "^3.12.1",
"@react-stately/menu": "^3.9.1",
"@react-stately/selection": "^3.19.0",
"@react-stately/tree": "^3.8.7",
"@react-types/button": "^3.10.2",
"@react-types/menu": "^3.9.14",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/meter": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.4.19",
"resolved": "https://registry.npmjs.org/@react-aria/meter/-/meter-3.4.19.tgz",
"integrity": "sha512-IIA+gTHrNVbMuBgcqdGLEKd/ZiKM2hOUqS6uztbT15dwPJTmtfJiTWA2872PiY52p+gqPSanZuTc2TXYJa+rew==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/progress": "^3.4.19",
"@react-types/meter": "^3.4.6",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/numberfield": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.11.10",
"resolved": "https://registry.npmjs.org/@react-aria/numberfield/-/numberfield-3.11.10.tgz",
"integrity": "sha512-bYbTfO9NbAKMFOfEGGs+lvlxk0I9L0lU3WD2PFQZWdaoBz9TCkL+vK0fJk1zsuKaVjeGsmHP9VesBPRmaP0MiA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
"@react-aria/spinbutton": "^3.6.11",
"@react-aria/textfield": "^3.16.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/form": "^3.1.1",
"@react-stately/numberfield": "^3.9.9",
"@react-types/button": "^3.10.2",
"@react-types/numberfield": "^3.8.8",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/overlays": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.25.0",
"resolved": "https://registry.npmjs.org/@react-aria/overlays/-/overlays-3.25.0.tgz",
"integrity": "sha512-UEqJJ4duowrD1JvwXpPZreBuK79pbyNjNxFUVpFSskpGEJe3oCWwsSDKz7P1O7xbx5OYp+rDiY8fk/sE5rkaKw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-aria/ssr": "^3.9.7",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/utils": "^3.27.0",
"@react-aria/visually-hidden": "^3.8.19",
"@react-stately/overlays": "^3.6.13",
"@react-types/button": "^3.10.2",
"@react-types/overlays": "^3.8.12",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/progress": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.4.19",
"resolved": "https://registry.npmjs.org/@react-aria/progress/-/progress-3.4.19.tgz",
"integrity": "sha512-5HHnBJHqEUuY+dYsjIZDYsENeKr49VCuxeaDZ0OSahbOlloIOB1baCo/6jLBv1O1rwrAzZ2gCCPcVGed/cjrcw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/i18n": "^3.12.5",
"@react-aria/label": "^3.7.14",
"@react-aria/utils": "^3.27.0",
"@react-types/progress": "^3.5.9",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/radio": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.10.11",
"resolved": "https://registry.npmjs.org/@react-aria/radio/-/radio-3.10.11.tgz",
"integrity": "sha512-R150HsBFPr1jLMShI4aBM8heCa1k6h0KEvnFRfTAOBu+B9hMSZOPB+d6GQOwGPysNlbset90Kej8G15FGHjqiA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/form": "^3.0.12",
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
"@react-aria/label": "^3.7.14",
"@react-aria/utils": "^3.27.0",
"@react-stately/radio": "^3.10.10",
"@react-types/radio": "^3.8.6",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/searchfield": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.8.0",
"resolved": "https://registry.npmjs.org/@react-aria/searchfield/-/searchfield-3.8.0.tgz",
"integrity": "sha512-AaZuH9YIWlMyE1m7cSjHCfOuQmlWN+w8HVW32TxeGGGL1kJsYAlSYWYHUyYFIKh245kq/m5zUxAxmw5Ygmnx5w==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/i18n": "^3.12.5",
"@react-aria/textfield": "^3.16.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/searchfield": "^3.5.9",
"@react-types/button": "^3.10.2",
"@react-types/searchfield": "^3.5.11",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/select": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.15.1",
"resolved": "https://registry.npmjs.org/@react-aria/select/-/select-3.15.1.tgz",
"integrity": "sha512-FOtY1tuHt0YTHwOEy/sf7LEIL+Nnkho3wJmfpWQuTxsvMCF7UJdQPYPd6/jGCcCdiqW7H4iqyjUkSp6nk/XRWQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/form": "^3.0.12",
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
"@react-aria/label": "^3.7.14",
"@react-aria/listbox": "^3.14.0",
"@react-aria/menu": "^3.17.0",
"@react-aria/selection": "^3.22.0",
"@react-aria/utils": "^3.27.0",
"@react-aria/visually-hidden": "^3.8.19",
"@react-stately/select": "^3.6.10",
"@react-types/button": "^3.10.2",
"@react-types/select": "^3.9.9",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/selection": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.22.0",
"resolved": "https://registry.npmjs.org/@react-aria/selection/-/selection-3.22.0.tgz",
"integrity": "sha512-XFOrK525HX2eeWeLZcZscUAs5qsuC1ZxsInDXMjvLeAaUPtQNEhUKHj3psDAl6XDU4VV1IJo0qCmFTVqTTMZSg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/selection": "^3.19.0",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/separator": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.4.5",
"resolved": "https://registry.npmjs.org/@react-aria/separator/-/separator-3.4.5.tgz",
"integrity": "sha512-RQA9sKZdAEjP1Yrv0GpDdXgmXd56kXDE8atPDHEC0/A4lpYh/YFLfXcv1JW0Hlg4kBocdX2pB2INyDGhiD+yfw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/utils": "^3.27.0",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/slider": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.7.15",
"resolved": "https://registry.npmjs.org/@react-aria/slider/-/slider-3.7.15.tgz",
"integrity": "sha512-v9tujsuvJYRX0vE/vMYBzTT9FXbzrLsjkOrouNq+UdBIr7wRjIWTHHM0j+khb2swyCWNTbdv6Ce316Zqx2qWFg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
"@react-aria/label": "^3.7.14",
"@react-aria/utils": "^3.27.0",
"@react-stately/slider": "^3.6.1",
"@react-types/shared": "^3.27.0",
"@react-types/slider": "^3.7.8",
♻️(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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/spinbutton": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.6.11",
"resolved": "https://registry.npmjs.org/@react-aria/spinbutton/-/spinbutton-3.6.11.tgz",
"integrity": "sha512-RM+gYS9tf9Wb+GegV18n4ArK3NBKgcsak7Nx1CkEgX9BjJ0yayWUHdfEjRRvxGXl+1z1n84cJVkZ6FUlWOWEZA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/i18n": "^3.12.5",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-aria/live-announcer": "^3.4.1",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/utils": "^3.27.0",
"@react-types/button": "^3.10.2",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/ssr": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "3.9.7",
"resolved": "https://registry.npmjs.org/@react-aria/ssr/-/ssr-3.9.7.tgz",
"integrity": "sha512-GQygZaGlmYjmYM+tiNBA5C6acmiDWF52Nqd40bBp0Znk4M4hP+LTmI0lpI1BuKMw45T8RIhrAsICIfKwZvi2Gg==",
"license": "Apache-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
"dependencies": {
"@swc/helpers": "^0.5.0"
},
"engines": {
"node": ">= 12"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/switch": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.6.11",
"resolved": "https://registry.npmjs.org/@react-aria/switch/-/switch-3.6.11.tgz",
"integrity": "sha512-paYCpH+oeL+8rgQK+cBJ+IaZ1sXSh3+50WPlg2LvLBta0QVfQhPR4juPvfXRpfHHhCjFBgF4/RGbV8q5zpl3vA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/toggle": "^3.10.11",
"@react-stately/toggle": "^3.8.1",
"@react-types/shared": "^3.27.0",
"@react-types/switch": "^3.5.8",
♻️(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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/table": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.16.1",
"resolved": "https://registry.npmjs.org/@react-aria/table/-/table-3.16.1.tgz",
"integrity": "sha512-T28TIGnKnPBunyErDBmm5jUX7AyzT7NVWBo9pDSt9wUuEnz0rVNd7p9sjmP2+u7I645feGG9klcdpCvFeqrk8A==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/grid": "^3.11.1",
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-aria/live-announcer": "^3.4.1",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/utils": "^3.27.0",
"@react-aria/visually-hidden": "^3.8.19",
"@react-stately/collections": "^3.12.1",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/flags": "^3.0.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/table": "^3.13.1",
"@react-types/checkbox": "^3.9.1",
"@react-types/grid": "^3.2.11",
"@react-types/shared": "^3.27.0",
"@react-types/table": "^3.10.4",
♻️(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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/tabs": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.9.9",
"resolved": "https://registry.npmjs.org/@react-aria/tabs/-/tabs-3.9.9.tgz",
"integrity": "sha512-oXPtANs16xu6MdMGLHjGV/2Zupvyp9CJEt7ORPLv5xAzSY5hSjuQHJLZ0te3Lh/KSG5/0o3RW/W5yEqo7pBQQQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/i18n": "^3.12.5",
"@react-aria/selection": "^3.22.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/tabs": "^3.7.1",
"@react-types/shared": "^3.27.0",
"@react-types/tabs": "^3.3.12",
♻️(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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/tag": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.4.9",
"resolved": "https://registry.npmjs.org/@react-aria/tag/-/tag-3.4.9.tgz",
"integrity": "sha512-Vnps+zk8vYyjevv2Bc6vc9kSp9HFLKrKUDmrWMc0DfseypwJMc3Ya6F965ZVTjF9nuWrojNmvgusNu7qyXFShQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/gridlist": "^3.10.1",
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
"@react-aria/label": "^3.7.14",
"@react-aria/selection": "^3.22.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/list": "^3.11.2",
"@react-types/button": "^3.10.2",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/textfield": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.16.0",
"resolved": "https://registry.npmjs.org/@react-aria/textfield/-/textfield-3.16.0.tgz",
"integrity": "sha512-53RVpMeMDN/QoabqnYZ1lxTh1xTQ3IBYQARuayq5EGGMafyxoFHzttxUdSqkZGK/+zdSF2GfmjOYJVm2nDKuDQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/form": "^3.0.12",
"@react-aria/label": "^3.7.14",
"@react-aria/utils": "^3.27.0",
"@react-stately/form": "^3.1.1",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.0",
"@react-types/textfield": "^3.11.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
➕(frontend) install react-toast in beta Absolutely needed some toasts to handle in app notifications, or feedbacks. React Aria is working on it, and has released a first beta. No component is available, only hooks.
2024-09-09 18:54:57 +02:00
"node_modules/@react-aria/toast": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.0.0-beta.19",
"resolved": "https://registry.npmjs.org/@react-aria/toast/-/toast-3.0.0-beta.19.tgz",
"integrity": "sha512-LCMTcmSmum5CzBk+DIec66q6pJGEl+InQPJdsby7QG/row0ka6wHPvul78HVseN7dzg6G3xVjvHtVPOixkuegA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
"@react-aria/landmark": "3.0.0-beta.18",
"@react-aria/utils": "^3.27.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/toast": "3.0.0-beta.7",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/button": "^3.10.2",
"@react-types/shared": "^3.27.0",
➕(frontend) install react-toast in beta Absolutely needed some toasts to handle in app notifications, or feedbacks. React Aria is working on it, and has released a first beta. No component is available, only hooks.
2024-09-09 18:54:57 +02:00
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1"
➕(frontend) install react-toast in beta Absolutely needed some toasts to handle in app notifications, or feedbacks. React Aria is working on it, and has released a first beta. No component is available, only hooks.
2024-09-09 18:54:57 +02:00
}
},
♻️(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
"node_modules/@react-aria/toggle": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.10.11",
"resolved": "https://registry.npmjs.org/@react-aria/toggle/-/toggle-3.10.11.tgz",
"integrity": "sha512-J3jO3KJiUbaYVDEpeXSBwqcyKxpi9OreiHRGiaxb6VwB+FWCj7Gb2WKajByXNyfs8jc6kX9VUFaXa7jze60oEQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/interactions": "^3.23.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/toggle": "^3.8.1",
"@react-types/checkbox": "^3.9.1",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/toolbar": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.0.0-beta.12",
"resolved": "https://registry.npmjs.org/@react-aria/toolbar/-/toolbar-3.0.0-beta.12.tgz",
"integrity": "sha512-a+Be27BtM2lzEdTzm19FikPbitfW65g/JZln3kyAvgpswhU6Ljl8lztaVw4ixjG4H0nqnKvVggMy4AlWwDUaVQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/i18n": "^3.12.5",
"@react-aria/utils": "^3.27.0",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/tooltip": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.7.11",
"resolved": "https://registry.npmjs.org/@react-aria/tooltip/-/tooltip-3.7.11.tgz",
"integrity": "sha512-mhZgAWUj7bUWipDeJXaVPZdqnzoBCd/uaEbdafnvgETmov1udVqPTh9w4ZKX2Oh1wa2+OdLFrBOk+8vC6QbWag==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/focus": "^3.19.1",
"@react-aria/interactions": "^3.23.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/tooltip": "^3.5.1",
"@react-types/shared": "^3.27.0",
"@react-types/tooltip": "^3.4.14",
♻️(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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/tree": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.0.0-beta.3",
"resolved": "https://registry.npmjs.org/@react-aria/tree/-/tree-3.0.0-beta.3.tgz",
"integrity": "sha512-eQnCtvDgpunCHInIT+Da3qdgzDzKEFW9REX2j1vMqWTsbM1YikVlBzB9AJOd9KIAWyn+p4TYdL8zzPWxvuSdfA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/gridlist": "^3.10.1",
"@react-aria/i18n": "^3.12.5",
"@react-aria/selection": "^3.22.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/tree": "^3.8.7",
"@react-types/button": "^3.10.2",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-aria/utils": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.27.0",
"resolved": "https://registry.npmjs.org/@react-aria/utils/-/utils-3.27.0.tgz",
"integrity": "sha512-p681OtApnKOdbeN8ITfnnYqfdHS0z7GE+4l8EXlfLnr70Rp/9xicBO6d2rU+V/B3JujDw2gPWxYKEnEeh0CGCw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-aria/ssr": "^3.9.7",
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0",
"clsx": "^2.0.0"
},
"peerDependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/@react-aria/virtualizer": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "4.1.1",
"resolved": "https://registry.npmjs.org/@react-aria/virtualizer/-/virtualizer-4.1.1.tgz",
"integrity": "sha512-AYQmC/S9HhxGOj8HkQdxDW8/+sUEmmfcGpjkInzXB8UZCB1FQLC0LpvA8fOP7AfzLaAL+HVcYF5BvnGMPijHTQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
"@react-aria/utils": "^3.27.0",
"@react-stately/virtualizer": "^4.2.1",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/@react-aria/visually-hidden": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.8.19",
"resolved": "https://registry.npmjs.org/@react-aria/visually-hidden/-/visually-hidden-3.8.19.tgz",
"integrity": "sha512-MZgCCyQ3sdG94J5iJz7I7Ai3IxoN0U5d/+EaUnA1mfK7jf2fSYQBqi6Eyp8sWUYzBTLw4giXB5h0RGAnWzk9hA==",
"license": "Apache-2.0",
"dependencies": {
"@react-aria/interactions": "^3.23.0",
"@react-aria/utils": "^3.27.0",
"@react-types/shared": "^3.27.0",
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1"
}
},
"node_modules/@react-stately/autocomplete": {
"version": "3.0.0-alpha.0",
"resolved": "https://registry.npmjs.org/@react-stately/autocomplete/-/autocomplete-3.0.0-alpha.0.tgz",
"integrity": "sha512-as4si0pBcnGnggwpvemMwCLTeV0h9GS9e5eHSR3RFg14eqUHZBEzYJ0kh9oTugpsGuf1TSM/HDizo8GQk3EtPA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/utils": "^3.10.4",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"@swc/helpers": "^0.5.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
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/calendar": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.7.0",
"resolved": "https://registry.npmjs.org/@react-stately/calendar/-/calendar-3.7.0.tgz",
"integrity": "sha512-N15zKubP2S7eWfPSJjKVlmJA7YpWzrIGx52BFhwLSQAZcV+OPcMgvOs71WtB7PLwl6DUYQGsgc0B3tcHzzvdvQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@internationalized/date": "^3.7.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/calendar": "^3.6.0",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/checkbox": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.6.11",
"resolved": "https://registry.npmjs.org/@react-stately/checkbox/-/checkbox-3.6.11.tgz",
"integrity": "sha512-jApdBis+Q1sXLivg+f7krcVaP/AMMMiQcVqcz5gwxlweQN+dRZ/NpL0BYaDOuGc26Mp0lcuVaET3jIZeHwtyxA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/form": "^3.1.1",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/checkbox": "^3.9.1",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/collections": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.12.1",
"resolved": "https://registry.npmjs.org/@react-stately/collections/-/collections-3.12.1.tgz",
"integrity": "sha512-8QmFBL7f+P64dEP4o35pYH61/lP0T/ziSdZAvNMrCqaM+fXcMfUp2yu1E63kADVX7WRDsFJWE3CVMeqirPH6Xg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/color": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.8.2",
"resolved": "https://registry.npmjs.org/@react-stately/color/-/color-3.8.2.tgz",
"integrity": "sha512-GXwLmv1Eos2OwOiRsGFrXBKx8+uZh2q0qzLZEVYrWsedNhIdTm7nnpwO68nCYZPHkqhv6rhhVSlOOFmDLY++ow==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
"@internationalized/number": "^3.6.0",
"@internationalized/string": "^3.2.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/form": "^3.1.1",
"@react-stately/numberfield": "^3.9.9",
"@react-stately/slider": "^3.6.1",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/color": "^3.0.2",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/combobox": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.10.2",
"resolved": "https://registry.npmjs.org/@react-stately/combobox/-/combobox-3.10.2.tgz",
"integrity": "sha512-uT642Dool4tQBh+8UQjlJnTisrJVtg3LqmiP/HqLQ4O3pW0O+ImbG+2r6c9dUzlAnH4kEfmEwCp9dxkBkmFWsg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/collections": "^3.12.1",
"@react-stately/form": "^3.1.1",
"@react-stately/list": "^3.11.2",
"@react-stately/overlays": "^3.6.13",
"@react-stately/select": "^3.6.10",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/combobox": "^3.13.2",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/data": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.12.1",
"resolved": "https://registry.npmjs.org/@react-stately/data/-/data-3.12.1.tgz",
"integrity": "sha512-/Nc8X1FmrJ53QU4rN/1i1JtNir4iqo+39Xn5ZOJ74Nng7T+xVVuEuWSo+OEGaycCJf2eZRsomauPxUnnZgCM1A==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/datepicker": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.12.0",
"resolved": "https://registry.npmjs.org/@react-stately/datepicker/-/datepicker-3.12.0.tgz",
"integrity": "sha512-AfJEP36d+QgQ30GfacXtYdGsJvqY2yuCJ+JrjHct+m1nYuTkMvMMnhwNBFasgDJPLCDyHzyANlWkl2kQGfsBFw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@internationalized/date": "^3.7.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@internationalized/string": "^3.2.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/form": "^3.1.1",
"@react-stately/overlays": "^3.6.13",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/datepicker": "^3.10.0",
"@react-types/shared": "^3.27.0",
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1"
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
}
},
"node_modules/@react-stately/disclosure": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/@react-stately/disclosure/-/disclosure-3.0.1.tgz",
"integrity": "sha512-afpNy5b0UcqRGjU/W5OD0xkx4PbymvhMrgQZ4o4OdtDVMMvr9T5UqMF8/j3J591DxgQfXM872tJu0kotqT0L6Q==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"dependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/dnd": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.5.1",
"resolved": "https://registry.npmjs.org/@react-stately/dnd/-/dnd-3.5.1.tgz",
"integrity": "sha512-N18wt6fka9ngJJqxfAzmdtyrk9whAnqWUxZn22CatjNQsqukI4a6KRYwZTXM9x/wm7KamhVOp+GBl85zM8GLdA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/selection": "^3.19.0",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/flags": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "3.0.5",
"resolved": "https://registry.npmjs.org/@react-stately/flags/-/flags-3.0.5.tgz",
"integrity": "sha512-6wks4csxUwPCp23LgJSnkBRhrWpd9jGd64DjcCTNB2AHIFu7Ab1W59pJpUL6TW7uAxVxdNKjgn6D1hlBy8qWsA==",
"license": "Apache-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
"dependencies": {
"@swc/helpers": "^0.5.0"
}
},
"node_modules/@react-stately/form": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/@react-stately/form/-/form-3.1.1.tgz",
"integrity": "sha512-qavrz5X5Mdf/Q1v/QJRxc0F8UTNEyRCNSM1we/nnF7GV64+aYSDLOtaRGmzq+09RSwo1c8ZYnIkK5CnwsPhTsQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/grid": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.10.1",
"resolved": "https://registry.npmjs.org/@react-stately/grid/-/grid-3.10.1.tgz",
"integrity": "sha512-MOIy//AdxZxIXIzvWSKpvMvaPEMZGQNj+/cOsElHepv/Veh0psNURZMh2TP6Mr0+MnDTZbX+5XIeinGkWYO3JQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/collections": "^3.12.1",
"@react-stately/selection": "^3.19.0",
"@react-types/grid": "^3.2.11",
"@react-types/shared": "^3.27.0",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/@react-stately/layout": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "4.1.1",
"resolved": "https://registry.npmjs.org/@react-stately/layout/-/layout-4.1.1.tgz",
"integrity": "sha512-kXeo7HKYTOcqMKru1sKFoMoZA+YywSUqHeIA90MptzRugbFhQGq4nUbIYM2p3FeHAX9HU1JAXThuLcwDOHhB8Q==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/collections": "^3.12.1",
"@react-stately/table": "^3.13.1",
"@react-stately/virtualizer": "^4.2.1",
"@react-types/grid": "^3.2.11",
"@react-types/shared": "^3.27.0",
"@react-types/table": "^3.10.4",
♻️(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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/list": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.11.2",
"resolved": "https://registry.npmjs.org/@react-stately/list/-/list-3.11.2.tgz",
"integrity": "sha512-eU2tY3aWj0SEeC7lH9AQoeAB4LL9mwS54FvTgHHoOgc1ZIwRJUaZoiuETyWQe98AL8KMgR1nrnDJ1I+CcT1Y7g==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/collections": "^3.12.1",
"@react-stately/selection": "^3.19.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/menu": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.9.1",
"resolved": "https://registry.npmjs.org/@react-stately/menu/-/menu-3.9.1.tgz",
"integrity": "sha512-WRjGGImhQlQaer/hhahGytwd1BDq3fjpTkY/04wv3cQJPJR6lkVI5nSvGFMHfCaErsA1bNyB8/T9Y5F5u4u9ng==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/overlays": "^3.6.13",
"@react-types/menu": "^3.9.14",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/numberfield": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.9.9",
"resolved": "https://registry.npmjs.org/@react-stately/numberfield/-/numberfield-3.9.9.tgz",
"integrity": "sha512-hZsLiGGHTHmffjFymbH1qVmA633rU2GNjMFQTuSsN4lqqaP8fgxngd5pPCoTCUFEkUgWjdHenw+ZFByw8lIE+g==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"dependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@internationalized/number": "^3.6.0",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/form": "^3.1.1",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/numberfield": "^3.8.8",
♻️(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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/overlays": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.6.13",
"resolved": "https://registry.npmjs.org/@react-stately/overlays/-/overlays-3.6.13.tgz",
"integrity": "sha512-WsU85Gf/b+HbWsnnYw7P/Ila3wD+C37Uk/WbU4/fHgJ26IEOWsPE6wlul8j54NZ1PnLNhV9Fn+Kffi+PaJMQXQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/overlays": "^3.8.12",
♻️(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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/radio": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.10.10",
"resolved": "https://registry.npmjs.org/@react-stately/radio/-/radio-3.10.10.tgz",
"integrity": "sha512-9x3bpq87uV8iYA4NaioTTWjriQSlSdp+Huqlxll0T3W3okpyraTTejE91PbIoRTUmL5qByIh2WzxYmr4QdBgAA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/form": "^3.1.1",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/radio": "^3.8.6",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/searchfield": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.5.9",
"resolved": "https://registry.npmjs.org/@react-stately/searchfield/-/searchfield-3.5.9.tgz",
"integrity": "sha512-7/aO/oLJ4czKEji0taI/lbHKqPJRag9p3YmRaZ4yqjIMpKxzmJCWQcov5lzWeFhG/1hINKndYlxFnVIKV/urpg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/searchfield": "^3.5.11",
♻️(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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/select": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.6.10",
"resolved": "https://registry.npmjs.org/@react-stately/select/-/select-3.6.10.tgz",
"integrity": "sha512-V7V0FCL9T+GzLjyfnJB6PUaKldFyT/8Rj6M+R9ura1A0O+s/FEOesy0pdMXFoL1l5zeUpGlCnhJrsI5HFWHfDw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/form": "^3.1.1",
"@react-stately/list": "^3.11.2",
"@react-stately/overlays": "^3.6.13",
"@react-types/select": "^3.9.9",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/selection": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.19.0",
"resolved": "https://registry.npmjs.org/@react-stately/selection/-/selection-3.19.0.tgz",
"integrity": "sha512-AvbUqnWjqVQC48RD39S9BpMKMLl55Zo5l/yx5JQFPl55cFwe9Tpku1KY0wzt3fXXiXWaqjDn/7Gkg1VJYy8esQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/collections": "^3.12.1",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/slider": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.6.1",
"resolved": "https://registry.npmjs.org/@react-stately/slider/-/slider-3.6.1.tgz",
"integrity": "sha512-8kij5O82Xe233vZZ6qNGqPXidnlNQiSnyF1q613c7ktFmzAyGjkIWVUapHi23T1fqm7H2Rs3RWlmwE9bo2KecA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.0",
"@react-types/slider": "^3.7.8",
♻️(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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/table": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.13.1",
"resolved": "https://registry.npmjs.org/@react-stately/table/-/table-3.13.1.tgz",
"integrity": "sha512-Im8W+F8o9EhglY5kqRa3xcMGXl8zBi6W5phGpAjXb+UGDL1tBIlAcYj733bw8g/ITCnaSz9ubsmON0HekPd6Jg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/collections": "^3.12.1",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/flags": "^3.0.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/grid": "^3.10.1",
"@react-stately/selection": "^3.19.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/grid": "^3.2.11",
"@react-types/shared": "^3.27.0",
"@react-types/table": "^3.10.4",
♻️(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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/tabs": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.7.1",
"resolved": "https://registry.npmjs.org/@react-stately/tabs/-/tabs-3.7.1.tgz",
"integrity": "sha512-gr9ACyuWrYuc727h7WaHdmNw8yxVlUyQlguziR94MdeRtFGQnf3V6fNQG3kxyB77Ljko69tgDF7Nf6kfPUPAQQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/list": "^3.11.2",
"@react-types/shared": "^3.27.0",
"@react-types/tabs": "^3.3.12",
♻️(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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
➕(frontend) install react-toast in beta Absolutely needed some toasts to handle in app notifications, or feedbacks. React Aria is working on it, and has released a first beta. No component is available, only hooks.
2024-09-09 18:54:57 +02:00
"node_modules/@react-stately/toast": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "3.0.0-beta.7",
"resolved": "https://registry.npmjs.org/@react-stately/toast/-/toast-3.0.0-beta.7.tgz",
"integrity": "sha512-+KDkaOS5Y4ApOfiP0HHij4ySwAd1VM9/pI4rVTyHrzkp0R2Q0eBxZ74MpWMpVfJa2lSjb/qEm60tqJ3A+4R/cQ==",
"license": "Apache-2.0",
➕(frontend) install react-toast in beta Absolutely needed some toasts to handle in app notifications, or feedbacks. React Aria is working on it, and has released a first beta. No component is available, only hooks.
2024-09-09 18:54:57 +02:00
"dependencies": {
"@swc/helpers": "^0.5.0",
"use-sync-external-store": "^1.2.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1"
➕(frontend) install react-toast in beta Absolutely needed some toasts to handle in app notifications, or feedbacks. React Aria is working on it, and has released a first beta. No component is available, only hooks.
2024-09-09 18:54:57 +02:00
}
},
♻️(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
"node_modules/@react-stately/toggle": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.8.1",
"resolved": "https://registry.npmjs.org/@react-stately/toggle/-/toggle-3.8.1.tgz",
"integrity": "sha512-MVpe79ghVQiwLmVzIPhF/O/UJAUc9B+ZSylVTyJiEPi0cwhbkKGQv9thOF0ebkkRkace5lojASqUAYtSTZHQJA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/checkbox": "^3.9.1",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/tooltip": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.5.1",
"resolved": "https://registry.npmjs.org/@react-stately/tooltip/-/tooltip-3.5.1.tgz",
"integrity": "sha512-0aI3U5kB7Cop9OCW9/Bag04zkivFSdUcQgy/TWL4JtpXidVWmOha8txI1WySawFSjZhH83KIyPc+wKm1msfLMQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/overlays": "^3.6.13",
"@react-types/tooltip": "^3.4.14",
♻️(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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/tree": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.8.7",
"resolved": "https://registry.npmjs.org/@react-stately/tree/-/tree-3.8.7.tgz",
"integrity": "sha512-hpc3pyuXWeQV5ufQ02AeNQg/MYhnzZ4NOznlY5OOUoPzpLYiI3ZJubiY3Dot4jw5N/LR7CqvDLHmrHaJPmZlHg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/collections": "^3.12.1",
"@react-stately/selection": "^3.19.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/utils": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "3.10.5",
"resolved": "https://registry.npmjs.org/@react-stately/utils/-/utils-3.10.5.tgz",
"integrity": "sha512-iMQSGcpaecghDIh3mZEpZfoFH3ExBwTtuBEcvZ2XnGzCgQjeYXcMdIUwAfVQLXFTdHUHGF6Gu6/dFrYsCzySBQ==",
"license": "Apache-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
"dependencies": {
"@swc/helpers": "^0.5.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-stately/virtualizer": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "4.2.1",
"resolved": "https://registry.npmjs.org/@react-stately/virtualizer/-/virtualizer-4.2.1.tgz",
"integrity": "sha512-GHGEXV0ZRhq34U/P3LzkByCBfy2IDynYlV1SE4njkUWWGE/0AH56UegM6w2l3GeiNpXsXCgXl7jpAKeIGMEnrQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/utils": "^3.27.0",
"@react-types/shared": "^3.27.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
"@swc/helpers": "^0.5.0"
},
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"peerDependencies": {
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1"
}
},
"node_modules/@react-types/autocomplete": {
"version": "3.0.0-alpha.28",
"resolved": "https://registry.npmjs.org/@react-types/autocomplete/-/autocomplete-3.0.0-alpha.28.tgz",
"integrity": "sha512-meHxBVS5H2L7lVOX99jiAfhcvtG0s7EE7iF7X20/yqEnkwWSpyeMKcDKFpvx/bLGUSmRTVFCBLgvPpwUyhcFkg==",
"license": "Apache-2.0",
"dependencies": {
"@react-types/combobox": "^3.13.2",
"@react-types/searchfield": "^3.5.11",
"@react-types/shared": "^3.27.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
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1"
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
}
},
♻️(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
"node_modules/@react-types/breadcrumbs": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.7.10",
"resolved": "https://registry.npmjs.org/@react-types/breadcrumbs/-/breadcrumbs-3.7.10.tgz",
"integrity": "sha512-5HhRxkKHfAQBoyOYzyf4HT+24HgPE/C/QerxJLNNId303LXO03yeYrbvRqhYZSlD1ACLJW9OmpPpREcw5iSqgw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/link": "^3.5.10",
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/button": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.10.2",
"resolved": "https://registry.npmjs.org/@react-types/button/-/button-3.10.2.tgz",
"integrity": "sha512-h8SB/BLoCgoBulCpyzaoZ+miKXrolK9XC48+n1dKJXT8g4gImrficurDW6+PRTQWaRai0Q0A6bu8UibZOU4syg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/calendar": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.6.0",
"resolved": "https://registry.npmjs.org/@react-types/calendar/-/calendar-3.6.0.tgz",
"integrity": "sha512-BtFh4BFwvsYlsaSqUOVxlqXZSlJ6u4aozgO3PwHykhpemwidlzNwm9qDZhcMWPioNF/w2cU/6EqhvEKUHDnFZg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@internationalized/date": "^3.7.0",
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/checkbox": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.9.1",
"resolved": "https://registry.npmjs.org/@react-types/checkbox/-/checkbox-3.9.1.tgz",
"integrity": "sha512-0x/KQcipfNM9Nvy6UMwYG25roRLvsiqf0J3woTYylNNWzF+72XT0iI5FdJkE3w2wfa0obmSoeq4WcbFREQrH/A==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/color": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/@react-types/color/-/color-3.0.2.tgz",
"integrity": "sha512-4k9c0l5SACwTtkHV0dQ0GrF0Kktk/NChkxtyu58BamyUQOsCe8sqny+uul2nPrqQvuVof/dkRjKhv/DVyyx2mw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.0",
"@react-types/slider": "^3.7.8"
♻️(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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/combobox": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.13.2",
"resolved": "https://registry.npmjs.org/@react-types/combobox/-/combobox-3.13.2.tgz",
"integrity": "sha512-yl2yMcM5/v3lJiNZWjpAhQ9vRW6dD55CD4rYmO2K7XvzYJaFVT4WYI/AymPYD8RqomMp7coBmBHfHW0oupk8gg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/datepicker": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.10.0",
"resolved": "https://registry.npmjs.org/@react-types/datepicker/-/datepicker-3.10.0.tgz",
"integrity": "sha512-Att7y4NedNH1CogMDIX9URXgMLxGbZgnFCZ8oxgFAVndWzbh3TBcc4s7uoJDPvgRMAalq+z+SrlFFeoBeJmvvg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@internationalized/date": "^3.7.0",
"@react-types/calendar": "^3.6.0",
"@react-types/overlays": "^3.8.12",
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/dialog": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.5.15",
"resolved": "https://registry.npmjs.org/@react-types/dialog/-/dialog-3.5.15.tgz",
"integrity": "sha512-BX1+mV35Oa0aIlhu98OzJaSB7uiCWDPQbr0AkpFBajSSlESUoAjntN+4N+QJmj24z2v6UE9zxGQ85/U/0Le+bw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/overlays": "^3.8.12",
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/form": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.7.9",
"resolved": "https://registry.npmjs.org/@react-types/form/-/form-3.7.9.tgz",
"integrity": "sha512-+qGDrQFdIh8umU82zmnYJ0V2rLoGSQ3yApFT02URz//NWeTA7qo0Oab2veKvXUkcBb47oSvytZYmkExPikxIEg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/grid": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.2.11",
"resolved": "https://registry.npmjs.org/@react-types/grid/-/grid-3.2.11.tgz",
"integrity": "sha512-Mww9nrasppvPbsBi+uUqFnf7ya8fXN0cTVzDNG+SveD8mhW+sbtuy+gPtEpnFD2Oyi8qLuObefzt4gdekJX2Yw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/link": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.5.10",
"resolved": "https://registry.npmjs.org/@react-types/link/-/link-3.5.10.tgz",
"integrity": "sha512-IM2mbSpB0qP44Jh1Iqpevo7bQdZAr0iDyDi13OhsiUYJeWgPMHzGEnQqdBMkrfQeOTXLtZtUyOYLXE2v39bhzQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/listbox": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.5.4",
"resolved": "https://registry.npmjs.org/@react-types/listbox/-/listbox-3.5.4.tgz",
"integrity": "sha512-5otTes0zOwRZwNtqysPD/aW4qFJSxd5znjwoWTLnzDXXOBHXPyR83IJf8ITgvIE5C0y+EFadsWR/BBO3k9Pj7g==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/menu": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.9.14",
"resolved": "https://registry.npmjs.org/@react-types/menu/-/menu-3.9.14.tgz",
"integrity": "sha512-RJW/S8IPwbRuohJ/A9HJ7W8QaAY816tm7Nv6+H/TLXG76zu2AS5vEgq+0TcCAWvJJwUdLDpJWJMlo0iIoIBtcg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/overlays": "^3.8.12",
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/meter": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.4.6",
"resolved": "https://registry.npmjs.org/@react-types/meter/-/meter-3.4.6.tgz",
"integrity": "sha512-YczAht1VXy3s4fR6Dq0ibGsjulGHzS/A/K4tOruSNTL6EkYH9ktHX62Xk/OhCiKHxV315EbZ136WJaCeO4BgHw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/progress": "^3.5.9"
♻️(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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/numberfield": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.8.8",
"resolved": "https://registry.npmjs.org/@react-types/numberfield/-/numberfield-3.8.8.tgz",
"integrity": "sha512-825JPppxDaWh0Zxb0Q+wSslgRQYOtQPCAuhszPuWEy6d2F/M+hLR+qQqvQm9+LfMbdwiTg6QK5wxdWFCp2t7jw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/overlays": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.8.12",
"resolved": "https://registry.npmjs.org/@react-types/overlays/-/overlays-3.8.12.tgz",
"integrity": "sha512-ZvR1t0YV7/6j+6OD8VozKYjvsXT92+C/2LOIKozy7YUNS5KI4MkXbRZzJvkuRECVZOmx8JXKTUzhghWJM/3QuQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/progress": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.5.9",
"resolved": "https://registry.npmjs.org/@react-types/progress/-/progress-3.5.9.tgz",
"integrity": "sha512-zFxOzx3G8XUmHgpm037Hcayls5bqzXVa182E3iM7YWTmrjxJPKZ58XL0WWBgpTd+mJD7fTpnFdAZqSmFbtDOdA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/radio": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.8.6",
"resolved": "https://registry.npmjs.org/@react-types/radio/-/radio-3.8.6.tgz",
"integrity": "sha512-woTQYdRFjPzuml4qcIf+2zmycRuM5w3fDS5vk6CQmComVUjOFPtD28zX3Z9kc9lSNzaBQz9ONZfFqkZ1gqfICA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/searchfield": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.5.11",
"resolved": "https://registry.npmjs.org/@react-types/searchfield/-/searchfield-3.5.11.tgz",
"integrity": "sha512-MX8d9pgvxZxmgDwI0tiDaf6ijOY8XcRj0HM8Ocfttlk7PEFJK44p51WsUC+fPX1GmZni2JpFkx/haPOSLUECdw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.0",
"@react-types/textfield": "^3.11.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/select": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.9.9",
"resolved": "https://registry.npmjs.org/@react-types/select/-/select-3.9.9.tgz",
"integrity": "sha512-/hCd0o+ztn29FKCmVec+v7t4JpOzz56o+KrG7NDq2pcRWqUR9kNwCjrPhSbJIIEDm4ubtrfPu41ysIuDvRd2Bg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/shared": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.27.0",
"resolved": "https://registry.npmjs.org/@react-types/shared/-/shared-3.27.0.tgz",
"integrity": "sha512-gvznmLhi6JPEf0bsq7SwRYTHAKKq/wcmKqFez9sRdbED+SPMUmK5omfZ6w3EwUFQHbYUa4zPBYedQ7Knv70RMw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/slider": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.7.8",
"resolved": "https://registry.npmjs.org/@react-types/slider/-/slider-3.7.8.tgz",
"integrity": "sha512-utW1o9KT70hqFwu1zqMtyEWmP0kSATk4yx+Fm/peSR4iZa+BasRqH83yzir5GKc8OfqfE1kmEsSlO98/k986+w==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/switch": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.5.8",
"resolved": "https://registry.npmjs.org/@react-types/switch/-/switch-3.5.8.tgz",
"integrity": "sha512-sL7jmh8llF8BxzY4HXkSU4bwU8YU6gx45P85D0AdYXgRHxU9Cp7BQPOMF4pJoQ8TTej05MymY5q7xvJVmxUTAQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/table": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.10.4",
"resolved": "https://registry.npmjs.org/@react-types/table/-/table-3.10.4.tgz",
"integrity": "sha512-d0tLz/whxVteqr1rophtuuxqyknHHfTKeXrCgDjt8pAyd9U8GPDbfcFSfYPUhWdELRt7aLVyQw6VblZHioVEgQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/grid": "^3.2.11",
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/tabs": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.3.12",
"resolved": "https://registry.npmjs.org/@react-types/tabs/-/tabs-3.3.12.tgz",
"integrity": "sha512-E9O9G+wf9kaQ8UbDEDliW/oxYlJnh7oDCW1zaMOySwnG4yeCh7Wu02EOCvlQW4xvgn/i+lbEWgirf7L+yj5nRg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/textfield": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.11.0",
"resolved": "https://registry.npmjs.org/@react-types/textfield/-/textfield-3.11.0.tgz",
"integrity": "sha512-YORBgr6wlu2xfvr4MqjKFHGpj+z8LBzk14FbWDbYnnhGnv0I10pj+m2KeOHgDNFHrfkDdDOQmMIKn1UCqeUuEg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/@react-types/tooltip": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.4.14",
"resolved": "https://registry.npmjs.org/@react-types/tooltip/-/tooltip-3.4.14.tgz",
"integrity": "sha512-J7CeYL2yPeKIasx1rPaEefyCHGEx2DOCx+7bM3XcKGmCxvNdVQLjimNJOt8IHlUA0nFJQOjmSW/mz9P0f2/kUw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-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
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-types/overlays": "^3.8.12",
"@react-types/shared": "^3.27.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
💄(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
"node_modules/@remixicon/react": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "4.6.0",
"resolved": "https://registry.npmjs.org/@remixicon/react/-/react-4.6.0.tgz",
"integrity": "sha512-bY56maEgT5IYUSRotqy9h03IAKJC85vlKtWFg2FKzfs8JPrkdBAYSa9dxoUSKFwGzup8Ux6vjShs9Aec3jvr2w==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.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
"peerDependencies": {
"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
"node_modules/@rollup/rollup-android-arm-eabi": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/@rollup/rollup-android-arm-eabi/-/rollup-android-arm-eabi-4.24.0.tgz",
"integrity": "sha512-Q6HJd7Y6xdB48x8ZNVDOqsbh2uByBhgK8PiQgPhwkIw/HC/YX5Ghq2mQY5sRMZWHb3VsFkWooUVOZHKr7DmDIA==",
♻️(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
"cpu": [
"arm"
],
"dev": true,
"optional": true,
"os": [
"android"
]
},
"node_modules/@rollup/rollup-android-arm64": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/@rollup/rollup-android-arm64/-/rollup-android-arm64-4.24.0.tgz",
"integrity": "sha512-ijLnS1qFId8xhKjT81uBHuuJp2lU4x2yxa4ctFPtG+MqEE6+C5f/+X/bStmxapgmwLwiL3ih122xv8kVARNAZA==",
♻️(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
"cpu": [
"arm64"
],
"dev": true,
"optional": true,
"os": [
"android"
]
},
"node_modules/@rollup/rollup-darwin-arm64": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/@rollup/rollup-darwin-arm64/-/rollup-darwin-arm64-4.24.0.tgz",
"integrity": "sha512-bIv+X9xeSs1XCk6DVvkO+S/z8/2AMt/2lMqdQbMrmVpgFvXlmde9mLcbQpztXm1tajC3raFDqegsH18HQPMYtA==",
♻️(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
"cpu": [
"arm64"
],
"dev": true,
"optional": true,
"os": [
"darwin"
]
},
"node_modules/@rollup/rollup-darwin-x64": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/@rollup/rollup-darwin-x64/-/rollup-darwin-x64-4.24.0.tgz",
"integrity": "sha512-X6/nOwoFN7RT2svEQWUsW/5C/fYMBe4fnLK9DQk4SX4mgVBiTA9h64kjUYPvGQ0F/9xwJ5U5UfTbl6BEjaQdBQ==",
♻️(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
"cpu": [
"x64"
],
"dev": true,
"optional": true,
"os": [
"darwin"
]
},
"node_modules/@rollup/rollup-linux-arm-gnueabihf": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/@rollup/rollup-linux-arm-gnueabihf/-/rollup-linux-arm-gnueabihf-4.24.0.tgz",
"integrity": "sha512-0KXvIJQMOImLCVCz9uvvdPgfyWo93aHHp8ui3FrtOP57svqrF/roSSR5pjqL2hcMp0ljeGlU4q9o/rQaAQ3AYA==",
♻️(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
"cpu": [
"arm"
],
"dev": true,
"optional": true,
"os": [
"linux"
]
},
"node_modules/@rollup/rollup-linux-arm-musleabihf": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/@rollup/rollup-linux-arm-musleabihf/-/rollup-linux-arm-musleabihf-4.24.0.tgz",
"integrity": "sha512-it2BW6kKFVh8xk/BnHfakEeoLPv8STIISekpoF+nBgWM4d55CZKc7T4Dx1pEbTnYm/xEKMgy1MNtYuoA8RFIWw==",
♻️(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
"cpu": [
"arm"
],
"dev": true,
"optional": true,
"os": [
"linux"
]
},
"node_modules/@rollup/rollup-linux-arm64-gnu": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/@rollup/rollup-linux-arm64-gnu/-/rollup-linux-arm64-gnu-4.24.0.tgz",
"integrity": "sha512-i0xTLXjqap2eRfulFVlSnM5dEbTVque/3Pi4g2y7cxrs7+a9De42z4XxKLYJ7+OhE3IgxvfQM7vQc43bwTgPwA==",
♻️(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
"cpu": [
"arm64"
],
"dev": true,
"optional": true,
"os": [
"linux"
]
},
"node_modules/@rollup/rollup-linux-arm64-musl": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/@rollup/rollup-linux-arm64-musl/-/rollup-linux-arm64-musl-4.24.0.tgz",
"integrity": "sha512-9E6MKUJhDuDh604Qco5yP/3qn3y7SLXYuiC0Rpr89aMScS2UAmK1wHP2b7KAa1nSjWJc/f/Lc0Wl1L47qjiyQw==",
♻️(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
"cpu": [
"arm64"
],
"dev": true,
"optional": true,
"os": [
"linux"
]
},
"node_modules/@rollup/rollup-linux-powerpc64le-gnu": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/@rollup/rollup-linux-powerpc64le-gnu/-/rollup-linux-powerpc64le-gnu-4.24.0.tgz",
"integrity": "sha512-2XFFPJ2XMEiF5Zi2EBf4h73oR1V/lycirxZxHZNc93SqDN/IWhYYSYj8I9381ikUFXZrz2v7r2tOVk2NBwxrWw==",
♻️(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
"cpu": [
"ppc64"
],
"dev": true,
"optional": true,
"os": [
"linux"
]
},
"node_modules/@rollup/rollup-linux-riscv64-gnu": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/@rollup/rollup-linux-riscv64-gnu/-/rollup-linux-riscv64-gnu-4.24.0.tgz",
"integrity": "sha512-M3Dg4hlwuntUCdzU7KjYqbbd+BLq3JMAOhCKdBE3TcMGMZbKkDdJ5ivNdehOssMCIokNHFOsv7DO4rlEOfyKpg==",
♻️(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
"cpu": [
"riscv64"
],
"dev": true,
"optional": true,
"os": [
"linux"
]
},
"node_modules/@rollup/rollup-linux-s390x-gnu": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/@rollup/rollup-linux-s390x-gnu/-/rollup-linux-s390x-gnu-4.24.0.tgz",
"integrity": "sha512-mjBaoo4ocxJppTorZVKWFpy1bfFj9FeCMJqzlMQGjpNPY9JwQi7OuS1axzNIk0nMX6jSgy6ZURDZ2w0QW6D56g==",
♻️(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
"cpu": [
"s390x"
],
"dev": true,
"optional": true,
"os": [
"linux"
]
},
"node_modules/@rollup/rollup-linux-x64-gnu": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/@rollup/rollup-linux-x64-gnu/-/rollup-linux-x64-gnu-4.24.0.tgz",
"integrity": "sha512-ZXFk7M72R0YYFN5q13niV0B7G8/5dcQ9JDp8keJSfr3GoZeXEoMHP/HlvqROA3OMbMdfr19IjCeNAnPUG93b6A==",
♻️(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
"cpu": [
"x64"
],
"dev": true,
"optional": true,
"os": [
"linux"
]
},
"node_modules/@rollup/rollup-linux-x64-musl": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/@rollup/rollup-linux-x64-musl/-/rollup-linux-x64-musl-4.24.0.tgz",
"integrity": "sha512-w1i+L7kAXZNdYl+vFvzSZy8Y1arS7vMgIy8wusXJzRrPyof5LAb02KGr1PD2EkRcl73kHulIID0M501lN+vobQ==",
♻️(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
"cpu": [
"x64"
],
"dev": true,
"optional": true,
"os": [
"linux"
]
},
"node_modules/@rollup/rollup-win32-arm64-msvc": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/@rollup/rollup-win32-arm64-msvc/-/rollup-win32-arm64-msvc-4.24.0.tgz",
"integrity": "sha512-VXBrnPWgBpVDCVY6XF3LEW0pOU51KbaHhccHw6AS6vBWIC60eqsH19DAeeObl+g8nKAz04QFdl/Cefta0xQtUQ==",
♻️(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
"cpu": [
"arm64"
],
"dev": true,
"optional": true,
"os": [
"win32"
]
},
"node_modules/@rollup/rollup-win32-ia32-msvc": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/@rollup/rollup-win32-ia32-msvc/-/rollup-win32-ia32-msvc-4.24.0.tgz",
"integrity": "sha512-xrNcGDU0OxVcPTH/8n/ShH4UevZxKIO6HJFK0e15XItZP2UcaiLFd5kiX7hJnqCbSztUF8Qot+JWBC/QXRPYWQ==",
♻️(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
"cpu": [
"ia32"
],
"dev": true,
"optional": true,
"os": [
"win32"
]
},
"node_modules/@rollup/rollup-win32-x64-msvc": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/@rollup/rollup-win32-x64-msvc/-/rollup-win32-x64-msvc-4.24.0.tgz",
"integrity": "sha512-fbMkAF7fufku0N2dE5TBXcNlg0pt0cJue4xBRE2Qc5Vqikxr4VCgKj/ht6SMdFcOacVA9rqF70APJ8RN/4vMJw==",
♻️(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
"cpu": [
"x64"
],
"dev": true,
"optional": true,
"os": [
"win32"
]
},
"node_modules/@swc/helpers": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "0.5.13",
"resolved": "https://registry.npmjs.org/@swc/helpers/-/helpers-0.5.13.tgz",
"integrity": "sha512-UoKGxQ3r5kYI9dALKJapMmuK+1zWM/H17Z1+iwnNmzcJRnfFuevZs375TA5rW31pu4BS4NoSy1fRsexDXfWn5w==",
♻️(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
"dependencies": {
"tslib": "^2.4.0"
}
},
"node_modules/@tanstack/eslint-plugin-query": {
⬆️(frontend) bump react-query-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:00:48 +01:00
"version": "5.64.2",
"resolved": "https://registry.npmjs.org/@tanstack/eslint-plugin-query/-/eslint-plugin-query-5.64.2.tgz",
"integrity": "sha512-Xq7jRYvNtGMHjQEGUZLHgEMNB59hgTlqdmKor6cdJ6CMZ/nwmBGpnlr/dcHden7W7BPCdBVN4PWMZBICWvCNQQ==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(frontend) bump react-query-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:00:48 +01:00
"@typescript-eslint/utils": "^8.18.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
},
"funding": {
"type": "github",
"url": "https://github.com/sponsors/tannerlinsley"
},
"peerDependencies": {
"eslint": "^8.57.0 || ^9.0.0"
}
},
"node_modules/@tanstack/query-core": {
⬆️(frontend) bump react-query-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:00:48 +01:00
"version": "5.64.2",
"resolved": "https://registry.npmjs.org/@tanstack/query-core/-/query-core-5.64.2.tgz",
"integrity": "sha512-hdO8SZpWXoADNTWXV9We8CwTkXU88OVWRBcsiFrk7xJQnhm6WRlweDzMD+uH+GnuieTBVSML6xFa17C2cNV8+g==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"funding": {
"type": "github",
"url": "https://github.com/sponsors/tannerlinsley"
}
},
"node_modules/@tanstack/query-devtools": {
⬆️(frontend) bump react-query-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:00:48 +01:00
"version": "5.64.2",
"resolved": "https://registry.npmjs.org/@tanstack/query-devtools/-/query-devtools-5.64.2.tgz",
"integrity": "sha512-3DautR5UpVZdk/qNIhioZVF7g8fdQZ1U98sBEEk4Tzz3tihSBNMPgwlP40nzgbPEDBIrn/j/oyyvNBVSo083Vw==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"funding": {
"type": "github",
"url": "https://github.com/sponsors/tannerlinsley"
}
},
"node_modules/@tanstack/react-query": {
⬆️(frontend) bump react-query-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:00:48 +01:00
"version": "5.64.2",
"resolved": "https://registry.npmjs.org/@tanstack/react-query/-/react-query-5.64.2.tgz",
"integrity": "sha512-3pakNscZNm8KJkxmovvtZ4RaXLyiYYobwleTMvpIGUoKRa8j8VlrQKNl5W8VUEfVfZKkikvXVddLuWMbcSCA1Q==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(frontend) bump react-query-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:00:48 +01:00
"@tanstack/query-core": "5.64.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
},
"funding": {
"type": "github",
"url": "https://github.com/sponsors/tannerlinsley"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"react": "^18 || ^19"
♻️(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
}
},
"node_modules/@tanstack/react-query-devtools": {
⬆️(frontend) bump react-query-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:00:48 +01:00
"version": "5.64.2",
"resolved": "https://registry.npmjs.org/@tanstack/react-query-devtools/-/react-query-devtools-5.64.2.tgz",
"integrity": "sha512-+ZjJVnPzc8BUV/Eklu2k9T/IAyAyvwoCHqOaOrk2sbU33LFhM52BpX4eyENXn0bx5LwV3DJZgEQlIzucoemfGQ==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(frontend) bump react-query-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:00:48 +01:00
"@tanstack/query-devtools": "5.64.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
},
"funding": {
"type": "github",
"url": "https://github.com/sponsors/tannerlinsley"
},
"peerDependencies": {
⬆️(frontend) bump react-query-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:00:48 +01:00
"@tanstack/react-query": "^5.64.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
"react": "^18 || ^19"
}
},
"node_modules/@ts-morph/common": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.25.0",
"resolved": "https://registry.npmjs.org/@ts-morph/common/-/common-0.25.0.tgz",
"integrity": "sha512-kMnZz+vGGHi4GoHnLmMhGNjm44kGtKUXGnOvrKmMwAuvNjM/PgKVGfUnL7IDvK7Jb2QQ82jq3Zmp04Gy+r3Dkg==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"minimatch": "^9.0.4",
"path-browserify": "^1.0.1",
"tinyglobby": "^0.2.9"
♻️(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
}
},
"node_modules/@types/babel__core": {
"version": "7.20.5",
"resolved": "https://registry.npmjs.org/@types/babel__core/-/babel__core-7.20.5.tgz",
"integrity": "sha512-qoQprZvz5wQFJwMDqeseRXWv3rqMvhgpbXFfVyWhbx9X47POIA6i/+dXefEmZKoAgOaTdaIgNSMqMIU61yRyzA==",
"dev": true,
"dependencies": {
"@babel/parser": "^7.20.7",
"@babel/types": "^7.20.7",
"@types/babel__generator": "*",
"@types/babel__template": "*",
"@types/babel__traverse": "*"
}
},
"node_modules/@types/babel__generator": {
"version": "7.6.8",
"resolved": "https://registry.npmjs.org/@types/babel__generator/-/babel__generator-7.6.8.tgz",
"integrity": "sha512-ASsj+tpEDsEiFr1arWrlN6V3mdfjRMZt6LtK/Vp/kreFLnr5QH5+DhvD5nINYZXzwJvXeGq+05iUXcAzVrqWtw==",
"dev": true,
"dependencies": {
"@babel/types": "^7.0.0"
}
},
"node_modules/@types/babel__template": {
"version": "7.4.4",
"resolved": "https://registry.npmjs.org/@types/babel__template/-/babel__template-7.4.4.tgz",
"integrity": "sha512-h/NUaSyG5EyxBIp8YRxo4RMe2/qQgvyowRwVMzhYhBCONbW8PUsg4lkFMrhgZhUe5z3L3MiLDuvyJ/CaPa2A8A==",
"dev": true,
"dependencies": {
"@babel/parser": "^7.1.0",
"@babel/types": "^7.0.0"
}
},
"node_modules/@types/babel__traverse": {
"version": "7.20.6",
"resolved": "https://registry.npmjs.org/@types/babel__traverse/-/babel__traverse-7.20.6.tgz",
"integrity": "sha512-r1bzfrm0tomOI8g1SzvCaQHo6Lcv6zu0EA+W2kHrt8dyrHQxGzBBL4kdkzIS+jBMV+EYcMAEAqXqYaLJq5rOZg==",
"dev": true,
"dependencies": {
"@babel/types": "^7.20.7"
}
},
"node_modules/@types/estree": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "1.0.6",
"resolved": "https://registry.npmjs.org/@types/estree/-/estree-1.0.6.tgz",
"integrity": "sha512-AYnb1nQyY49te+VRAVgmzfcgjYS91mY5P0TKUDCLEM+gNnA+3T6rWITXRLYCpahpqSQbN5cE+gHpnPyXjHWxcw==",
♻️(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": true
},
🌐(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
"node_modules/@types/minimatch": {
"version": "3.0.5",
"resolved": "https://registry.npmjs.org/@types/minimatch/-/minimatch-3.0.5.tgz",
"integrity": "sha512-Klz949h02Gz2uZCMGwDUSDS1YBlTdDDgbWHi+81l29tQALUtvz4rAYi5uoVhE5Lagoq6DeqAUlbrHvW/mXDgdQ=="
},
♻️(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
"node_modules/@types/node": {
⬆️(dependencies) update js dependencies
2025-01-27 14:32:11 +00:00
"version": "22.10.10",
"resolved": "https://registry.npmjs.org/@types/node/-/node-22.10.10.tgz",
"integrity": "sha512-X47y/mPNzxviAGY5TcYPtYL8JsY3kAq2n8fMmKoRCxq/c4v4pyGNCzM2R6+M5/umG4ZfHuT+sgqDYqWc9rJ6ww==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"undici-types": "~6.20.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
}
},
"node_modules/@types/prop-types": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "15.7.14",
"resolved": "https://registry.npmjs.org/@types/prop-types/-/prop-types-15.7.14.tgz",
"integrity": "sha512-gNMvNH49DJ7OJYv+KAKn0Xp45p8PLl6zo2YnvDIbTd4J6MER2BmWN49TG7n9LvkyihINxeKW8+3bfS2yDC9dzQ==",
"devOptional": true,
"license": "MIT"
♻️(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
},
"node_modules/@types/react": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "18.3.12",
"resolved": "https://registry.npmjs.org/@types/react/-/react-18.3.12.tgz",
"integrity": "sha512-D2wOSq/d6Agt28q7rSI3jhU7G6aiuzljDGZ2hTZHIkrTLUI+AF3WMeKkEZ9nN2fkBAlcktT6vcZjDFiIhMYEQw==",
♻️(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
"devOptional": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
"@types/prop-types": "*",
"csstype": "^3.0.2"
}
},
"node_modules/@types/react-dom": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "18.3.1",
"resolved": "https://registry.npmjs.org/@types/react-dom/-/react-dom-18.3.1.tgz",
"integrity": "sha512-qW1Mfv8taImTthu4KoXgDfLuk4bydU6Q/TkADnDWWHwi4NX4BR+LWfTp2sVmTqRrsHvyDDTelgelxJ+SsejKKQ==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
"@types/react": "*"
}
},
🌐(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
"node_modules/@types/symlink-or-copy": {
"version": "1.2.2",
"resolved": "https://registry.npmjs.org/@types/symlink-or-copy/-/symlink-or-copy-1.2.2.tgz",
"integrity": "sha512-MQ1AnmTLOncwEf9IVU+B2e4Hchrku5N67NkgcAHW0p3sdzPe0FNMANxEm6OJUzPniEQGkeT3OROLlCwZJLWFZA=="
},
♻️(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
"node_modules/@typescript-eslint/eslint-plugin": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "8.21.0",
"resolved": "https://registry.npmjs.org/@typescript-eslint/eslint-plugin/-/eslint-plugin-8.21.0.tgz",
"integrity": "sha512-eTH+UOR4I7WbdQnG4Z48ebIA6Bgi7WO8HvFEneeYBxG8qCOYgTOFPSg6ek9ITIDvGjDQzWHcoWHCDO2biByNzA==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
"@eslint-community/regexpp": "^4.10.0",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@typescript-eslint/scope-manager": "8.21.0",
"@typescript-eslint/type-utils": "8.21.0",
"@typescript-eslint/utils": "8.21.0",
"@typescript-eslint/visitor-keys": "8.21.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
"graphemer": "^1.4.0",
"ignore": "^5.3.1",
"natural-compare": "^1.4.0",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"ts-api-utils": "^2.0.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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": "^18.18.0 || ^20.9.0 || >=21.1.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
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/typescript-eslint"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"@typescript-eslint/parser": "^8.0.0 || ^8.0.0-alpha.0",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"eslint": "^8.57.0 || ^9.0.0",
"typescript": ">=4.8.4 <5.8.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
}
},
"node_modules/@typescript-eslint/parser": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "8.21.0",
"resolved": "https://registry.npmjs.org/@typescript-eslint/parser/-/parser-8.21.0.tgz",
"integrity": "sha512-Wy+/sdEH9kI3w9civgACwabHbKl+qIOu0uFZ9IMKzX3Jpv9og0ZBJrZExGrPpFAY7rWsXuxs5e7CPPP17A4eYA==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@typescript-eslint/scope-manager": "8.21.0",
"@typescript-eslint/types": "8.21.0",
"@typescript-eslint/typescript-estree": "8.21.0",
"@typescript-eslint/visitor-keys": "8.21.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
"debug": "^4.3.4"
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": "^18.18.0 || ^20.9.0 || >=21.1.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
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/typescript-eslint"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"eslint": "^8.57.0 || ^9.0.0",
"typescript": ">=4.8.4 <5.8.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
}
},
"node_modules/@typescript-eslint/scope-manager": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "8.21.0",
"resolved": "https://registry.npmjs.org/@typescript-eslint/scope-manager/-/scope-manager-8.21.0.tgz",
"integrity": "sha512-G3IBKz0/0IPfdeGRMbp+4rbjfSSdnGkXsM/pFZA8zM9t9klXDnB/YnKOBQ0GoPmoROa4bCq2NeHgJa5ydsQ4mA==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@typescript-eslint/types": "8.21.0",
"@typescript-eslint/visitor-keys": "8.21.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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": "^18.18.0 || ^20.9.0 || >=21.1.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
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/typescript-eslint"
}
},
"node_modules/@typescript-eslint/type-utils": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "8.21.0",
"resolved": "https://registry.npmjs.org/@typescript-eslint/type-utils/-/type-utils-8.21.0.tgz",
"integrity": "sha512-95OsL6J2BtzoBxHicoXHxgk3z+9P3BEcQTpBKriqiYzLKnM2DeSqs+sndMKdamU8FosiadQFT3D+BSL9EKnAJQ==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@typescript-eslint/typescript-estree": "8.21.0",
"@typescript-eslint/utils": "8.21.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
"debug": "^4.3.4",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"ts-api-utils": "^2.0.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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": "^18.18.0 || ^20.9.0 || >=21.1.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
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/typescript-eslint"
},
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"peerDependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"eslint": "^8.57.0 || ^9.0.0",
"typescript": ">=4.8.4 <5.8.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
}
},
"node_modules/@typescript-eslint/types": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "8.21.0",
"resolved": "https://registry.npmjs.org/@typescript-eslint/types/-/types-8.21.0.tgz",
"integrity": "sha512-PAL6LUuQwotLW2a8VsySDBwYMm129vFm4tMVlylzdoTybTHaAi0oBp7Ac6LhSrHHOdLM3efH+nAR6hAWoMF89A==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": "^18.18.0 || ^20.9.0 || >=21.1.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
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/typescript-eslint"
}
},
"node_modules/@typescript-eslint/typescript-estree": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "8.21.0",
"resolved": "https://registry.npmjs.org/@typescript-eslint/typescript-estree/-/typescript-estree-8.21.0.tgz",
"integrity": "sha512-x+aeKh/AjAArSauz0GiQZsjT8ciadNMHdkUSwBB9Z6PrKc/4knM4g3UfHml6oDJmKC88a6//cdxnO/+P2LkMcg==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@typescript-eslint/types": "8.21.0",
"@typescript-eslint/visitor-keys": "8.21.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
"debug": "^4.3.4",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"fast-glob": "^3.3.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
"is-glob": "^4.0.3",
"minimatch": "^9.0.4",
"semver": "^7.6.0",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"ts-api-utils": "^2.0.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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": "^18.18.0 || ^20.9.0 || >=21.1.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
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/typescript-eslint"
},
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"peerDependencies": {
"typescript": ">=4.8.4 <5.8.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
}
},
"node_modules/@typescript-eslint/utils": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "8.21.0",
"resolved": "https://registry.npmjs.org/@typescript-eslint/utils/-/utils-8.21.0.tgz",
"integrity": "sha512-xcXBfcq0Kaxgj7dwejMbFyq7IOHgpNMtVuDveK7w3ZGwG9owKzhALVwKpTF2yrZmEwl9SWdetf3fxNzJQaVuxw==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
"@eslint-community/eslint-utils": "^4.4.0",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@typescript-eslint/scope-manager": "8.21.0",
"@typescript-eslint/types": "8.21.0",
"@typescript-eslint/typescript-estree": "8.21.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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": "^18.18.0 || ^20.9.0 || >=21.1.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
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/typescript-eslint"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"eslint": "^8.57.0 || ^9.0.0",
"typescript": ">=4.8.4 <5.8.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
}
},
"node_modules/@typescript-eslint/visitor-keys": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "8.21.0",
"resolved": "https://registry.npmjs.org/@typescript-eslint/visitor-keys/-/visitor-keys-8.21.0.tgz",
"integrity": "sha512-BkLMNpdV6prozk8LlyK/SOoWLmUFi+ZD+pcqti9ILCbVvHGk1ui1g4jJOc2WDLaeExz2qWwojxlPce5PljcT3w==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@typescript-eslint/types": "8.21.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"eslint-visitor-keys": "^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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": "^18.18.0 || ^20.9.0 || >=21.1.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
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/typescript-eslint"
}
},
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"node_modules/@typescript-eslint/visitor-keys/node_modules/eslint-visitor-keys": {
"version": "4.2.0",
"resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-4.2.0.tgz",
"integrity": "sha512-UyLnSehNt62FFhSwjZlHmeokpRK59rcz29j+F1/aDgbkbRTk7wIc9XzdoasMUbRNKDM0qQt/+BJ4BrpFeABemw==",
"dev": true,
"license": "Apache-2.0",
"engines": {
"node": "^18.18.0 || ^20.9.0 || >=21.1.0"
},
"funding": {
"url": "https://opencollective.com/eslint"
}
},
♻️(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
"node_modules/@ungap/structured-clone": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/@ungap/structured-clone/-/structured-clone-1.2.0.tgz",
"integrity": "sha512-zuVdFrMJiuCDQUMCzQaD6KL28MjnqqN8XnAqiEq9PNm/hCPTSGfrXCOfwj1ow4LFb/tNymJPwsNbVePc1xFqrQ==",
"dev": true
},
"node_modules/@vitejs/plugin-react": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "4.3.4",
"resolved": "https://registry.npmjs.org/@vitejs/plugin-react/-/plugin-react-4.3.4.tgz",
"integrity": "sha512-SCCPBJtYLdE8PX/7ZQAs1QAZ8Jqwih+0VBLum1EGqmCCQal+MIUqLCzj3ZUy8ufbC0cAM4LRlSTm7IQJwWT4ug==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@babel/core": "^7.26.0",
"@babel/plugin-transform-react-jsx-self": "^7.25.9",
"@babel/plugin-transform-react-jsx-source": "^7.25.9",
♻️(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
"@types/babel__core": "^7.20.5",
"react-refresh": "^0.14.2"
},
"engines": {
"node": "^14.18.0 || >=16.0.0"
},
"peerDependencies": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"vite": "^4.2.0 || ^5.0.0 || ^6.0.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
}
},
"node_modules/@vue/compiler-core": {
"version": "3.4.19",
"resolved": "https://registry.npmjs.org/@vue/compiler-core/-/compiler-core-3.4.19.tgz",
"integrity": "sha512-gj81785z0JNzRcU0Mq98E56e4ltO1yf8k5PQ+tV/7YHnbZkrM0fyFyuttnN8ngJZjbpofWE/m4qjKBiLl8Ju4w==",
"dev": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
♻️(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
"dependencies": {
"@babel/parser": "^7.23.9",
"@vue/shared": "3.4.19",
"entities": "^4.5.0",
"estree-walker": "^2.0.2",
"source-map-js": "^1.0.2"
}
},
"node_modules/@vue/compiler-dom": {
"version": "3.4.19",
"resolved": "https://registry.npmjs.org/@vue/compiler-dom/-/compiler-dom-3.4.19.tgz",
"integrity": "sha512-vm6+cogWrshjqEHTzIDCp72DKtea8Ry/QVpQRYoyTIg9k7QZDX6D8+HGURjtmatfgM8xgCFtJJaOlCaRYRK3QA==",
"dev": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
♻️(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
"dependencies": {
"@vue/compiler-core": "3.4.19",
"@vue/shared": "3.4.19"
}
},
"node_modules/@vue/compiler-sfc": {
"version": "3.4.19",
"resolved": "https://registry.npmjs.org/@vue/compiler-sfc/-/compiler-sfc-3.4.19.tgz",
"integrity": "sha512-LQ3U4SN0DlvV0xhr1lUsgLCYlwQfUfetyPxkKYu7dkfvx7g3ojrGAkw0AERLOKYXuAGnqFsEuytkdcComei3Yg==",
"dev": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
♻️(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
"dependencies": {
"@babel/parser": "^7.23.9",
"@vue/compiler-core": "3.4.19",
"@vue/compiler-dom": "3.4.19",
"@vue/compiler-ssr": "3.4.19",
"@vue/shared": "3.4.19",
"estree-walker": "^2.0.2",
"magic-string": "^0.30.6",
"postcss": "^8.4.33",
"source-map-js": "^1.0.2"
}
},
"node_modules/@vue/compiler-ssr": {
"version": "3.4.19",
"resolved": "https://registry.npmjs.org/@vue/compiler-ssr/-/compiler-ssr-3.4.19.tgz",
"integrity": "sha512-P0PLKC4+u4OMJ8sinba/5Z/iDT84uMRRlrWzadgLA69opCpI1gG4N55qDSC+dedwq2fJtzmGald05LWR5TFfLw==",
"dev": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
♻️(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
"dependencies": {
"@vue/compiler-dom": "3.4.19",
"@vue/shared": "3.4.19"
}
},
"node_modules/@vue/shared": {
"version": "3.4.19",
"resolved": "https://registry.npmjs.org/@vue/shared/-/shared-3.4.19.tgz",
"integrity": "sha512-/KliRRHMF6LoiThEy+4c1Z4KB/gbPrGjWwJR+crg2otgrf/egKzRaCPvJ51S5oetgsgXLfc4Rm5ZgrKHZrtMSw==",
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"dev": true,
"license": "MIT"
♻️(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
},
"node_modules/acorn": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "8.12.1",
"resolved": "https://registry.npmjs.org/acorn/-/acorn-8.12.1.tgz",
"integrity": "sha512-tcpGyI9zbizT9JbV6oYE477V6mTlXvvi0T0G3SNIYE2apm/G5huBa1+K89VGeovbg+jycCrfhl3ADxErOuO6Jg==",
♻️(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": true,
"bin": {
"acorn": "bin/acorn"
},
"engines": {
"node": ">=0.4.0"
}
},
"node_modules/acorn-jsx": {
"version": "5.3.2",
"resolved": "https://registry.npmjs.org/acorn-jsx/-/acorn-jsx-5.3.2.tgz",
"integrity": "sha512-rq9s+JNhf0IChjtDXxllJ7g41oZk5SlXtp0LHwyA5cejwn7vKmKp4pPri6YEePv2PU65sAsegbXtIinmDFDXgQ==",
"dev": true,
"peerDependencies": {
"acorn": "^6.0.0 || ^7.0.0 || ^8.0.0"
}
},
"node_modules/ajv": {
"version": "6.12.6",
"resolved": "https://registry.npmjs.org/ajv/-/ajv-6.12.6.tgz",
"integrity": "sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==",
"dev": true,
"dependencies": {
"fast-deep-equal": "^3.1.1",
"fast-json-stable-stringify": "^2.0.0",
"json-schema-traverse": "^0.4.1",
"uri-js": "^4.2.2"
},
"funding": {
"type": "github",
"url": "https://github.com/sponsors/epoberezkin"
}
},
"node_modules/ansi-colors": {
"version": "4.1.3",
"resolved": "https://registry.npmjs.org/ansi-colors/-/ansi-colors-4.1.3.tgz",
"integrity": "sha512-/6w/C21Pm1A7aZitlI5Ni/2J6FFQN8i1Cvz3kHABAAbw93v/NlvKdVOqz7CCWz/3iv/JplRSEEZ83XION15ovw==",
"dev": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
♻️(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
"engines": {
"node": ">=6"
}
},
"node_modules/ansi-regex": {
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
"integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
"dev": true,
"engines": {
"node": ">=8"
}
},
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"node_modules/ansi-styles": {
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz",
"integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==",
"dev": true,
"license": "MIT",
"dependencies": {
"color-convert": "^2.0.1"
},
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/chalk/ansi-styles?sponsor=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
"node_modules/anymatch": {
"version": "3.1.3",
"resolved": "https://registry.npmjs.org/anymatch/-/anymatch-3.1.3.tgz",
"integrity": "sha512-KMReFUr0B4t+D+OBkjR3KYqvocp2XaSzO55UcB6mgQMd3KbcE+mWTyvVV7D/zsdEbNnV6acZUutkiHQXvTr1Rw==",
"dependencies": {
"normalize-path": "^3.0.0",
"picomatch": "^2.0.4"
},
"engines": {
"node": ">= 8"
}
},
"node_modules/argparse": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/argparse/-/argparse-2.0.1.tgz",
🌐(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
"integrity": "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q=="
♻️(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
},
"node_modules/aria-query": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "5.3.2",
"resolved": "https://registry.npmjs.org/aria-query/-/aria-query-5.3.2.tgz",
"integrity": "sha512-COROpnaoap1E2F000S62r6A60uHZnmlvomhfyT2DlTcrY1OrBKn2UhH7qn5wTC9zMvD0AY7csdPSNwKP+7WiQw==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"engines": {
"node": ">= 0.4"
♻️(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
}
},
"node_modules/array-buffer-byte-length": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/array-buffer-byte-length/-/array-buffer-byte-length-1.0.1.tgz",
"integrity": "sha512-ahC5W1xgou+KTXix4sAO8Ki12Q+jf4i0+tmk3sC+zgcynshkHxzpXdImBehiUYKKKDwvfFiJl1tZt6ewscS1Mg==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.5",
"is-array-buffer": "^3.0.4"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/array-includes": {
"version": "3.1.8",
"resolved": "https://registry.npmjs.org/array-includes/-/array-includes-3.1.8.tgz",
"integrity": "sha512-itaWrbYbqpGXkGhZPGUulwnhVf5Hpy1xiCFsGqyIGglbBxmG5vSjxQen3/WGOjPpNEv1RtBLKxbmVXm8HpJStQ==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.7",
"define-properties": "^1.2.1",
"es-abstract": "^1.23.2",
"es-object-atoms": "^1.0.0",
"get-intrinsic": "^1.2.4",
"is-string": "^1.0.7"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/array.prototype.flat": {
"version": "1.3.2",
"resolved": "https://registry.npmjs.org/array.prototype.flat/-/array.prototype.flat-1.3.2.tgz",
"integrity": "sha512-djYB+Zx2vLewY8RWlNCUdHjDXs2XOgm602S9E7P/UpHgfeHL00cRiIF+IN/G/aUJ7kGPb6yO/ErDI5V2s8iycA==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.2",
"define-properties": "^1.2.0",
"es-abstract": "^1.22.1",
"es-shim-unscopables": "^1.0.0"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/array.prototype.flatmap": {
"version": "1.3.2",
"resolved": "https://registry.npmjs.org/array.prototype.flatmap/-/array.prototype.flatmap-1.3.2.tgz",
"integrity": "sha512-Ewyx0c9PmpcsByhSW4r+9zDU7sGjFc86qf/kKtuSCRdhfbk0SNLLkaT5qvcHnRGgc5NP/ly/y+qkXkqONX54CQ==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.2",
"define-properties": "^1.2.0",
"es-abstract": "^1.22.1",
"es-shim-unscopables": "^1.0.0"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/arraybuffer.prototype.slice": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/arraybuffer.prototype.slice/-/arraybuffer.prototype.slice-1.0.3.tgz",
"integrity": "sha512-bMxMKAjg13EBSVscxTaYA4mRc5t1UAXa2kXiGTNfZ079HIWXEkKmkgFrh/nJqamaLSrXO5H4WFFkPEaLJWbs3A==",
"dev": true,
"dependencies": {
"array-buffer-byte-length": "^1.0.1",
"call-bind": "^1.0.5",
"define-properties": "^1.2.1",
"es-abstract": "^1.22.3",
"es-errors": "^1.2.1",
"get-intrinsic": "^1.2.3",
"is-array-buffer": "^3.0.4",
"is-shared-array-buffer": "^1.0.2"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/ast-types-flow": {
"version": "0.0.8",
"resolved": "https://registry.npmjs.org/ast-types-flow/-/ast-types-flow-0.0.8.tgz",
"integrity": "sha512-OH/2E5Fg20h2aPrbe+QL8JZQFko0YZaF+j4mnQ7BGhfavO7OpSLa8a0y9sBwomHdSbkhTS8TQNayBfnW5DwbvQ==",
"dev": true
},
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"node_modules/astral-regex": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/astral-regex/-/astral-regex-2.0.0.tgz",
"integrity": "sha512-Z7tMw1ytTXt5jqMcOP+OQteU1VuNK9Y02uuJtKQ1Sv69jXQKKg5cibLwGJow8yzZP+eAc18EmLGPal0bp36rvQ==",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=8"
}
},
♻️(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
"node_modules/available-typed-arrays": {
"version": "1.0.7",
"resolved": "https://registry.npmjs.org/available-typed-arrays/-/available-typed-arrays-1.0.7.tgz",
"integrity": "sha512-wvUjBtSGN7+7SjNpq/9M2Tg350UZD3q62IFZLbRAR1bSMlCo1ZaeW+BJ+D090e4hIIZLBcTDWe4Mh4jvUDajzQ==",
"dev": true,
"dependencies": {
"possible-typed-array-names": "^1.0.0"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/axe-core": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "4.10.0",
"resolved": "https://registry.npmjs.org/axe-core/-/axe-core-4.10.0.tgz",
"integrity": "sha512-Mr2ZakwQ7XUAjp7pAwQWRhhK8mQQ6JAaNWSjmjxil0R8BPioMtQsTLOolGYkji1rcL++3dCqZA3zWqpT+9Ew6g==",
♻️(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": true,
"engines": {
"node": ">=4"
}
},
"node_modules/axobject-query": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/axobject-query/-/axobject-query-4.1.0.tgz",
"integrity": "sha512-qIj0G9wZbMGNLjLmg1PT6v2mE9AH2zlnADJD/2tC6E00hgmhUOfEB6greHPAfLRSufHqROIUTkw6E+M3lH0PTQ==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"engines": {
"node": ">= 0.4"
♻️(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
}
},
🌐(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
"node_modules/b4a": {
"version": "1.6.6",
"resolved": "https://registry.npmjs.org/b4a/-/b4a-1.6.6.tgz",
"integrity": "sha512-5Tk1HLk6b6ctmjIkAcU/Ujv/1WqiDl0F0JdRCR80VsOcUlHcu7pWeWRlOqQLHfDEsVx9YH/aif5AG4ehoCtTmg=="
},
♻️(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
"node_modules/balanced-match": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-1.0.2.tgz",
🌐(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
"integrity": "sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw=="
},
"node_modules/bare-events": {
"version": "2.4.2",
"resolved": "https://registry.npmjs.org/bare-events/-/bare-events-2.4.2.tgz",
"integrity": "sha512-qMKFd2qG/36aA4GwvKq8MxnPgCQAmBWmSyLWsJcbn8v03wvIPQ/hG1Ms8bPzndZxMDoHpxez5VOS+gC9Yi24/Q==",
"optional": true
},
"node_modules/base64-js": {
"version": "1.5.1",
"resolved": "https://registry.npmjs.org/base64-js/-/base64-js-1.5.1.tgz",
"integrity": "sha512-AKpaYlHn8t4SVbOHCy+b5+KKgvR4vrsD8vbvrbiQJps7fKDTkjkDry6ji0rUJjC0kzbNePLwzxq8iypo41qeWA==",
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
]
♻️(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
},
"node_modules/binary-extensions": {
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/binary-extensions/-/binary-extensions-2.3.0.tgz",
"integrity": "sha512-Ceh+7ox5qe7LJuLHoY0feh3pHuUDHAcRUeyL2VYghZwfpkNIy/+8Ocg0a3UuSoYzavmylwuLWQOf3hl0jjMMIw==",
"dev": true,
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
🌐(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
"node_modules/bl": {
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/bl/-/bl-5.1.0.tgz",
"integrity": "sha512-tv1ZJHLfTDnXE6tMHv73YgSJaWR2AFuPwMntBe7XL/GBFHnT0CLnsHMogfk5+GzCDC5ZWarSCYaIGATZt9dNsQ==",
"dependencies": {
"buffer": "^6.0.3",
"inherits": "^2.0.4",
"readable-stream": "^3.4.0"
}
},
"node_modules/bl/node_modules/readable-stream": {
"version": "3.6.2",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-3.6.2.tgz",
"integrity": "sha512-9u/sniCrY3D5WdsERHzHE4G2YCXqoG5FTHUiCC4SIbr6XcLZBY05ya9EKjYek9O5xOAwjGq+1JdGBAS7Q9ScoA==",
"dependencies": {
"inherits": "^2.0.3",
"string_decoder": "^1.1.1",
"util-deprecate": "^1.0.1"
},
"engines": {
"node": ">= 6"
}
},
"node_modules/boolbase": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/boolbase/-/boolbase-1.0.0.tgz",
"integrity": "sha512-JZOSA7Mo9sNGB8+UjSgzdLtokWAky1zbztM3WRLCbZ70/3cTANmQmOdR7y2g+J0e2WXywy1yS468tY+IruqEww=="
},
♻️(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
"node_modules/brace-expansion": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.0.1.tgz",
"integrity": "sha512-XnAIvQ8eM+kC6aULx6wuQiwVsnzsi9d3WxzV3FpWTGA19F621kwdbsAcFKXgKUHZWsy+mY6iL1sHTxWEFCytDA==",
"dev": true,
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
♻️(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
"dependencies": {
"balanced-match": "^1.0.0"
}
},
"node_modules/braces": {
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/braces/-/braces-3.0.3.tgz",
"integrity": "sha512-yQbXgO/OSZVD2IsiLlro+7Hf6Q18EJrKSEsdoMzKePKXct3gvD8oLcOQdIzGupr5Fj+EDe8gO/lxc1BzfMpxvA==",
"dev": true,
"dependencies": {
"fill-range": "^7.1.1"
},
"engines": {
"node": ">=8"
}
},
🌐(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
"node_modules/broccoli-node-api": {
"version": "1.7.0",
"resolved": "https://registry.npmjs.org/broccoli-node-api/-/broccoli-node-api-1.7.0.tgz",
"integrity": "sha512-QIqLSVJWJUVOhclmkmypJJH9u9s/aWH4+FH6Q6Ju5l+Io4dtwqdPUNmDfw40o6sxhbZHhqGujDJuHTML1wG8Yw=="
},
"node_modules/broccoli-node-info": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/broccoli-node-info/-/broccoli-node-info-2.2.0.tgz",
"integrity": "sha512-VabSGRpKIzpmC+r+tJueCE5h8k6vON7EIMMWu6d/FyPdtijwLQ7QvzShEw+m3mHoDzUaj/kiZsDYrS8X2adsBg==",
"engines": {
"node": "8.* || >= 10.*"
}
},
"node_modules/broccoli-output-wrapper": {
"version": "3.2.5",
"resolved": "https://registry.npmjs.org/broccoli-output-wrapper/-/broccoli-output-wrapper-3.2.5.tgz",
"integrity": "sha512-bQAtwjSrF4Nu0CK0JOy5OZqw9t5U0zzv2555EA/cF8/a8SLDTIetk9UgrtMVw7qKLKdSpOZ2liZNeZZDaKgayw==",
"dependencies": {
"fs-extra": "^8.1.0",
"heimdalljs-logger": "^0.1.10",
"symlink-or-copy": "^1.2.0"
},
"engines": {
"node": "10.* || >= 12.*"
}
},
"node_modules/broccoli-output-wrapper/node_modules/fs-extra": {
"version": "8.1.0",
"resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-8.1.0.tgz",
"integrity": "sha512-yhlQgA6mnOJUKOsRUFsgJdQCvkKhcz8tlZG5HBQfReYZy46OwLcY+Zia0mtdHsOo9y/hP+CxMN0TU9QxoOtG4g==",
"dependencies": {
"graceful-fs": "^4.2.0",
"jsonfile": "^4.0.0",
"universalify": "^0.1.0"
},
"engines": {
"node": ">=6 <7 || >=8"
}
},
"node_modules/broccoli-output-wrapper/node_modules/jsonfile": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-4.0.0.tgz",
"integrity": "sha512-m6F1R3z8jjlf2imQHS2Qez5sjKWQzbuuhuJ/FKYFRZvPE3PuHcSMVZzfsLhGVOkfd20obL5SWEBew5ShlquNxg==",
"optionalDependencies": {
"graceful-fs": "^4.1.6"
}
},
"node_modules/broccoli-output-wrapper/node_modules/universalify": {
"version": "0.1.2",
"resolved": "https://registry.npmjs.org/universalify/-/universalify-0.1.2.tgz",
"integrity": "sha512-rBJeI5CXAlmy1pV+617WB9J63U6XcazHHF2f2dbJix4XzpUF0RS3Zbj0FGIOCAva5P/d/GBOYaACQ1w+0azUkg==",
"engines": {
"node": ">= 4.0.0"
}
},
"node_modules/broccoli-plugin": {
"version": "4.0.7",
"resolved": "https://registry.npmjs.org/broccoli-plugin/-/broccoli-plugin-4.0.7.tgz",
"integrity": "sha512-a4zUsWtA1uns1K7p9rExYVYG99rdKeGRymW0qOCNkvDPHQxVi3yVyJHhQbM3EZwdt2E0mnhr5e0c/bPpJ7p3Wg==",
"dependencies": {
"broccoli-node-api": "^1.7.0",
"broccoli-output-wrapper": "^3.2.5",
"fs-merger": "^3.2.1",
"promise-map-series": "^0.3.0",
"quick-temp": "^0.1.8",
"rimraf": "^3.0.2",
"symlink-or-copy": "^1.3.1"
},
"engines": {
"node": "10.* || >= 12.*"
}
},
♻️(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
"node_modules/browserslist": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "4.23.3",
"resolved": "https://registry.npmjs.org/browserslist/-/browserslist-4.23.3.tgz",
"integrity": "sha512-btwCFJVjI4YWDNfau8RhZ+B1Q/VLoUITrm3RlP6y1tYGWIOa+InuYiRGXUBXo8nA1qKmHMyLB/iVQg5TT4eFoA==",
♻️(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": true,
"funding": [
{
"type": "opencollective",
"url": "https://opencollective.com/browserslist"
},
{
"type": "tidelift",
"url": "https://tidelift.com/funding/github/npm/browserslist"
},
{
"type": "github",
"url": "https://github.com/sponsors/ai"
}
],
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"caniuse-lite": "^1.0.30001646",
"electron-to-chromium": "^1.5.4",
"node-releases": "^2.0.18",
"update-browserslist-db": "^1.1.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
},
"bin": {
"browserslist": "cli.js"
},
"engines": {
"node": "^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7"
}
},
🌐(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
"node_modules/buffer": {
"version": "6.0.3",
"resolved": "https://registry.npmjs.org/buffer/-/buffer-6.0.3.tgz",
"integrity": "sha512-FTiCpNxtwiZZHEZbcbTIcZjERVICn9yq/pDFkTl95/AxzD1naBctN7YO68riM/gLSDY7sdrMby8hofADYuuqOA==",
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
],
"dependencies": {
"base64-js": "^1.3.1",
"ieee754": "^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
"node_modules/bundle-n-require": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/bundle-n-require/-/bundle-n-require-1.1.1.tgz",
"integrity": "sha512-EB2wFjXF106LQLe/CYnKCMCdLeTW47AtcEtUfiqAOgr2a08k0+YgRklur2aLfEYHlhz6baMskZ8L2U92Hh0vyA==",
"dev": true,
"dependencies": {
"esbuild": "^0.20.0",
"node-eval": "^2.0.0"
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/cac": {
"version": "6.7.14",
"resolved": "https://registry.npmjs.org/cac/-/cac-6.7.14.tgz",
"integrity": "sha512-b6Ilus+c3RrdDk+JhLKUAQfzzgLEPy6wcXqS7f/xe1EETvsDP6GORG7SFuOs6cID5YkqchW/LXZbX5bc8j7ZcQ==",
♻️(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": true,
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=8"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/call-bind": {
"version": "1.0.7",
"resolved": "https://registry.npmjs.org/call-bind/-/call-bind-1.0.7.tgz",
"integrity": "sha512-GHTSNSYICQ7scH7sZ+M2rFopRoLh8t2bLSW6BbgrtLsahOIB5iyAVJf9GjWK3cYTDaMj4XdBpM1cA6pIS0Kv2w==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
"es-define-property": "^1.0.0",
"es-errors": "^1.3.0",
"function-bind": "^1.1.2",
"get-intrinsic": "^1.2.4",
"set-function-length": "^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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/callsites": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/callsites/-/callsites-3.1.0.tgz",
"integrity": "sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==",
♻️(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": true,
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=6"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/caniuse-api": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/caniuse-api/-/caniuse-api-3.0.0.tgz",
"integrity": "sha512-bsTwuIg/BZZK/vreVTYYbSWoe2F+71P7K5QGEX+pT250DZbfU1MQ5prOKpPR+LL6uWKK3KMwMCAS74QB3Um1uw==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
"browserslist": "^4.0.0",
"caniuse-lite": "^1.0.0",
"lodash.memoize": "^4.1.2",
"lodash.uniq": "^4.5.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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/caniuse-lite": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "1.0.30001692",
"resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001692.tgz",
"integrity": "sha512-A95VKan0kdtrsnMubMKxEKUKImOPSuCpYgxSQBo036P5YYgVIcOYJEgt/txJWqObiRQeISNCfef9nvlQ0vbV7A==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"funding": [
{
"type": "opencollective",
"url": "https://opencollective.com/browserslist"
},
{
"type": "tidelift",
"url": "https://tidelift.com/funding/github/npm/caniuse-lite"
},
{
"type": "github",
"url": "https://github.com/sponsors/ai"
}
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
],
"license": "CC-BY-4.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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/cheerio": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/cheerio/-/cheerio-1.0.0.tgz",
"integrity": "sha512-quS9HgjQpdaXOvsZz82Oz7uxtXiy6UIsIQcpBj7HRw2M63Skasm9qlDocAM7jNuaxdhpPU7c4kJN+gA5MCu4ww==",
"dependencies": {
"cheerio-select": "^2.1.0",
"dom-serializer": "^2.0.0",
"domhandler": "^5.0.3",
"domutils": "^3.1.0",
"encoding-sniffer": "^0.2.0",
"htmlparser2": "^9.1.0",
"parse5": "^7.1.2",
"parse5-htmlparser2-tree-adapter": "^7.0.0",
"parse5-parser-stream": "^7.1.2",
"undici": "^6.19.5",
"whatwg-mimetype": "^4.0.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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18.17"
},
"funding": {
"url": "https://github.com/cheeriojs/cheerio?sponsor=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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/cheerio-select": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/cheerio-select/-/cheerio-select-2.1.0.tgz",
"integrity": "sha512-9v9kG0LvzrlcungtnJtpGNxY+fzECQKhK4EGJX2vByejiMX84MFNQw4UxPJl3bFbTMw+Dfs37XaIkCwTZfLh4g==",
"dependencies": {
"boolbase": "^1.0.0",
"css-select": "^5.1.0",
"css-what": "^6.1.0",
"domelementtype": "^2.3.0",
"domhandler": "^5.0.3",
"domutils": "^3.0.1"
},
"funding": {
"url": "https://github.com/sponsors/fb55"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/chokidar": {
"version": "3.6.0",
"resolved": "https://registry.npmjs.org/chokidar/-/chokidar-3.6.0.tgz",
"integrity": "sha512-7VT13fmjotKpGipCW9JEQAusEPE+Ei8nl6/g4FBAmIm0GOOLMua9NDDo/DWp0ZAxCr3cPq5ZpBqmPAQgDda2Pw==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
"anymatch": "~3.1.2",
"braces": "~3.0.2",
"glob-parent": "~5.1.2",
"is-binary-path": "~2.1.0",
"is-glob": "~4.0.1",
"normalize-path": "~3.0.0",
"readdirp": "~3.6.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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">= 8.10.0"
},
"funding": {
"url": "https://paulmillr.com/funding/"
},
"optionalDependencies": {
"fsevents": "~2.3.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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/chokidar/node_modules/glob-parent": {
"version": "5.1.2",
"resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz",
"integrity": "sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
"is-glob": "^4.0.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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">= 6"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/client-only": {
"version": "0.0.1",
"resolved": "https://registry.npmjs.org/client-only/-/client-only-0.0.1.tgz",
"integrity": "sha512-IV3Ou0jSMzZrd3pZ48nLkT9DA7Ag1pnPzaiQhpW7c3RbcqqzvzzVu+L8gfqMp/8IM2MQtSiqaCxrrcfu8I8rMA=="
},
"node_modules/clone": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/clone/-/clone-2.1.2.tgz",
"integrity": "sha512-3Pe/CF1Nn94hyhIYpjtiLhdCoEoz0DqQ+988E9gmeEdQZlojxnOb74wctFyuwWQHzqyf9X7C7MG8juUpqBJT8w==",
♻️(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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=0.8"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/clone-stats": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/clone-stats/-/clone-stats-1.0.0.tgz",
"integrity": "sha512-au6ydSpg6nsrigcZ4m8Bc9hxjeW+GJ8xh5G3BJCMt4WXe1H10UNaVOamqQTmrx1kjVuxAHIQSNU6hY4Nsn9/ag=="
♻️(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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/clsx": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/clsx/-/clsx-2.1.1.tgz",
"integrity": "sha512-eYm0QWBtUrBWZWG0d386OGAw16Z995PiOVo2B7bjWSbHedGl5e0ZWaq65kOGgUSNesEIDkB9ISbTg/JK9dhCZA==",
♻️(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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=6"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/code-block-writer": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "13.0.3",
"resolved": "https://registry.npmjs.org/code-block-writer/-/code-block-writer-13.0.3.tgz",
"integrity": "sha512-Oofo0pq3IKnsFtuHqSF7TqBfr71aeyZDVJ0HpmqB7FBM2qEigL0iPONSCZSO9pE9dZTAxANe5XHG9Uy0YMv8cg==",
"dev": true,
"license": "MIT"
},
"node_modules/color-convert": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz",
"integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==",
"dev": true,
"license": "MIT",
"dependencies": {
"color-name": "~1.1.4"
},
"engines": {
"node": ">=7.0.0"
}
},
"node_modules/color-name": {
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz",
"integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==",
"dev": true,
"license": "MIT"
♻️(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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/colors": {
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/colors/-/colors-1.4.0.tgz",
"integrity": "sha512-a+UqTh4kgZg/SlGvfbzDHpgRu7AAQOmmqRHJnxhRZICKFUT91brVhNNt58CMWU9PsBbv3PDCZUHbVxuDiH2mtA==",
♻️(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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=0.1.90"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/commander": {
"version": "12.1.0",
"resolved": "https://registry.npmjs.org/commander/-/commander-12.1.0.tgz",
"integrity": "sha512-Vw8qHK3bZM9y/P10u3Vib8o/DdkvA2OtPtZvD871QKjy74Wj1WSKFILMPRPSdUSx5RFK1arlJzEtA4PkFgnbuA==",
♻️(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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/concat-map": {
"version": "0.0.1",
"resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz",
"integrity": "sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg=="
},
"node_modules/confbox": {
"version": "0.1.7",
"resolved": "https://registry.npmjs.org/confbox/-/confbox-0.1.7.tgz",
"integrity": "sha512-uJcB/FKZtBMCJpK8MQji6bJHgu1tixKPxRLeGkNzBoOZzpnZUJm0jm2/sBDWcuBx1dYgxV4JU+g5hmNxCyAmdA==",
"dev": true
},
"node_modules/convert-source-map": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/convert-source-map/-/convert-source-map-2.0.0.tgz",
"integrity": "sha512-Kvp459HrV2FEJ1CAsi1Ku+MY3kasH19TFykTz2xWmMeq6bk2NU3XXvfJ+Q61m0xktWwt+1HSYf3JZsTms3aRJg=="
},
⬆️(frontend) update PostHog sdk Required by PostHog app, to benefits from latest survey features.
2024-11-17 22:53:11 +01:00
"node_modules/core-js": {
"version": "3.39.0",
"resolved": "https://registry.npmjs.org/core-js/-/core-js-3.39.0.tgz",
"integrity": "sha512-raM0ew0/jJUqkJ0E6e8UDtl+y/7ktFivgWvqw8dNSQeNWoSDLvQ1H/RN3aPXB9tBd4/FhyR4RDPGhsNIMsAn7g==",
"hasInstallScript": true,
"license": "MIT",
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/core-js"
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/core-util-is": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.3.tgz",
"integrity": "sha512-ZQBvi1DcpJ4GDqanjucZ2Hj3wEO5pZDS89BWbkcrvdxksJorwUDDZamX9ldFkp9aw2lmBDLgkObEA4DWNJ9FYQ=="
},
➕(frontend) add crisp-sdk-web dependency La Suite uses Crisp for Chat support. Added their react sdk.
2024-09-23 19:51:24 +02:00
"node_modules/crisp-sdk-web": {
"version": "1.0.25",
"resolved": "https://registry.npmjs.org/crisp-sdk-web/-/crisp-sdk-web-1.0.25.tgz",
"integrity": "sha512-CWTHFFeHRV0oqiXoPh/aIAKhFs6xcIM4NenGPnClAMCZUDQgQsF1OWmZWmnVNjJriXUmWRgDfeUxcxygS0dCRA=="
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/cross-spawn": {
"version": "7.0.3",
"resolved": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.3.tgz",
"integrity": "sha512-iRDPJKUPVEND7dHPO8rkbOnPpyDygcDFtWjpeWNCgy8WP2rXcxXL8TskReQl6OrB2G7+UJrags1q15Fudc7G6w==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
"path-key": "^3.1.0",
"shebang-command": "^2.0.0",
"which": "^2.0.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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">= 8"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/crosspath": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/crosspath/-/crosspath-2.0.0.tgz",
"integrity": "sha512-ju88BYCQ2uvjO2bR+SsgLSTwTSctU+6Vp2ePbKPgSCZyy4MWZxYsT738DlKVRE5utUjobjPRm1MkTYKJxCmpTA==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
"@types/node": "^17.0.36"
},
♻️(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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=14.9.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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/crosspath/node_modules/@types/node": {
"version": "17.0.45",
"resolved": "https://registry.npmjs.org/@types/node/-/node-17.0.45.tgz",
"integrity": "sha512-w+tIMs3rq2afQdsPJlODhoUEKzFP1ayaoyl1CcnwtIlsVe7K7bA1NGm4s3PraqTLlXnbIN84zuBlxBWo1u9BLw==",
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"dev": true,
"license": "MIT"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
},
"node_modules/css-select": {
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/css-select/-/css-select-5.1.0.tgz",
"integrity": "sha512-nwoRF1rvRRnnCqqY7updORDsuqKzqYJ28+oSMaJMMgOauh3fvwHqMS7EZpIPqK8GL+g9mKxF1vP/ZjSeNjEVHg==",
"dependencies": {
"boolbase": "^1.0.0",
"css-what": "^6.1.0",
"domhandler": "^5.0.2",
"domutils": "^3.0.1",
"nth-check": "^2.0.1"
},
"funding": {
"url": "https://github.com/sponsors/fb55"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/css-what": {
"version": "6.1.0",
"resolved": "https://registry.npmjs.org/css-what/-/css-what-6.1.0.tgz",
"integrity": "sha512-HTUrgRJ7r4dsZKU6GjmpfRK1O76h97Z8MfS1G0FozR+oF2kG6Vfe8JE6zwrkbxigziPHinCJ+gCPjA9EaBDtRw==",
♻️(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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">= 6"
},
"funding": {
"url": "https://github.com/sponsors/fb55"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/cssesc": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/cssesc/-/cssesc-3.0.0.tgz",
"integrity": "sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"bin": {
"cssesc": "bin/cssesc"
},
♻️(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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=4"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/cssnano-utils": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/cssnano-utils/-/cssnano-utils-5.0.0.tgz",
"integrity": "sha512-Uij0Xdxc24L6SirFr25MlwC2rCFX6scyUmuKpzI+JQ7cyqDEwD42fJ0xfB3yLfOnRDU5LKGgjQ9FA6LYh76GWQ==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
♻️(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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": "^18.12.0 || ^20.9.0 || >=22.0"
},
"peerDependencies": {
"postcss": "^8.4.31"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/csstype": {
"version": "3.1.3",
"resolved": "https://registry.npmjs.org/csstype/-/csstype-3.1.3.tgz",
"integrity": "sha512-M1uQkMl8rQK/szD0LNhtqxIPLpimGm8sOBwU7lLnCpSbTyY3yeU1Vc7l4KT5zT4s/yOxHH5O7tIuuLOCnLADRw==",
"devOptional": true
},
"node_modules/damerau-levenshtein": {
"version": "1.0.8",
"resolved": "https://registry.npmjs.org/damerau-levenshtein/-/damerau-levenshtein-1.0.8.tgz",
"integrity": "sha512-sdQSFB7+llfUcQHUQO3+B8ERRj0Oa4w9POWMI/puGtuf7gFywGmkaLCElnudfTiKZV+NvHqL0ifzdrI8Ro7ESA==",
"dev": true
},
"node_modules/data-view-buffer": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/data-view-buffer/-/data-view-buffer-1.0.1.tgz",
"integrity": "sha512-0lht7OugA5x3iJLOWFhWK/5ehONdprk0ISXqVFn/NFrDu+cuc8iADFrGQz5BnRK7LLU3JmkbXSxaqX+/mXYtUA==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
"call-bind": "^1.0.6",
"es-errors": "^1.3.0",
"is-data-view": "^1.0.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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">= 0.4"
♻️(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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"funding": {
"url": "https://github.com/sponsors/ljharb"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/data-view-byte-length": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/data-view-byte-length/-/data-view-byte-length-1.0.1.tgz",
"integrity": "sha512-4J7wRJD3ABAzr8wP+OcIcqq2dlUKp4DVflx++hs5h5ZKydWMI6/D/fAot+yh6g2tHh8fLFTvNOaVN357NvSrOQ==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
"call-bind": "^1.0.7",
"es-errors": "^1.3.0",
"is-data-view": "^1.0.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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/data-view-byte-offset": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/data-view-byte-offset/-/data-view-byte-offset-1.0.0.tgz",
"integrity": "sha512-t/Ygsytq+R995EJ5PZlD4Cu56sWa8InXySaViRzw9apusqsOO2bQP+SbYzAhR0pFKoB+43lYy8rWban9JSuXnA==",
♻️(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": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"call-bind": "^1.0.6",
♻️(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
"es-errors": "^1.3.0",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"is-data-view": "^1.0.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
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/debug": {
"version": "4.3.7",
"resolved": "https://registry.npmjs.org/debug/-/debug-4.3.7.tgz",
"integrity": "sha512-Er2nc/H7RrMXZBFCEim6TCmMk02Z8vLC2Rbi1KEBggpo0fS6l0S1nnapwmIi3yW/+GOJap1Krg4w0Hg80oCqgQ==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
"ms": "^2.1.3"
},
♻️(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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=6.0"
},
"peerDependenciesMeta": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"supports-color": {
"optional": true
}
♻️(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
}
},
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"node_modules/decimal.js": {
"version": "10.4.3",
"resolved": "https://registry.npmjs.org/decimal.js/-/decimal.js-10.4.3.tgz",
"integrity": "sha512-VBBaLc1MgL5XpzgIP7ny5Z6Nx3UrRkIViUkPUdtl9aya5amy3De1gsUUSB1g3+3sExYNjCAsAznmukyxCb1GRA==",
"license": "MIT"
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/deep-is": {
"version": "0.1.4",
"resolved": "https://registry.npmjs.org/deep-is/-/deep-is-0.1.4.tgz",
"integrity": "sha512-oIPzksmTg4/MriiaYGO+okXDT7ztn/w3Eptv/+gSIdMdKsJo0u4CfYNFJPy+4SKMuCqGw2wxnA+URMg3t8a/bQ==",
"dev": true
♻️(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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/define-data-property": {
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/define-data-property/-/define-data-property-1.1.4.tgz",
"integrity": "sha512-rBMvIzlpA8v6E+SJZoo++HAYqsLrkg7MSfIinMPFhmkorw7X+dOXVJQs+QT69zGkzMyfDnIMN2Wid1+NbL3T+A==",
♻️(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": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"es-define-property": "^1.0.0",
"es-errors": "^1.3.0",
"gopd": "^1.0.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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/define-properties": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.2.1.tgz",
"integrity": "sha512-8QmQKqEASLd5nx0U1B1okLElbUuuttJ/AnYmRXbbbGDWh6uS208EjD4Xqq/I9wK7u0v6O08XhTWnt5XtEbR6Dg==",
"dev": true,
🌐(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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"define-data-property": "^1.0.1",
"has-property-descriptors": "^1.0.0",
"object-keys": "^1.1.1"
🌐(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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">= 0.4"
🌐(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
},
"funding": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"url": "https://github.com/sponsors/ljharb"
🌐(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/detect-libc": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/detect-libc/-/detect-libc-1.0.3.tgz",
"integrity": "sha512-pGjwhsmsp4kL2RTz08wcOlGN83otlqHeD/Z5T8GXZB+/YcpQ/dgo+lbU8ZsGxV0HIvqqxo9l7mqYwyYMD9bKDg==",
"dev": true,
"bin": {
"detect-libc": "bin/detect-libc.js"
🌐(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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"engines": {
"node": ">=0.10"
🌐(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/doctrine": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/doctrine/-/doctrine-3.0.0.tgz",
"integrity": "sha512-yS+Q5i3hBf7GBkd4KG8a7eBNNWNGLTaEwwYWUijIYM7zrlYDM0BFXHjjPWlWZ1Rg7UaddZeIDmi9jF3HmqiQ2w==",
♻️(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": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"esutils": "^2.0.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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=6.0.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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/dom-serializer": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/dom-serializer/-/dom-serializer-2.0.0.tgz",
"integrity": "sha512-wIkAryiqt/nV5EQKqQpo3SToSOV9J0DnbJqwK7Wv/Trc92zIAYZ4FlMu+JPFW1DfGFt81ZTCGgDEabffXeLyJg==",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"domelementtype": "^2.3.0",
"domhandler": "^5.0.2",
"entities": "^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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"funding": {
"url": "https://github.com/cheeriojs/dom-serializer?sponsor=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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/domelementtype": {
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-2.3.0.tgz",
"integrity": "sha512-OLETBj6w0OsagBwdXnPdN0cnMfF9opN69co+7ZrbfPGrdpPVNBUj02spi6B1N7wChLQiPn4CSH/zJvXw56gmHw==",
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/fb55"
}
]
🌐(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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/domhandler": {
"version": "5.0.3",
"resolved": "https://registry.npmjs.org/domhandler/-/domhandler-5.0.3.tgz",
"integrity": "sha512-cgwlv/1iFQiFnU96XXgROh8xTeetsnJiDsTc7TYCLFd9+/WNkIqPTxiM/8pSd8VIrhXGTf1Ny1q1hquVqDJB5w==",
"dependencies": {
"domelementtype": "^2.3.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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">= 4"
},
"funding": {
"url": "https://github.com/fb55/domhandler?sponsor=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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/domutils": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/domutils/-/domutils-3.1.0.tgz",
"integrity": "sha512-H78uMmQtI2AhgDJjWeQmHwJJ2bLPD3GMmO7Zja/ZZh84wkm+4ut+IUnUdRa8uCGX88DiVx1j6FRe1XfxEgjEZA==",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dom-serializer": "^2.0.0",
"domelementtype": "^2.3.0",
"domhandler": "^5.0.3"
},
"funding": {
"url": "https://github.com/fb55/domutils?sponsor=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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/electron-to-chromium": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "1.5.83",
"resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.5.83.tgz",
"integrity": "sha512-LcUDPqSt+V0QmI47XLzZrz5OqILSMGsPFkDYus22rIbgorSvBYEFqq854ltTmUdHkY92FSdAAvsh4jWEULMdfQ==",
"dev": true,
"license": "ISC"
♻️(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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/emoji-regex": {
"version": "9.2.2",
"resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-9.2.2.tgz",
"integrity": "sha512-L18DaJsXSUk2+42pv8mLs5jJT2hqFkFE4j21wOmgbUqsZ2hL72NsUU785g9RXgo3s0ZNgVl42TiHp3ZtOv/Vyg==",
♻️(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": true
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/encoding-sniffer": {
"version": "0.2.0",
"resolved": "https://registry.npmjs.org/encoding-sniffer/-/encoding-sniffer-0.2.0.tgz",
"integrity": "sha512-ju7Wq1kg04I3HtiYIOrUrdfdDvkyO9s5XM8QAj/bN61Yo/Vb4vgJxy5vi4Yxk01gWHbrofpPtpxM8bKger9jhg==",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"iconv-lite": "^0.6.3",
"whatwg-encoding": "^3.1.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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"funding": {
"url": "https://github.com/fb55/encoding-sniffer?sponsor=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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/ensure-posix-path": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/ensure-posix-path/-/ensure-posix-path-1.1.1.tgz",
"integrity": "sha512-VWU0/zXzVbeJNXvME/5EmLuEj2TauvoaTz6aFYK1Z92JCBlDlZ3Gu0tuGR42kpW1754ywTs+QB0g5TP0oj9Zaw=="
},
"node_modules/entities": {
"version": "4.5.0",
"resolved": "https://registry.npmjs.org/entities/-/entities-4.5.0.tgz",
"integrity": "sha512-V0hjH4dGPh9Ao5p0MoRY6BVqtwCjhz6vI5LT8AJ55H+4g9/4vbHx1I54fS0XuclLhDHArPQCiMjDxjaL8fPxhw==",
♻️(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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=0.12"
},
"funding": {
"url": "https://github.com/fb55/entities?sponsor=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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/eol": {
"version": "0.9.1",
"resolved": "https://registry.npmjs.org/eol/-/eol-0.9.1.tgz",
"integrity": "sha512-Ds/TEoZjwggRoz/Q2O7SE3i4Jm66mqTDfmdHdq/7DKVk3bro9Q8h6WdXKdPqFLMoqxrDK5SVRzHVPOS6uuGtrg=="
♻️(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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/es-abstract": {
"version": "1.23.3",
"resolved": "https://registry.npmjs.org/es-abstract/-/es-abstract-1.23.3.tgz",
"integrity": "sha512-e+HfNH61Bj1X9/jLc5v1owaLYuHdeHHSQlkhCBiTK8rBvKaULl/beGMxwrMXjpYrv4pz22BlY570vVePA2ho4A==",
"dev": true,
🌐(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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"array-buffer-byte-length": "^1.0.1",
"arraybuffer.prototype.slice": "^1.0.3",
"available-typed-arrays": "^1.0.7",
"call-bind": "^1.0.7",
"data-view-buffer": "^1.0.1",
"data-view-byte-length": "^1.0.1",
"data-view-byte-offset": "^1.0.0",
"es-define-property": "^1.0.0",
"es-errors": "^1.3.0",
"es-object-atoms": "^1.0.0",
"es-set-tostringtag": "^2.0.3",
"es-to-primitive": "^1.2.1",
"function.prototype.name": "^1.1.6",
"get-intrinsic": "^1.2.4",
"get-symbol-description": "^1.0.2",
"globalthis": "^1.0.3",
"gopd": "^1.0.1",
"has-property-descriptors": "^1.0.2",
"has-proto": "^1.0.3",
"has-symbols": "^1.0.3",
"hasown": "^2.0.2",
"internal-slot": "^1.0.7",
"is-array-buffer": "^3.0.4",
"is-callable": "^1.2.7",
"is-data-view": "^1.0.1",
"is-negative-zero": "^2.0.3",
"is-regex": "^1.1.4",
"is-shared-array-buffer": "^1.0.3",
"is-string": "^1.0.7",
"is-typed-array": "^1.1.13",
"is-weakref": "^1.0.2",
"object-inspect": "^1.13.1",
"object-keys": "^1.1.1",
"object.assign": "^4.1.5",
"regexp.prototype.flags": "^1.5.2",
"safe-array-concat": "^1.1.2",
"safe-regex-test": "^1.0.3",
"string.prototype.trim": "^1.2.9",
"string.prototype.trimend": "^1.0.8",
"string.prototype.trimstart": "^1.0.8",
"typed-array-buffer": "^1.0.2",
"typed-array-byte-length": "^1.0.1",
"typed-array-byte-offset": "^1.0.2",
"typed-array-length": "^1.0.6",
"unbox-primitive": "^1.0.2",
"which-typed-array": "^1.1.15"
🌐(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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">= 0.4"
🌐(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
},
"funding": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"url": "https://github.com/sponsors/ljharb"
🌐(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/es-define-property": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/es-define-property/-/es-define-property-1.0.0.tgz",
"integrity": "sha512-jxayLKShrEqqzJ0eumQbVhTYQM27CfT1T35+gCgDFoL82JLsXqTJ76zv6A0YLOgEnLUMvLzsDsGIrl8NFpT2gQ==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
"get-intrinsic": "^1.2.4"
♻️(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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">= 0.4"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/es-errors": {
"version": "1.3.0",
"resolved": "https://registry.npmjs.org/es-errors/-/es-errors-1.3.0.tgz",
"integrity": "sha512-Zf5H2Kxt2xjTvbJvP2ZWLEICxA6j+hAmMzIlypy4xcBg1vKVnx89Wy0GbS+kf5cwCVFFzdCFh2XSCFNULS6csw==",
♻️(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": true,
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">= 0.4"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/es-object-atoms": {
♻️(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
"version": "1.0.0",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"resolved": "https://registry.npmjs.org/es-object-atoms/-/es-object-atoms-1.0.0.tgz",
"integrity": "sha512-MZ4iQ6JwHOBQjahnjwaC1ZtIBH+2ohjamzAO3oaHcXYup7qxjF2fixyH+Q71voWHeOkI2q/TnJao/KfXYIZWbw==",
♻️(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": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"es-errors": "^1.3.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
},
"engines": {
"node": ">= 0.4"
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/es-set-tostringtag": {
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/es-set-tostringtag/-/es-set-tostringtag-2.0.3.tgz",
"integrity": "sha512-3T8uNMC3OQTHkFUsFq8r/BwAXLHvU/9O9mE0fBc/MY5iq/8H7ncvO947LmYA6ldWw9Uh8Yhf25zu6n7nML5QWQ==",
♻️(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": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"get-intrinsic": "^1.2.4",
"has-tostringtag": "^1.0.2",
"hasown": "^2.0.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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">= 0.4"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/es-shim-unscopables": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/es-shim-unscopables/-/es-shim-unscopables-1.0.2.tgz",
"integrity": "sha512-J3yBRXCzDu4ULnQwxyToo/OjdMx6akgVC7K6few0a7F/0wLtmKKN7I73AH5T2836UuXRqN7Qg+IIUw/+YJksRw==",
♻️(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": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"hasown": "^2.0.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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/es-to-primitive": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/es-to-primitive/-/es-to-primitive-1.2.1.tgz",
"integrity": "sha512-QCOllgZJtaUo9miYBcLChTUaHNjJF3PYs1VidD7AwiEj1kYxKeQTctLAezAOH5ZKRH0g2IgPn6KwB4IT8iRpvA==",
♻️(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": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"is-callable": "^1.1.4",
"is-date-object": "^1.0.1",
"is-symbol": "^1.0.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
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/esbuild": {
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/esbuild/-/esbuild-0.20.2.tgz",
"integrity": "sha512-WdOOppmUNU+IbZ0PaDiTst80zjnrOkyJNHoKupIcVyU8Lvla3Ugx94VzkQ32Ijqd7UhHJy75gNWDMUekcrSJ6g==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"hasInstallScript": true,
"bin": {
"esbuild": "bin/esbuild"
♻️(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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=12"
♻️(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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optionalDependencies": {
"@esbuild/aix-ppc64": "0.20.2",
"@esbuild/android-arm": "0.20.2",
"@esbuild/android-arm64": "0.20.2",
"@esbuild/android-x64": "0.20.2",
"@esbuild/darwin-arm64": "0.20.2",
"@esbuild/darwin-x64": "0.20.2",
"@esbuild/freebsd-arm64": "0.20.2",
"@esbuild/freebsd-x64": "0.20.2",
"@esbuild/linux-arm": "0.20.2",
"@esbuild/linux-arm64": "0.20.2",
"@esbuild/linux-ia32": "0.20.2",
"@esbuild/linux-loong64": "0.20.2",
"@esbuild/linux-mips64el": "0.20.2",
"@esbuild/linux-ppc64": "0.20.2",
"@esbuild/linux-riscv64": "0.20.2",
"@esbuild/linux-s390x": "0.20.2",
"@esbuild/linux-x64": "0.20.2",
"@esbuild/netbsd-x64": "0.20.2",
"@esbuild/openbsd-x64": "0.20.2",
"@esbuild/sunos-x64": "0.20.2",
"@esbuild/win32-arm64": "0.20.2",
"@esbuild/win32-ia32": "0.20.2",
"@esbuild/win32-x64": "0.20.2"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/escalade": {
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/escalade/-/escalade-3.1.2.tgz",
"integrity": "sha512-ErCHMCae19vR8vQGe50xIsVomy19rg6gFu3+r3jkEO46suLMWBksvVyoGgQV+jOfl84ZSOSlmv6Gxa89PmTGmA==",
♻️(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": true,
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=6"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/eslint": {
"version": "8.57.0",
"resolved": "https://registry.npmjs.org/eslint/-/eslint-8.57.0.tgz",
"integrity": "sha512-dZ6+mexnaTIbSBZWgou51U6OmzIhYM2VcNdtiTtI7qPNZm35Akpr0f6vtw3w1Kmn5PYo+tZVfh13WrhpS6oLqQ==",
♻️(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": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"@eslint-community/eslint-utils": "^4.2.0",
"@eslint-community/regexpp": "^4.6.1",
"@eslint/eslintrc": "^2.1.4",
"@eslint/js": "8.57.0",
"@humanwhocodes/config-array": "^0.11.14",
"@humanwhocodes/module-importer": "^1.0.1",
"@nodelib/fs.walk": "^1.2.8",
"@ungap/structured-clone": "^1.2.0",
"ajv": "^6.12.4",
"chalk": "^4.0.0",
"cross-spawn": "^7.0.2",
"debug": "^4.3.2",
"doctrine": "^3.0.0",
"escape-string-regexp": "^4.0.0",
"eslint-scope": "^7.2.2",
"eslint-visitor-keys": "^3.4.3",
"espree": "^9.6.1",
"esquery": "^1.4.2",
"esutils": "^2.0.2",
"fast-deep-equal": "^3.1.3",
"file-entry-cache": "^6.0.1",
"find-up": "^5.0.0",
"glob-parent": "^6.0.2",
"globals": "^13.19.0",
"graphemer": "^1.4.0",
"ignore": "^5.2.0",
"imurmurhash": "^0.1.4",
"is-glob": "^4.0.0",
"is-path-inside": "^3.0.3",
"js-yaml": "^4.1.0",
"json-stable-stringify-without-jsonify": "^1.0.1",
"levn": "^0.4.1",
"lodash.merge": "^4.6.2",
"minimatch": "^3.1.2",
"natural-compare": "^1.4.0",
"optionator": "^0.9.3",
"strip-ansi": "^6.0.1",
"text-table": "^0.2.0"
},
"bin": {
"eslint": "bin/eslint.js"
♻️(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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": "^12.22.0 || ^14.17.0 || >=16.0.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
},
"funding": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"url": "https://opencollective.com/eslint"
🌐(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/eslint-config-prettier": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "10.0.1",
"resolved": "https://registry.npmjs.org/eslint-config-prettier/-/eslint-config-prettier-10.0.1.tgz",
"integrity": "sha512-lZBts941cyJyeaooiKxAtzoPHTN+GbQTJFAIdQbRhA4/8whaAraEh47Whw/ZFfrjNSnlAxqfm9i0XVAEkULjCw==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dev": true,
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"bin": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"eslint-config-prettier": "build/bin/cli.js"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
},
"peerDependencies": {
"eslint": ">=7.0.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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/eslint-plugin-jsx-a11y": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "6.10.2",
"resolved": "https://registry.npmjs.org/eslint-plugin-jsx-a11y/-/eslint-plugin-jsx-a11y-6.10.2.tgz",
"integrity": "sha512-scB3nz4WmG75pV8+3eRUQOHZlNSUhFNq37xnpgRkCCELU3XMvXAxLk1eqWWyE22Ki4Q01Fnsw9BA3cJHDPgn2Q==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dev": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
🌐(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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"aria-query": "^5.3.2",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"array-includes": "^3.1.8",
"array.prototype.flatmap": "^1.3.2",
"ast-types-flow": "^0.0.8",
"axe-core": "^4.10.0",
"axobject-query": "^4.1.0",
"damerau-levenshtein": "^1.0.8",
"emoji-regex": "^9.2.2",
"hasown": "^2.0.2",
"jsx-ast-utils": "^3.3.5",
"language-tags": "^1.0.9",
"minimatch": "^3.1.2",
"object.fromentries": "^2.0.8",
"safe-regex-test": "^1.0.3",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"string.prototype.includes": "^2.0.1"
🌐(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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=4.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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"peerDependencies": {
"eslint": "^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9"
🌐(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/eslint-plugin-jsx-a11y/node_modules/brace-expansion": {
"version": "1.1.11",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz",
"integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==",
"dev": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
🌐(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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
🌐(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/eslint-plugin-jsx-a11y/node_modules/minimatch": {
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz",
"integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==",
"dev": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "ISC",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
"brace-expansion": "^1.1.7"
},
"engines": {
"node": "*"
}
🌐(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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/eslint-plugin-react-hooks": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/eslint-plugin-react-hooks/-/eslint-plugin-react-hooks-5.1.0.tgz",
"integrity": "sha512-mpJRtPgHN2tNAvZ35AMfqeB3Xqeo273QxrHJsbBEPWODRM4r0yB6jfoROqKEYrOn27UtRPpcpHc2UqyBSuUNTw==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dev": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=10"
♻️(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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"eslint": "^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0-0 || ^9.0.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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/eslint-plugin-react-refresh": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.4.18",
"resolved": "https://registry.npmjs.org/eslint-plugin-react-refresh/-/eslint-plugin-react-refresh-0.4.18.tgz",
"integrity": "sha512-IRGEoFn3OKalm3hjfolEWGqoF/jPqeEYFp+C8B0WMzwGwBMvlRDQd06kghDhF0C61uJ6WfSDhEZE/sAQjduKgw==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dev": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"peerDependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"eslint": ">=8.40"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
🌐(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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/eslint-scope": {
"version": "7.2.2",
"resolved": "https://registry.npmjs.org/eslint-scope/-/eslint-scope-7.2.2.tgz",
"integrity": "sha512-dOt21O7lTMhDM+X9mB4GX+DZrZtCUJPL/wlcTqxyrx5IvO0IYtILdtrQGQp+8n5S0gwSVmOf9NQrjMOgfQZlIg==",
♻️(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": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"esrecurse": "^4.3.0",
"estraverse": "^5.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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": "^12.22.0 || ^14.17.0 || >=16.0.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
},
"funding": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"url": "https://opencollective.com/eslint"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/eslint-visitor-keys": {
"version": "3.4.3",
"resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-3.4.3.tgz",
"integrity": "sha512-wpc+LXeiyiisxPlEkUzU6svyS1frIO3Mgxj1fdy7Pm8Ygzguax2N3Fa/D/ag1WqbOprdI+uY6wMUl8/a2G+iag==",
"dev": true,
"engines": {
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
},
"funding": {
"url": "https://opencollective.com/eslint"
}
},
"node_modules/eslint/node_modules/brace-expansion": {
"version": "1.1.11",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz",
"integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
"balanced-match": "^1.0.0",
"concat-map": "0.0.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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/eslint/node_modules/chalk": {
"version": "4.1.2",
"resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz",
"integrity": "sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==",
♻️(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": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"ansi-styles": "^4.1.0",
"supports-color": "^7.1.0"
},
"engines": {
"node": ">=10"
♻️(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
},
"funding": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"url": "https://github.com/chalk/chalk?sponsor=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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/eslint/node_modules/escape-string-regexp": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-4.0.0.tgz",
"integrity": "sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA==",
♻️(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": true,
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/eslint/node_modules/globals": {
"version": "13.24.0",
"resolved": "https://registry.npmjs.org/globals/-/globals-13.24.0.tgz",
"integrity": "sha512-AhO5QUcj8llrbG09iWhPU2B204J1xnPeL8kQmVorSsy+Sjj1sk8gIyh6cUocGmH4L0UuhAJy+hJMRA4mgA4mFQ==",
♻️(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": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"type-fest": "^0.20.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
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=8"
♻️(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
},
"funding": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"url": "https://github.com/sponsors/sindresorhus"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/eslint/node_modules/has-flag": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz",
"integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==",
♻️(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": true,
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=8"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/eslint/node_modules/minimatch": {
♻️(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
"version": "3.1.2",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz",
"integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
"brace-expansion": "^1.1.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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": "*"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/eslint/node_modules/supports-color": {
"version": "7.2.0",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-7.2.0.tgz",
"integrity": "sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
"has-flag": "^4.0.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
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=8"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/espree": {
"version": "9.6.1",
"resolved": "https://registry.npmjs.org/espree/-/espree-9.6.1.tgz",
"integrity": "sha512-oruZaFkjorTpF32kDSI5/75ViwGeZginGGy2NoOSg3Q9bnwlnmDm4HLnkl0RE3n+njDXR037aY1+x58Z/zFdwQ==",
♻️(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": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"acorn": "^8.9.0",
"acorn-jsx": "^5.3.2",
"eslint-visitor-keys": "^3.4.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
},
"engines": {
"node": "^12.22.0 || ^14.17.0 || >=16.0.0"
},
"funding": {
"url": "https://opencollective.com/eslint"
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/esquery": {
"version": "1.6.0",
"resolved": "https://registry.npmjs.org/esquery/-/esquery-1.6.0.tgz",
"integrity": "sha512-ca9pw9fomFcKPvFLXhBKUK90ZvGibiGOvRJNbjljY7s7uq/5YO4BOzcYtJqExdx99rF6aAcnRxHmcUHcz6sQsg==",
🔧(frontend) configure Prettier and ESLint Set up Prettier with minimal configuration. Installed eslint-config-prettier to prevent conflicts between ESLint and Prettier.
2024-08-06 11:06:16 +02:00
"dev": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
"estraverse": "^5.1.0"
🔧(frontend) configure Prettier and ESLint Set up Prettier with minimal configuration. Installed eslint-config-prettier to prevent conflicts between ESLint and Prettier.
2024-08-06 11:06:16 +02:00
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"engines": {
"node": ">=0.10"
🔧(frontend) configure Prettier and ESLint Set up Prettier with minimal configuration. Installed eslint-config-prettier to prevent conflicts between ESLint and Prettier.
2024-08-06 11:06:16 +02:00
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/esrecurse": {
"version": "4.3.0",
"resolved": "https://registry.npmjs.org/esrecurse/-/esrecurse-4.3.0.tgz",
"integrity": "sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag==",
♻️(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": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"estraverse": "^5.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
},
"engines": {
"node": ">=4.0"
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/estraverse": {
"version": "5.3.0",
"resolved": "https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz",
"integrity": "sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"engines": {
"node": ">=4.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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/estree-walker": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/estree-walker/-/estree-walker-2.0.2.tgz",
"integrity": "sha512-Rfkk/Mp/DL7JVje3u18FxFujQlTNR2q6QfMSMB7AvCBx91NGj/ba3kCfza0f6dVDbw7YlRf/nDrn7pQrCCyQ/w==",
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"dev": true,
"license": "MIT"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
},
"node_modules/esutils": {
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/esutils/-/esutils-2.0.3.tgz",
"integrity": "sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==",
♻️(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": true,
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/events": {
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/events/-/events-3.3.0.tgz",
"integrity": "sha512-mQw+2fkQbALzQ7V0MY0IqdnXNOeTtP4r0lN9z7AAawCXgqea7bDii20AYrIBrFd/Hx0M2Ocz6S111CaFkUcb0Q==",
"engines": {
"node": ">=0.8.x"
}
},
"node_modules/fast-deep-equal": {
"version": "3.1.3",
"resolved": "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz",
"integrity": "sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==",
"dev": true
},
🌐(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
"node_modules/fast-fifo": {
"version": "1.3.2",
"resolved": "https://registry.npmjs.org/fast-fifo/-/fast-fifo-1.3.2.tgz",
"integrity": "sha512-/d9sfos4yxzpwkDkuN7k2SqFKtYNmCTzgfEpz82x34IM9/zc8KGxQoXg1liNC/izpRM/MBdt44Nmx41ZWqk+FQ=="
},
♻️(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
"node_modules/fast-glob": {
"version": "3.3.2",
"resolved": "https://registry.npmjs.org/fast-glob/-/fast-glob-3.3.2.tgz",
"integrity": "sha512-oX2ruAFQwf/Orj8m737Y5adxDQO0LAB7/S5MnxCdTNDd4p6BsyIVsv9JQsATbTSq8KHRpLwIHbVlUNatxd+1Ow==",
✨(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
"dev": true,
"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
"@nodelib/fs.stat": "^2.0.2",
"@nodelib/fs.walk": "^1.2.3",
"glob-parent": "^5.1.2",
"merge2": "^1.3.0",
"micromatch": "^4.0.4"
✨(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
},
"engines": {
♻️(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
"node": ">=8.6.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
}
},
♻️(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
"node_modules/fast-glob/node_modules/glob-parent": {
"version": "5.1.2",
"resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz",
"integrity": "sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==",
✨(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
"dev": true,
"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
"is-glob": "^4.0.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
},
"engines": {
♻️(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
"node": ">= 6"
✨(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) 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
"node_modules/fast-json-stable-stringify": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/fast-json-stable-stringify/-/fast-json-stable-stringify-2.1.0.tgz",
"integrity": "sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==",
"dev": true
},
"node_modules/fast-levenshtein": {
"version": "2.0.6",
"resolved": "https://registry.npmjs.org/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz",
"integrity": "sha512-DCXu6Ifhqcks7TZKY3Hxp3y6qphY5SJZmrWMDrKcERSOXWQdMhU9Ig/PYrzyw/ul9jOIyh0N4M0tbC5hodg8dw==",
"dev": true
},
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"node_modules/fast-uri": {
"version": "3.0.6",
"resolved": "https://registry.npmjs.org/fast-uri/-/fast-uri-3.0.6.tgz",
"integrity": "sha512-Atfo14OibSv5wAp4VWNsFYE1AchQRTv9cBGWET4pZWHzYshFSS9NQI6I57rdKn9croWVMbYFbLhJ+yJvmZIIHw==",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/fastify"
},
{
"type": "opencollective",
"url": "https://opencollective.com/fastify"
}
],
"license": "BSD-3-Clause"
},
♻️(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
"node_modules/fastq": {
"version": "1.17.1",
"resolved": "https://registry.npmjs.org/fastq/-/fastq-1.17.1.tgz",
"integrity": "sha512-sRVD3lWVIXWg6By68ZN7vho9a1pQcN/WBFaAAsDDFzlJjvoGx0P8z7V1t72grFJfJhu3YPZBuu25f7Kaw2jN1w==",
✨(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
"reusify": "^1.0.4"
✨(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) add posthog dependency Posthog is a product analysis tool. Installed the js SDK to track product usage.
2024-09-17 10:45:58 +02:00
"node_modules/fflate": {
"version": "0.4.8",
"resolved": "https://registry.npmjs.org/fflate/-/fflate-0.4.8.tgz",
"integrity": "sha512-FJqqoDBR00Mdj9ppamLa/Y7vxm+PRmNWA67N846RvsoYVMKB4q3y/de5PA7gUmRMYK/8CMz2GDZQmCRN1wBcWA=="
},
♻️(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
"node_modules/file-entry-cache": {
"version": "6.0.1",
"resolved": "https://registry.npmjs.org/file-entry-cache/-/file-entry-cache-6.0.1.tgz",
"integrity": "sha512-7Gps/XWymbLk2QLYK4NzpMOrYjMhdIxXuIvy2QBsLE6ljuodKvdkWs/cpyJJ3CVIVpH0Oi1Hvg1ovbMzLdFBBg==",
✨(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
"dev": true,
"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
"flat-cache": "^3.0.4"
✨(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
},
"engines": {
♻️(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
"node": "^10.12.0 || >=12.0.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
}
},
♻️(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
"node_modules/fill-range": {
"version": "7.1.1",
"resolved": "https://registry.npmjs.org/fill-range/-/fill-range-7.1.1.tgz",
"integrity": "sha512-YsGpe3WHLK8ZYi4tWDg2Jy3ebRz2rXowDxnld4bkQB00cc/1Zw9AWnC0i9ztDJitivtQvaI9KaLyKrc+hBW0yg==",
✨(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
"dev": true,
"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
"to-regex-range": "^5.0.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
},
"engines": {
♻️(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
"node": ">=8"
✨(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) 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
"node_modules/find-up": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/find-up/-/find-up-5.0.0.tgz",
"integrity": "sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==",
✨(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
"dev": true,
"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
"locate-path": "^6.0.0",
"path-exists": "^4.0.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
},
"engines": {
♻️(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
"node": ">=10"
✨(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
},
"funding": {
♻️(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
"url": "https://github.com/sponsors/sindresorhus"
✨(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) 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
"node_modules/flat-cache": {
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/flat-cache/-/flat-cache-3.2.0.tgz",
"integrity": "sha512-CYcENa+FtcUKLmhhqyctpclsq7QF38pKjZHsGNiSQF5r4FtoKDWabFDl3hzaEQMvT1LHEysw5twgLvpYYb4vbw==",
"dev": true,
"dependencies": {
"flatted": "^3.2.9",
"keyv": "^4.5.3",
"rimraf": "^3.0.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
},
"engines": {
♻️(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
"node": "^10.12.0 || >=12.0.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
}
},
♻️(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
"node_modules/flatted": {
"version": "3.3.1",
"resolved": "https://registry.npmjs.org/flatted/-/flatted-3.3.1.tgz",
"integrity": "sha512-X8cqMLLie7KsNUDSdzeN8FYK9rEt4Dt67OsG/DNGnYTSDBG4uFAJFBnUeiV+zCVAvwFy56IjM9sH51jVaEhNxw==",
✨(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
"dev": true
},
♻️(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
"node_modules/for-each": {
"version": "0.3.3",
"resolved": "https://registry.npmjs.org/for-each/-/for-each-0.3.3.tgz",
"integrity": "sha512-jqYfLp7mo9vIyQf8ykW2v7A+2N4QjeCeI5+Dz9XraiO1ign81wjiH7Fb9vSOWvQfNtmSa4H2RoQTrrXivdUZmw==",
✨(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
"dev": true,
"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
"is-callable": "^1.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
}
},
♻️(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
"node_modules/fs-extra": {
"version": "11.2.0",
"resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-11.2.0.tgz",
"integrity": "sha512-PmDi3uwK5nFuXh7XDTlVnS17xJS7vW36is2+w3xcv8SVxiB4NyATf4ctkVY5bkSjX0Y4nbvZCq1/EjtEyr9ktw==",
"dependencies": {
"graceful-fs": "^4.2.0",
"jsonfile": "^6.0.1",
"universalify": "^2.0.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
},
"engines": {
♻️(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
"node": ">=14.14"
✨(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) 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
"node_modules/fs-merger": {
"version": "3.2.1",
"resolved": "https://registry.npmjs.org/fs-merger/-/fs-merger-3.2.1.tgz",
"integrity": "sha512-AN6sX12liy0JE7C2evclwoo0aCG3PFulLjrTLsJpWh/2mM+DinhpSGqYLbHBBbIW1PLRNcFhJG8Axtz8mQW3ug==",
"dependencies": {
"broccoli-node-api": "^1.7.0",
"broccoli-node-info": "^2.1.0",
"fs-extra": "^8.0.1",
"fs-tree-diff": "^2.0.1",
"walk-sync": "^2.2.0"
}
},
"node_modules/fs-merger/node_modules/fs-extra": {
"version": "8.1.0",
"resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-8.1.0.tgz",
"integrity": "sha512-yhlQgA6mnOJUKOsRUFsgJdQCvkKhcz8tlZG5HBQfReYZy46OwLcY+Zia0mtdHsOo9y/hP+CxMN0TU9QxoOtG4g==",
"dependencies": {
"graceful-fs": "^4.2.0",
"jsonfile": "^4.0.0",
"universalify": "^0.1.0"
},
"engines": {
"node": ">=6 <7 || >=8"
}
},
"node_modules/fs-merger/node_modules/jsonfile": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-4.0.0.tgz",
"integrity": "sha512-m6F1R3z8jjlf2imQHS2Qez5sjKWQzbuuhuJ/FKYFRZvPE3PuHcSMVZzfsLhGVOkfd20obL5SWEBew5ShlquNxg==",
"optionalDependencies": {
"graceful-fs": "^4.1.6"
}
},
"node_modules/fs-merger/node_modules/universalify": {
"version": "0.1.2",
"resolved": "https://registry.npmjs.org/universalify/-/universalify-0.1.2.tgz",
"integrity": "sha512-rBJeI5CXAlmy1pV+617WB9J63U6XcazHHF2f2dbJix4XzpUF0RS3Zbj0FGIOCAva5P/d/GBOYaACQ1w+0azUkg==",
"engines": {
"node": ">= 4.0.0"
}
},
"node_modules/fs-mkdirp-stream": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/fs-mkdirp-stream/-/fs-mkdirp-stream-2.0.1.tgz",
"integrity": "sha512-UTOY+59K6IA94tec8Wjqm0FSh5OVudGNB0NL/P6fB3HiE3bYOY3VYBGijsnOHNkQSwC1FKkU77pmq7xp9CskLw==",
"dependencies": {
"graceful-fs": "^4.2.8",
"streamx": "^2.12.0"
},
"engines": {
"node": ">=10.13.0"
}
},
"node_modules/fs-tree-diff": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/fs-tree-diff/-/fs-tree-diff-2.0.1.tgz",
"integrity": "sha512-x+CfAZ/lJHQqwlD64pYM5QxWjzWhSjroaVsr8PW831zOApL55qPibed0c+xebaLWVr2BnHFoHdrwOv8pzt8R5A==",
"dependencies": {
"@types/symlink-or-copy": "^1.2.0",
"heimdalljs-logger": "^0.1.7",
"object-assign": "^4.1.0",
"path-posix": "^1.0.0",
"symlink-or-copy": "^1.1.8"
},
"engines": {
"node": "6.* || 8.* || >= 10.*"
}
},
♻️(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
"node_modules/fs.realpath": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/fs.realpath/-/fs.realpath-1.0.0.tgz",
🌐(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
"integrity": "sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw=="
♻️(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
},
"node_modules/fsevents": {
"version": "2.3.3",
"resolved": "https://registry.npmjs.org/fsevents/-/fsevents-2.3.3.tgz",
"integrity": "sha512-5xoDfX+fL7faATnagmWPpbFtwh/R77WmMMqqHGS65C3vvB0YHrgF+B1YmZ3441tMj5n63k0212XNoJwzlhffQw==",
"dev": true,
"hasInstallScript": true,
"optional": true,
"os": [
"darwin"
],
"engines": {
"node": "^8.16.0 || ^10.6.0 || >=11.0.0"
}
},
"node_modules/function-bind": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/function-bind/-/function-bind-1.1.2.tgz",
"integrity": "sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA==",
✨(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
"dev": true,
♻️(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
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/function.prototype.name": {
"version": "1.1.6",
"resolved": "https://registry.npmjs.org/function.prototype.name/-/function.prototype.name-1.1.6.tgz",
"integrity": "sha512-Z5kx79swU5P27WEayXM1tBi5Ze/lbIyiNgU3qyXUOf9b2rgXYyF9Dy9Cx+IQv/Lc8WCG6L82zwUPpSS9hGehIg==",
✨(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
"dev": true,
"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
"call-bind": "^1.0.2",
"define-properties": "^1.2.0",
"es-abstract": "^1.22.1",
"functions-have-names": "^1.2.3"
},
"engines": {
"node": ">= 0.4"
✨(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
},
"funding": {
♻️(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
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/functions-have-names": {
"version": "1.2.3",
"resolved": "https://registry.npmjs.org/functions-have-names/-/functions-have-names-1.2.3.tgz",
"integrity": "sha512-xckBUXyTIqT97tq2x2AMb+g163b5JFysYk0x4qxNFwbfQkmNZoiRHb6sPzI9/QV33WeuvVYBUIiD4NzNIyqaRQ==",
✨(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
"dev": true,
♻️(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
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/gensync": {
"version": "1.0.0-beta.2",
"resolved": "https://registry.npmjs.org/gensync/-/gensync-1.0.0-beta.2.tgz",
"integrity": "sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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
"engines": {
♻️(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
"node": ">=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
}
},
♻️(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
"node_modules/get-intrinsic": {
"version": "1.2.4",
"resolved": "https://registry.npmjs.org/get-intrinsic/-/get-intrinsic-1.2.4.tgz",
"integrity": "sha512-5uYhsJH8VJBTv7oslg4BznJYhDoRI6waYCxMmCdnTrcCrHA/fCFKoTFz2JKKE0HdDFUF7/oQuhzumXJK7paBRQ==",
✨(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
"dev": true,
♻️(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
"dependencies": {
"es-errors": "^1.3.0",
"function-bind": "^1.1.2",
"has-proto": "^1.0.1",
"has-symbols": "^1.0.3",
"hasown": "^2.0.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
"engines": {
♻️(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
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/get-symbol-description": {
✨(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
"version": "1.0.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
"resolved": "https://registry.npmjs.org/get-symbol-description/-/get-symbol-description-1.0.2.tgz",
"integrity": "sha512-g0QYk1dZBxGwk+Ngc+ltRH2IBp2f7zBkBMBJZCDerh6EhlhSR6+9irMCuT/09zD6qkarHUSn529sK/yL4S27mg==",
✨(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
"dev": true,
"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
"call-bind": "^1.0.5",
"es-errors": "^1.3.0",
"get-intrinsic": "^1.2.4"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/glob": {
"version": "7.2.3",
"resolved": "https://registry.npmjs.org/glob/-/glob-7.2.3.tgz",
"integrity": "sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==",
"deprecated": "Glob versions prior to v9 are no longer supported",
✨(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
"fs.realpath": "^1.0.0",
"inflight": "^1.0.4",
"inherits": "2",
"minimatch": "^3.1.1",
"once": "^1.3.0",
"path-is-absolute": "^1.0.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
},
"engines": {
♻️(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
"node": "*"
},
"funding": {
"url": "https://github.com/sponsors/isaacs"
✨(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) 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
"node_modules/glob-parent": {
"version": "6.0.2",
"resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-6.0.2.tgz",
"integrity": "sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==",
✨(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
"is-glob": "^4.0.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
},
"engines": {
♻️(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
"node": ">=10.13.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
}
},
🌐(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
"node_modules/glob-stream": {
"version": "8.0.2",
"resolved": "https://registry.npmjs.org/glob-stream/-/glob-stream-8.0.2.tgz",
"integrity": "sha512-R8z6eTB55t3QeZMmU1C+Gv+t5UnNRkA55c5yo67fAVfxODxieTwsjNG7utxS/73NdP1NbDgCrhVEg2h00y4fFw==",
"dependencies": {
"@gulpjs/to-absolute-glob": "^4.0.0",
"anymatch": "^3.1.3",
"fastq": "^1.13.0",
"glob-parent": "^6.0.2",
"is-glob": "^4.0.3",
"is-negated-glob": "^1.0.0",
"normalize-path": "^3.0.0",
"streamx": "^2.12.5"
},
"engines": {
"node": ">=10.13.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
"node_modules/glob/node_modules/brace-expansion": {
"version": "1.1.11",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz",
"integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==",
"dependencies": {
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
}
},
"node_modules/glob/node_modules/minimatch": {
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz",
"integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==",
"dependencies": {
"brace-expansion": "^1.1.7"
},
✨(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
"engines": {
♻️(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
"node": "*"
✨(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) 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
"node_modules/globals": {
"version": "11.12.0",
"resolved": "https://registry.npmjs.org/globals/-/globals-11.12.0.tgz",
"integrity": "sha512-WOBp/EEGUiIsJSp7wcv/y6MO+lV9UoncWqxuFfm8eBwzWNgyfBd6Gz+IeKQ9jCmyhoH99g15M3T+QaVHFjizVA==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
♻️(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
"engines": {
"node": ">=4"
}
✨(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) 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
"node_modules/globalthis": {
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/globalthis/-/globalthis-1.0.4.tgz",
"integrity": "sha512-DpLKbNU4WylpxJykQujfCcwYWiV/Jhm50Goo0wrVILAv5jOr9d+H+UR3PhSCD2rCCEIg0uc+G+muBTwD54JhDQ==",
✨(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
"dev": true,
"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
"define-properties": "^1.2.1",
"gopd": "^1.0.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
},
"engines": {
♻️(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
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/globrex": {
"version": "0.1.2",
"resolved": "https://registry.npmjs.org/globrex/-/globrex-0.1.2.tgz",
"integrity": "sha512-uHJgbwAMwNFf5mLst7IWLNg14x1CkeqglJb/K3doi4dw6q2IvAAmM/Y81kevy83wP+Sst+nutFTYOGg3d1lsxg==",
"dev": true
},
"node_modules/gopd": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/gopd/-/gopd-1.0.1.tgz",
"integrity": "sha512-d65bNlIadxvpb/A2abVdlqKqV563juRnZ1Wtk6s1sIR8uNsXR70xqIzVqxVf1eTqDunwT2MkczEeaezCKTZhwA==",
✨(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
"dev": true,
"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
"get-intrinsic": "^1.1.3"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/graceful-fs": {
"version": "4.2.11",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.11.tgz",
🌐(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
"integrity": "sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ=="
✨(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) 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
"node_modules/graphemer": {
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/graphemer/-/graphemer-1.4.0.tgz",
"integrity": "sha512-EtKwoO6kxCL9WO5xipiHTZlSzBm7WLT627TqC/uVRd0HKmq8NXyebnNYxDoBi7wt8eTWrUrKXCOVaFq9x1kgag==",
✨(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
"dev": true
},
🌐(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
"node_modules/gulp-sort": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/gulp-sort/-/gulp-sort-2.0.0.tgz",
"integrity": "sha512-MyTel3FXOdh1qhw1yKhpimQrAmur9q1X0ZigLmCOxouQD+BD3za9/89O+HfbgBQvvh4igEbp0/PUWO+VqGYG1g==",
"dependencies": {
"through2": "^2.0.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
"node_modules/has-bigints": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/has-bigints/-/has-bigints-1.0.2.tgz",
"integrity": "sha512-tSvCKtBr9lkF0Ex0aQiP9N+OpV4zi2r/Nee5VkRDbaqv35RLYMzbwQfFSZZH0kR+Rd6302UJZ2p/bJCEoR3VoQ==",
"dev": true,
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
✨(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) 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
"node_modules/has-property-descriptors": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/has-property-descriptors/-/has-property-descriptors-1.0.2.tgz",
"integrity": "sha512-55JNKuIW+vq4Ke1BjOTjM2YctQIvCT7GFzHwmfZPGo5wnrgkid0YQtnAleFSqumZm4az3n2BS+erby5ipJdgrg==",
✨(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
"dev": true,
"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
"es-define-property": "^1.0.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
},
♻️(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
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/has-proto": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/has-proto/-/has-proto-1.0.3.tgz",
"integrity": "sha512-SJ1amZAJUiZS+PhsVLf5tGydlaVB8EdFpaSO4gmiUKUOxk8qzn5AIy4ZeJUmh22znIdk/uMAUT2pl3FxzVUH+Q==",
"dev": true,
✨(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
"engines": {
♻️(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
"node": ">= 0.4"
✨(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) 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
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/has-symbols": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.3.tgz",
"integrity": "sha512-l3LCuF6MgDNwTDKkdYGEihYjt5pRPbEg46rtlmnSPlUbgmB8LOIrKJbYYFBSbnPaJexMKtiPO8hmeRjRz2Td+A==",
"dev": true,
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
✨(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) 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
"node_modules/has-tostringtag": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/has-tostringtag/-/has-tostringtag-1.0.2.tgz",
"integrity": "sha512-NqADB8VjPFLM2V0VvHUewwwsw0ZWBaIdgo+ieHtK3hasLz4qeCRjYcqfB6AQrBggRKppKF8L52/VqdVsO47Dlw==",
✨(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
"dev": true,
"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
"has-symbols": "^1.0.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
},
"engines": {
♻️(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
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/hasown": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/hasown/-/hasown-2.0.2.tgz",
"integrity": "sha512-0hJU9SCPvmMzIBdZFqNPXWa6dqh7WdH0cII9y+CyS8rG3nL48Bclra9HmKhVVUHyPWNH5Y7xDwAB7bfgSjkUMQ==",
✨(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
"dev": true,
"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
"function-bind": "^1.1.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
},
"engines": {
♻️(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
"node": ">= 0.4"
✨(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) 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
"node_modules/heimdalljs": {
"version": "0.2.6",
"resolved": "https://registry.npmjs.org/heimdalljs/-/heimdalljs-0.2.6.tgz",
"integrity": "sha512-o9bd30+5vLBvBtzCPwwGqpry2+n0Hi6H1+qwt6y+0kwRHGGF8TFIhJPmnuM0xO97zaKrDZMwO/V56fAnn8m/tA==",
"dependencies": {
"rsvp": "~3.2.1"
}
},
"node_modules/heimdalljs-logger": {
"version": "0.1.10",
"resolved": "https://registry.npmjs.org/heimdalljs-logger/-/heimdalljs-logger-0.1.10.tgz",
"integrity": "sha512-pO++cJbhIufVI/fmB/u2Yty3KJD0TqNPecehFae0/eps0hkZ3b4Zc/PezUMOpYuHFQbA7FxHZxa305EhmjLj4g==",
"dependencies": {
"debug": "^2.2.0",
"heimdalljs": "^0.2.6"
}
},
"node_modules/heimdalljs-logger/node_modules/debug": {
"version": "2.6.9",
"resolved": "https://registry.npmjs.org/debug/-/debug-2.6.9.tgz",
"integrity": "sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==",
"dependencies": {
"ms": "2.0.0"
}
},
"node_modules/heimdalljs-logger/node_modules/ms": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.0.0.tgz",
"integrity": "sha512-Tpp60P6IUJDTuOq/5Z8cdskzJujfwqfOTkrwIwj7IRISpnkJnT6SyJ4PCPnGMoFjC9ddhal5KVIYtAt97ix05A=="
},
"node_modules/heimdalljs/node_modules/rsvp": {
"version": "3.2.1",
"resolved": "https://registry.npmjs.org/rsvp/-/rsvp-3.2.1.tgz",
"integrity": "sha512-Rf4YVNYpKjZ6ASAmibcwTNciQ5Co5Ztq6iZPEykHpkoflnD/K5ryE/rHehFsTm4NJj8nKDhbi3eKBWGogmNnkg=="
},
"node_modules/hoofd": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "1.7.3",
"resolved": "https://registry.npmjs.org/hoofd/-/hoofd-1.7.3.tgz",
"integrity": "sha512-ssVCn3i3w97C4ubB6Xf4oGbil5lj/r9rn7ZRlY5p1JmLa6i7ZviCk9Huo9WDK2OvP6K7HTga5+SRnw07e2uKOw==",
"license": "MIT",
🌐(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
"peerDependencies": {
"react": ">= 16.8.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
"node_modules/hookable": {
"version": "5.5.3",
"resolved": "https://registry.npmjs.org/hookable/-/hookable-5.5.3.tgz",
"integrity": "sha512-Yc+BQe8SvoXH1643Qez1zqLRmbA5rCL+sSmk6TVos0LWVfNIB7PGncdlId77WzLGSIB5KaWgTaNTs2lNVEI6VQ==",
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"dev": true,
"license": "MIT"
✨(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) draft sound design on notifications More a brainsto idea inspired from Gmeet than a polished feature. Try adding sound notification to add a new dimension on the user experience.
2024-09-11 12:02:01 +02:00
"node_modules/howler": {
"version": "2.2.4",
"resolved": "https://registry.npmjs.org/howler/-/howler-2.2.4.tgz",
"integrity": "sha512-iARIBPgcQrwtEr+tALF+rapJ8qSc+Set2GJQl7xT1MQzWaVkFebdJhR3alVlSiUf5U7nAANKuj3aWpwerocD5w=="
},
🌐(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
"node_modules/html-parse-stringify": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/html-parse-stringify/-/html-parse-stringify-3.0.1.tgz",
"integrity": "sha512-KknJ50kTInJ7qIScF3jeaFRpMpE8/lfiTdzf/twXyPBLAGrLRTmkz3AdTnKeh40X8k9L2fdYwEp/42WGXIRGcg==",
"dependencies": {
"void-elements": "3.1.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
}
},
🌐(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
"node_modules/htmlparser2": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "9.1.0",
"resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-9.1.0.tgz",
"integrity": "sha512-5zfg6mHUoaer/97TxnGpxmbR7zJtPwIYFMZ/H5ucTlPZhKvtum05yiPK3Mgai3a0DyVxv7qYqoweaEd2nrYQzQ==",
🌐(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
"funding": [
"https://github.com/fb55/htmlparser2?sponsor=1",
{
"type": "github",
"url": "https://github.com/sponsors/fb55"
}
],
"dependencies": {
"domelementtype": "^2.3.0",
"domhandler": "^5.0.3",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"domutils": "^3.1.0",
"entities": "^4.5.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
}
},
"node_modules/i18next": {
⬆️(dependencies) update js dependencies
2025-01-27 14:32:11 +00:00
"version": "24.2.2",
"resolved": "https://registry.npmjs.org/i18next/-/i18next-24.2.2.tgz",
"integrity": "sha512-NE6i86lBCKRYZa5TaUDkU5S4HFgLIEJRLr3Whf2psgaxBleQ2LC1YW1Vc+SCgkAW7VEzndT6al6+CzegSUHcTQ==",
🌐(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
"funding": [
{
"type": "individual",
"url": "https://locize.com"
},
{
"type": "individual",
"url": "https://locize.com/i18next.html"
},
{
"type": "individual",
"url": "https://www.i18next.com/how-to/faq#i18next-is-awesome.-how-can-i-support-the-project"
}
],
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
🌐(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
"dependencies": {
"@babel/runtime": "^7.23.2"
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
},
"peerDependencies": {
"typescript": "^5"
},
"peerDependenciesMeta": {
"typescript": {
"optional": true
}
🌐(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
}
},
"node_modules/i18next-browser-languagedetector": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "8.0.2",
"resolved": "https://registry.npmjs.org/i18next-browser-languagedetector/-/i18next-browser-languagedetector-8.0.2.tgz",
"integrity": "sha512-shBvPmnIyZeD2VU5jVGIOWP7u9qNG3Lj7mpaiPFpbJ3LVfHZJvVzKR4v1Cb91wAOFpNw442N+LGPzHOHsten2g==",
"license": "MIT",
🌐(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
"dependencies": {
"@babel/runtime": "^7.23.2"
}
},
"node_modules/i18next-parser": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "9.1.0",
"resolved": "https://registry.npmjs.org/i18next-parser/-/i18next-parser-9.1.0.tgz",
"integrity": "sha512-HuuTdZ7VoDHtBnB8x9Vwt/DT4XgflGkRgIDhmjxy5Aa6YYzaRpkMqIcR3GDO+LVX09CYG9K+T10x+JeZfsl4sw==",
"license": "MIT",
🌐(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
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@babel/runtime": "^7.25.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
"broccoli-plugin": "^4.0.7",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cheerio": "^1.0.0",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"colors": "^1.4.0",
"commander": "^12.1.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
"eol": "^0.9.1",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"esbuild": "^0.24.0",
"fs-extra": "^11.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
"gulp-sort": "^2.0.0",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"i18next": "^23.5.1 || ^24.2.0",
"js-yaml": "^4.1.0",
"lilconfig": "^3.1.2",
"rsvp": "^4.8.5",
🌐(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
"sort-keys": "^5.0.0",
"typescript": "^5.0.4",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"vinyl": "^3.0.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
"vinyl-fs": "^4.0.0"
},
"bin": {
"i18next": "bin/cli.js"
},
"engines": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"node": "^18.0.0 || ^20.0.0 || ^22.0.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
"npm": ">=6",
"yarn": ">=1"
}
},
"node_modules/i18next-parser/node_modules/@esbuild/aix-ppc64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/aix-ppc64/-/aix-ppc64-0.24.2.tgz",
"integrity": "sha512-thpVCb/rhxE/BnMLQ7GReQLLN8q9qbHmI55F4489/ByVg2aQaQ6kbcLb6FHkocZzQhxc4gx0sCk0tJkKBFzDhA==",
🌐(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
"cpu": [
"ppc64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"aix"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/android-arm": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/android-arm/-/android-arm-0.24.2.tgz",
"integrity": "sha512-tmwl4hJkCfNHwFB3nBa8z1Uy3ypZpxqxfTQOcHX+xRByyYgunVbZ9MzUUfb0RxaHIMnbHagwAxuTL+tnNM+1/Q==",
🌐(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
"cpu": [
"arm"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"android"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/android-arm64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/android-arm64/-/android-arm64-0.24.2.tgz",
"integrity": "sha512-cNLgeqCqV8WxfcTIOeL4OAtSmL8JjcN6m09XIgro1Wi7cF4t/THaWEa7eL5CMoMBdjoHOTh/vwTO/o2TRXIyzg==",
🌐(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
"cpu": [
"arm64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"android"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/android-x64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/android-x64/-/android-x64-0.24.2.tgz",
"integrity": "sha512-B6Q0YQDqMx9D7rvIcsXfmJfvUYLoP722bgfBlO5cGvNVb5V/+Y7nhBE3mHV9OpxBf4eAS2S68KZztiPaWq4XYw==",
🌐(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
"cpu": [
"x64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"android"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/darwin-arm64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/darwin-arm64/-/darwin-arm64-0.24.2.tgz",
"integrity": "sha512-kj3AnYWc+CekmZnS5IPu9D+HWtUI49hbnyqk0FLEJDbzCIQt7hg7ucF1SQAilhtYpIujfaHr6O0UHlzzSPdOeA==",
🌐(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
"cpu": [
"arm64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"darwin"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/darwin-x64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/darwin-x64/-/darwin-x64-0.24.2.tgz",
"integrity": "sha512-WeSrmwwHaPkNR5H3yYfowhZcbriGqooyu3zI/3GGpF8AyUdsrrP0X6KumITGA9WOyiJavnGZUwPGvxvwfWPHIA==",
🌐(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
"cpu": [
"x64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"darwin"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/freebsd-arm64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/freebsd-arm64/-/freebsd-arm64-0.24.2.tgz",
"integrity": "sha512-UN8HXjtJ0k/Mj6a9+5u6+2eZ2ERD7Edt1Q9IZiB5UZAIdPnVKDoG7mdTVGhHJIeEml60JteamR3qhsr1r8gXvg==",
🌐(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
"cpu": [
"arm64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"freebsd"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/freebsd-x64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/freebsd-x64/-/freebsd-x64-0.24.2.tgz",
"integrity": "sha512-TvW7wE/89PYW+IevEJXZ5sF6gJRDY/14hyIGFXdIucxCsbRmLUcjseQu1SyTko+2idmCw94TgyaEZi9HUSOe3Q==",
🌐(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
"cpu": [
"x64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"freebsd"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/linux-arm": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-arm/-/linux-arm-0.24.2.tgz",
"integrity": "sha512-n0WRM/gWIdU29J57hJyUdIsk0WarGd6To0s+Y+LwvlC55wt+GT/OgkwoXCXvIue1i1sSNWblHEig00GBWiJgfA==",
🌐(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
"cpu": [
"arm"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/linux-arm64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-arm64/-/linux-arm64-0.24.2.tgz",
"integrity": "sha512-7HnAD6074BW43YvvUmE/35Id9/NB7BeX5EoNkK9obndmZBUk8xmJJeU7DwmUeN7tkysslb2eSl6CTrYz6oEMQg==",
🌐(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
"cpu": [
"arm64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/linux-ia32": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-ia32/-/linux-ia32-0.24.2.tgz",
"integrity": "sha512-sfv0tGPQhcZOgTKO3oBE9xpHuUqguHvSo4jl+wjnKwFpapx+vUDcawbwPNuBIAYdRAvIDBfZVvXprIj3HA+Ugw==",
🌐(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
"cpu": [
"ia32"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/linux-loong64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-loong64/-/linux-loong64-0.24.2.tgz",
"integrity": "sha512-CN9AZr8kEndGooS35ntToZLTQLHEjtVB5n7dl8ZcTZMonJ7CCfStrYhrzF97eAecqVbVJ7APOEe18RPI4KLhwQ==",
🌐(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
"cpu": [
"loong64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/linux-mips64el": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-mips64el/-/linux-mips64el-0.24.2.tgz",
"integrity": "sha512-iMkk7qr/wl3exJATwkISxI7kTcmHKE+BlymIAbHO8xanq/TjHaaVThFF6ipWzPHryoFsesNQJPE/3wFJw4+huw==",
🌐(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
"cpu": [
"mips64el"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/linux-ppc64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-ppc64/-/linux-ppc64-0.24.2.tgz",
"integrity": "sha512-shsVrgCZ57Vr2L8mm39kO5PPIb+843FStGt7sGGoqiiWYconSxwTiuswC1VJZLCjNiMLAMh34jg4VSEQb+iEbw==",
🌐(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
"cpu": [
"ppc64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/linux-riscv64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-riscv64/-/linux-riscv64-0.24.2.tgz",
"integrity": "sha512-4eSFWnU9Hhd68fW16GD0TINewo1L6dRrB+oLNNbYyMUAeOD2yCK5KXGK1GH4qD/kT+bTEXjsyTCiJGHPZ3eM9Q==",
🌐(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
"cpu": [
"riscv64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/linux-s390x": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-s390x/-/linux-s390x-0.24.2.tgz",
"integrity": "sha512-S0Bh0A53b0YHL2XEXC20bHLuGMOhFDO6GN4b3YjRLK//Ep3ql3erpNcPlEFed93hsQAjAQDNsvcK+hV90FubSw==",
🌐(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
"cpu": [
"s390x"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/linux-x64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-x64/-/linux-x64-0.24.2.tgz",
"integrity": "sha512-8Qi4nQcCTbLnK9WoMjdC9NiTG6/E38RNICU6sUNqK0QFxCYgoARqVqxdFmWkdonVsvGqWhmm7MO0jyTqLqwj0Q==",
🌐(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
"cpu": [
"x64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/netbsd-x64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/netbsd-x64/-/netbsd-x64-0.24.2.tgz",
"integrity": "sha512-VefFaQUc4FMmJuAxmIHgUmfNiLXY438XrL4GDNV1Y1H/RW3qow68xTwjZKfj/+Plp9NANmzbH5R40Meudu8mmw==",
🌐(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
"cpu": [
"x64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"netbsd"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/openbsd-x64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/openbsd-x64/-/openbsd-x64-0.24.2.tgz",
"integrity": "sha512-+iDS6zpNM6EnJyWv0bMGLWSWeXGN/HTaF/LXHXHwejGsVi+ooqDfMCCTerNFxEkM3wYVcExkeGXNqshc9iMaOA==",
🌐(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
"cpu": [
"x64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"openbsd"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/sunos-x64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/sunos-x64/-/sunos-x64-0.24.2.tgz",
"integrity": "sha512-hTdsW27jcktEvpwNHJU4ZwWFGkz2zRJUz8pvddmXPtXDzVKTTINmlmga3ZzwcuMpUvLw7JkLy9QLKyGpD2Yxig==",
🌐(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
"cpu": [
"x64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"sunos"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/win32-arm64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/win32-arm64/-/win32-arm64-0.24.2.tgz",
"integrity": "sha512-LihEQ2BBKVFLOC9ZItT9iFprsE9tqjDjnbulhHoFxYQtQfai7qfluVODIYxt1PgdoyQkz23+01rzwNwYfutxUQ==",
🌐(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
"cpu": [
"arm64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"win32"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/win32-ia32": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/win32-ia32/-/win32-ia32-0.24.2.tgz",
"integrity": "sha512-q+iGUwfs8tncmFC9pcnD5IvRHAzmbwQ3GPS5/ceCyHdjXubwQWI12MKWSNSMYLJMq23/IUCvJMS76PDqXe1fxA==",
🌐(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
"cpu": [
"ia32"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"win32"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/@esbuild/win32-x64": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/win32-x64/-/win32-x64-0.24.2.tgz",
"integrity": "sha512-7VTgWzgMGvup6aSqDPLiW5zHaxYJGTO4OokMjIlrCtf+VpEL+cXKtCvg723iguPYI5oaUNdS+/V7OU2gvXVWEg==",
🌐(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
"cpu": [
"x64"
],
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"optional": true,
"os": [
"win32"
],
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
}
},
"node_modules/i18next-parser/node_modules/esbuild": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/esbuild/-/esbuild-0.24.2.tgz",
"integrity": "sha512-+9egpBW8I3CD5XPe0n6BfT5fxLzxrlDzqydF3aviG+9ni1lDC/OvMHcxqEFV0+LANZG5R1bFMWfUrjVsdwxJvA==",
🌐(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
"hasInstallScript": true,
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
🌐(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
"bin": {
"esbuild": "bin/esbuild"
},
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">=18"
🌐(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
},
"optionalDependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@esbuild/aix-ppc64": "0.24.2",
"@esbuild/android-arm": "0.24.2",
"@esbuild/android-arm64": "0.24.2",
"@esbuild/android-x64": "0.24.2",
"@esbuild/darwin-arm64": "0.24.2",
"@esbuild/darwin-x64": "0.24.2",
"@esbuild/freebsd-arm64": "0.24.2",
"@esbuild/freebsd-x64": "0.24.2",
"@esbuild/linux-arm": "0.24.2",
"@esbuild/linux-arm64": "0.24.2",
"@esbuild/linux-ia32": "0.24.2",
"@esbuild/linux-loong64": "0.24.2",
"@esbuild/linux-mips64el": "0.24.2",
"@esbuild/linux-ppc64": "0.24.2",
"@esbuild/linux-riscv64": "0.24.2",
"@esbuild/linux-s390x": "0.24.2",
"@esbuild/linux-x64": "0.24.2",
"@esbuild/netbsd-arm64": "0.24.2",
"@esbuild/netbsd-x64": "0.24.2",
"@esbuild/openbsd-arm64": "0.24.2",
"@esbuild/openbsd-x64": "0.24.2",
"@esbuild/sunos-x64": "0.24.2",
"@esbuild/win32-arm64": "0.24.2",
"@esbuild/win32-ia32": "0.24.2",
"@esbuild/win32-x64": "0.24.2"
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
}
},
🌐(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
"node_modules/i18next-resources-to-backend": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/i18next-resources-to-backend/-/i18next-resources-to-backend-1.2.1.tgz",
"integrity": "sha512-okHbVA+HZ7n1/76MsfhPqDou0fptl2dAlhRDu2ideXloRRduzHsqDOznJBef+R3DFZnbvWoBW+KxJ7fnFjd6Yw==",
"dependencies": {
"@babel/runtime": "^7.23.2"
}
},
"node_modules/iconv-lite": {
"version": "0.6.3",
"resolved": "https://registry.npmjs.org/iconv-lite/-/iconv-lite-0.6.3.tgz",
"integrity": "sha512-4fCk79wshMdzMp2rH06qWrJE4iolqLhCUH+OiuIgU++RB0+94NlDL81atO7GX55uUKueo0txHNtvEyI6D7WdMw==",
"dependencies": {
"safer-buffer": ">= 2.1.2 < 3.0.0"
},
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/ieee754": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/ieee754/-/ieee754-1.2.1.tgz",
"integrity": "sha512-dcyqhDvX1C46lXZcVqCpK+FtMRQVdIMN6/Df5js2zouUsqG7I6sFxitIC+7KYK29KdXOLHdu9zL4sFnoVQnqaA==",
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
]
},
"node_modules/ignore": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "5.3.2",
"resolved": "https://registry.npmjs.org/ignore/-/ignore-5.3.2.tgz",
"integrity": "sha512-hsBTNUqQTDwkWtcdYI2i06Y/nUBEsNEDJKjWdigLvegy8kDuJAS8uRlpkkcQpyEXL0Z/pjDy5HBmMjRCJ2gq+g==",
🌐(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
"dev": true,
"engines": {
"node": ">= 4"
}
},
"node_modules/import-fresh": {
"version": "3.3.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
"resolved": "https://registry.npmjs.org/import-fresh/-/import-fresh-3.3.0.tgz",
"integrity": "sha512-veYYhQa+D1QBKznvhUHxb8faxlrwUnxseDAbAp457E0wLNio2bOSKnjYDhMj+YiAq61xrMGhQk9iXVk5FzgQMw==",
✨(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
"dev": true,
♻️(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
"dependencies": {
"parent-module": "^1.0.0",
"resolve-from": "^4.0.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
"engines": {
"node": ">=6"
♻️(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
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
✨(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) 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
"node_modules/imurmurhash": {
"version": "0.1.4",
"resolved": "https://registry.npmjs.org/imurmurhash/-/imurmurhash-0.1.4.tgz",
"integrity": "sha512-JmXMZ6wuvDmLiHEml9ykzqO6lwFbof0GG4IkcGaENdCRDDmMVnny7s5HsIgHCbaq0w2MyPhDqkhTUgS2LU2PHA==",
✨(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
"dev": true,
"engines": {
♻️(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
"node": ">=0.8.19"
✨(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) 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
"node_modules/inflight": {
"version": "1.0.6",
"resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.6.tgz",
"integrity": "sha512-k92I/b08q4wvFscXCLvqfsHCrjrF7yiXsQuIVvVE7N82W3+aqpzuUdBbfhWcy/FZR3/4IgflMgKLOsvPDrGCJA==",
"deprecated": "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.",
✨(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
"once": "^1.3.0",
"wrappy": "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
}
},
♻️(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
"node_modules/inherits": {
"version": "2.0.4",
"resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.4.tgz",
🌐(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
"integrity": "sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ=="
♻️(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
},
"node_modules/internal-slot": {
"version": "1.0.7",
"resolved": "https://registry.npmjs.org/internal-slot/-/internal-slot-1.0.7.tgz",
"integrity": "sha512-NGnrKwXzSms2qUUih/ILZ5JBqNTSa1+ZmP6flaIp6KmSElgE9qdndzS3cqjrDovwFdmwsGsLdeFgB6suw+1e9g==",
✨(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
"dev": true,
♻️(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
"dependencies": {
"es-errors": "^1.3.0",
"hasown": "^2.0.0",
"side-channel": "^1.0.4"
✨(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) 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
"engines": {
"node": ">= 0.4"
✨(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) 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
"node_modules/intl-messageformat": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "10.7.14",
"resolved": "https://registry.npmjs.org/intl-messageformat/-/intl-messageformat-10.7.14.tgz",
"integrity": "sha512-mMGnE4E1otdEutV5vLUdCxRJygHB5ozUBxsPB5qhitewssrS/qGruq9bmvIRkkGsNeK5ZWLfYRld18UHGTIifQ==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "BSD-3-Clause",
✨(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) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@formatjs/ecma402-abstract": "2.3.2",
"@formatjs/fast-memoize": "2.2.6",
"@formatjs/icu-messageformat-parser": "2.11.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"tslib": "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
}
},
♻️(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
"node_modules/is-array-buffer": {
"version": "3.0.4",
"resolved": "https://registry.npmjs.org/is-array-buffer/-/is-array-buffer-3.0.4.tgz",
"integrity": "sha512-wcjaerHw0ydZwfhiKbXJWLDY8A7yV7KhjQOpb83hGgGfId/aQa4TOvwyzn2PuswW2gPCYEL/nEAiSVpdOj1lXw==",
✨(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
"dev": true,
♻️(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
"dependencies": {
"call-bind": "^1.0.2",
"get-intrinsic": "^1.2.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
"engines": {
♻️(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
"node": ">= 0.4"
✨(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
},
"funding": {
♻️(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
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/is-bigint": {
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/is-bigint/-/is-bigint-1.0.4.tgz",
"integrity": "sha512-zB9CruMamjym81i2JZ3UMn54PKGsQzsJeo6xvN3HJJ4CAsQNB6iRutp2To77OfCNuoxspsIhzaPoO1zyCEhFOg==",
✨(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
"dev": true,
"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
"has-bigints": "^1.0.1"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/is-binary-path": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/is-binary-path/-/is-binary-path-2.1.0.tgz",
"integrity": "sha512-ZMERYes6pDydyuGidse7OsHxtbI7WVeUEozgR/g7rd0xUimYNlvZRE/K2MgZTjWy725IfelLeVcEM97mmtRGXw==",
✨(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
"dev": true,
"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
"binary-extensions": "^2.0.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
},
"engines": {
♻️(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
"node": ">=8"
✨(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) 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
"node_modules/is-boolean-object": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/is-boolean-object/-/is-boolean-object-1.1.2.tgz",
"integrity": "sha512-gDYaKHJmnj4aWxyj6YHyXVpdQawtVLHU5cb+eztPGczf6cjuTdwve5ZIEfgXqH4e57An1D1AKf8CZ3kYrQRqYA==",
✨(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
"dev": true,
"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
"call-bind": "^1.0.2",
"has-tostringtag": "^1.0.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
},
"engines": {
♻️(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
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/is-callable": {
"version": "1.2.7",
"resolved": "https://registry.npmjs.org/is-callable/-/is-callable-1.2.7.tgz",
"integrity": "sha512-1BC0BVFhS/p0qtw6enp8e+8OD0UrK0oFLztSjNzhcKA3WDuJxxAPXzPuPtKkjEY9UUoEWlX/8fgKeu2S8i9JTA==",
"dev": true,
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
✨(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) 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
"node_modules/is-data-view": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/is-data-view/-/is-data-view-1.0.1.tgz",
"integrity": "sha512-AHkaJrsUVW6wq6JS8y3JnM/GJF/9cf+k20+iDzlSaJrinEo5+7vRiteOSwBhHRiAyQATN1AmY4hwzxJKPmYf+w==",
✨(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
"dev": true,
♻️(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
"dependencies": {
"is-typed-array": "^1.1.13"
},
✨(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
"engines": {
♻️(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
"node": ">= 0.4"
✨(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
},
"funding": {
♻️(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
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/is-date-object": {
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/is-date-object/-/is-date-object-1.0.5.tgz",
"integrity": "sha512-9YQaSxsAiSwcvS33MBk3wTCVnWK+HhF8VZR2jRxehM16QcVOdHqPn4VPHmRK4lSr38n9JriurInLcP90xsYNfQ==",
✨(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
"dev": true,
"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
"has-tostringtag": "^1.0.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
},
"engines": {
♻️(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
"node": ">= 0.4"
✨(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
},
"funding": {
♻️(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
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/is-extglob": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/is-extglob/-/is-extglob-2.1.1.tgz",
"integrity": "sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==",
✨(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
"engines": {
♻️(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
"node": ">=0.10.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
}
},
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"node_modules/is-fullwidth-code-point": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz",
"integrity": "sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=8"
}
},
♻️(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
"node_modules/is-glob": {
"version": "4.0.3",
"resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz",
"integrity": "sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==",
✨(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
"is-extglob": "^2.1.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
},
"engines": {
♻️(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
"node": ">=0.10.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
"node_modules/is-negated-glob": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-negated-glob/-/is-negated-glob-1.0.0.tgz",
"integrity": "sha512-czXVVn/QEmgvej1f50BZ648vUI+em0xqMq2Sn+QncCLN4zj1UAxlT+kw/6ggQTOaZPd1HqKQGEqbpQVtJucWug==",
"engines": {
"node": ">=0.10.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
"node_modules/is-negative-zero": {
"version": "2.0.3",
"resolved": "https://registry.npmjs.org/is-negative-zero/-/is-negative-zero-2.0.3.tgz",
"integrity": "sha512-5KoIu2Ngpyek75jXodFvnafB6DJgr3u8uuK0LEZJjrU19DrMD3EVERaR8sjz8CCGgpZvxPl9SuE1GMVPFHx1mw==",
✨(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
"dev": true,
♻️(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
"engines": {
"node": ">= 0.4"
✨(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) 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
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/is-number": {
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/is-number/-/is-number-7.0.0.tgz",
"integrity": "sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==",
"dev": true,
✨(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
"engines": {
♻️(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
"node": ">=0.12.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
}
},
♻️(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
"node_modules/is-number-object": {
"version": "1.0.7",
"resolved": "https://registry.npmjs.org/is-number-object/-/is-number-object-1.0.7.tgz",
"integrity": "sha512-k1U0IRzLMo7ZlYIfzRu23Oh6MiIFasgpb9X76eqfFZAqwH44UI4KTBvBYIZ1dSL9ZzChTB9ShHfLkR4pdW5krQ==",
✨(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
"dev": true,
"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
"has-tostringtag": "^1.0.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
},
"engines": {
♻️(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
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/is-path-inside": {
"version": "3.0.3",
"resolved": "https://registry.npmjs.org/is-path-inside/-/is-path-inside-3.0.3.tgz",
"integrity": "sha512-Fd4gABb+ycGAmKou8eMftCupSir5lRxqf4aD/vd0cD2qc4HL07OjCeuHMr8Ro4CoMaeCKDB0/ECBOVWjTwUvPQ==",
✨(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
"dev": true,
"engines": {
♻️(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
"node": ">=8"
✨(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) 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
"node_modules/is-plain-obj": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/is-plain-obj/-/is-plain-obj-4.1.0.tgz",
"integrity": "sha512-+Pgi+vMuUNkJyExiMBt5IlFoMyKnr5zhJ4Uspz58WOhBF5QoIZkFyNHIbBAtHwzVAgk5RtndVNsDRN61/mmDqg==",
"engines": {
"node": ">=12"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
♻️(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
"node_modules/is-regex": {
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/is-regex/-/is-regex-1.1.4.tgz",
"integrity": "sha512-kvRdxDsxZjhzUX07ZnLydzS1TU/TJlTUHHY4YLL87e37oUA49DfkLqgy+VjFocowy29cKvcSiu+kIv728jTTVg==",
✨(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
"dev": true,
♻️(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
"dependencies": {
"call-bind": "^1.0.2",
"has-tostringtag": "^1.0.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
"engines": {
♻️(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
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/is-shared-array-buffer": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/is-shared-array-buffer/-/is-shared-array-buffer-1.0.3.tgz",
"integrity": "sha512-nA2hv5XIhLR3uVzDDfCIknerhx8XUKnstuOERPNNIinXG7v9u+ohXF67vxm4TPTEPU6lm61ZkwP3c9PCB97rhg==",
✨(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
"dev": true,
"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
"call-bind": "^1.0.7"
✨(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
},
"engines": {
♻️(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
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/is-string": {
"version": "1.0.7",
"resolved": "https://registry.npmjs.org/is-string/-/is-string-1.0.7.tgz",
"integrity": "sha512-tE2UXzivje6ofPW7l23cjDOMa09gb7xlAqG6jG5ej6uPV32TlWP3NKPigtaGeHNu9fohccRYvIiZMfOOnOYUtg==",
✨(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
"dev": true,
"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
"has-tostringtag": "^1.0.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
},
"engines": {
♻️(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
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/is-symbol": {
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/is-symbol/-/is-symbol-1.0.4.tgz",
"integrity": "sha512-C/CPBqKWnvdcxqIARxyOh4v1UUEOCHpgDa0WYgpKDFMszcrPcffg5uhwSgPCLD2WWxmq6isisz87tzT01tuGhg==",
✨(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
"dev": true,
"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
"has-symbols": "^1.0.2"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/is-typed-array": {
"version": "1.1.13",
"resolved": "https://registry.npmjs.org/is-typed-array/-/is-typed-array-1.1.13.tgz",
"integrity": "sha512-uZ25/bUAlUY5fR4OKT4rZQEBrzQWYV9ZJYGGsUmEJ6thodVJ1HX64ePQ6Z0qPWP+m+Uq6e9UugrE38jeYsDSMw==",
✨(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
"dev": true,
"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
"which-typed-array": "^1.1.14"
✨(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
},
"engines": {
♻️(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
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/is-valid-glob": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/is-valid-glob/-/is-valid-glob-1.0.0.tgz",
"integrity": "sha512-AhiROmoEFDSsjx8hW+5sGwgKVIORcXnrlAx/R0ZSeaPw70Vw0CqkGBBhHGL58Uox2eXnU1AnvXJl1XlyedO5bA==",
"engines": {
"node": ">=0.10.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
"node_modules/is-weakref": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/is-weakref/-/is-weakref-1.0.2.tgz",
"integrity": "sha512-qctsuLZmIQ0+vSSMfoVvyFe2+GSEvnmZ2ezTup1SBse9+twCCeial6EEi3Nc2KFcf6+qz2FBPnjXsk8xhKSaPQ==",
✨(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
"dev": true,
"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
"call-bind": "^1.0.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
},
♻️(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
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/is-what": {
"version": "4.1.16",
"resolved": "https://registry.npmjs.org/is-what/-/is-what-4.1.16.tgz",
"integrity": "sha512-ZhMwEosbFJkA0YhFnNDgTM4ZxDRsS6HqTo7qsZM08fehyRYIYa0yHu5R6mgo1n/8MgaPBXiPimPD77baVFYg+A==",
✨(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
"dev": true,
"engines": {
♻️(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
"node": ">=12.13"
},
"funding": {
"url": "https://github.com/sponsors/mesqueeb"
✨(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) 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
"node_modules/isarray": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-2.0.5.tgz",
"integrity": "sha512-xHjhDr3cNBK0BzdUJSPXZntQUx/mwMS5Rw4A7lPJ90XGAO6ISP/ePDNuo0vhqOZU+UD5JoodwCAAoZQd3FeAKw==",
✨(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
"dev": true
},
♻️(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
"node_modules/isexe": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz",
"integrity": "sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==",
✨(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
"dev": true
},
♻️(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
"node_modules/javascript-stringify": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/javascript-stringify/-/javascript-stringify-2.1.0.tgz",
"integrity": "sha512-JVAfqNPTvNq3sB/VHQJAFxN/sPgKnsKrCwyRt15zwNCdrMMJDdcEOdubuy+DuJYYdm0ox1J4uzEuYKkN+9yhVg==",
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"dev": true,
"license": "MIT"
♻️(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
},
"node_modules/js-tokens": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/js-tokens/-/js-tokens-4.0.0.tgz",
"integrity": "sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ=="
},
"node_modules/js-yaml": {
"version": "4.1.0",
"resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.0.tgz",
"integrity": "sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==",
"dependencies": {
"argparse": "^2.0.1"
},
"bin": {
"js-yaml": "bin/js-yaml.js"
✨(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) 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
"node_modules/jsesc": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/jsesc/-/jsesc-3.1.0.tgz",
"integrity": "sha512-/sM3dO2FOzXjKQhJuo0Q173wf2KOo8t4I8vHy6lF9poUp7bKT0/NHE8fPX23PwfhnykfqnC2xRxOnVw5XuGIaA==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
♻️(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
"bin": {
"jsesc": "bin/jsesc"
✨(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
},
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=6"
✨(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) 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
"node_modules/json-buffer": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/json-buffer/-/json-buffer-3.0.1.tgz",
"integrity": "sha512-4bV5BfR2mqfQTJm+V5tPPdf+ZpuhiIvTuAB5g8kcrXOZpTT/QwwVRWBywX1ozr6lEuPdbHxwaJlm9G6mI2sfSQ==",
"dev": true
},
"node_modules/json-schema-traverse": {
"version": "0.4.1",
"resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz",
"integrity": "sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==",
"dev": true
},
"node_modules/json-stable-stringify-without-jsonify": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/json-stable-stringify-without-jsonify/-/json-stable-stringify-without-jsonify-1.0.1.tgz",
"integrity": "sha512-Bdboy+l7tA3OGW6FjyFHWkP5LuByj1Tk33Ljyq0axyzdk9//JSi2u3fP1QSmd1KNwq6VOKYGlAu87CisVir6Pw==",
"dev": true
},
"node_modules/json5": {
"version": "2.2.3",
"resolved": "https://registry.npmjs.org/json5/-/json5-2.2.3.tgz",
"integrity": "sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg==",
✨(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
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
♻️(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
"bin": {
"json5": "lib/cli.js"
✨(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
},
"engines": {
♻️(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
"node": ">=6"
✨(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) 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
"node_modules/jsonc-parser": {
"version": "3.3.1",
"resolved": "https://registry.npmjs.org/jsonc-parser/-/jsonc-parser-3.3.1.tgz",
"integrity": "sha512-HUgH65KyejrUFPvHFPbqOY0rsFip3Bo5wb4ngvdi1EpCYWUQDC5V+Y7mZws+DLkr4M//zQJoanu1SP+87Dv1oQ==",
"dev": true
},
"node_modules/jsonfile": {
"version": "6.1.0",
"resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-6.1.0.tgz",
"integrity": "sha512-5dgndWOriYSm5cnYaJNhalLNDKOqFwyDB/rr1E9ZsGciGvKPs8R2xYGCacuf3z6K1YKDz182fd+fY3cn3pMqXQ==",
✨(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
"universalify": "^2.0.0"
},
"optionalDependencies": {
"graceful-fs": "^4.1.6"
✨(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) 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
"node_modules/jsx-ast-utils": {
"version": "3.3.5",
"resolved": "https://registry.npmjs.org/jsx-ast-utils/-/jsx-ast-utils-3.3.5.tgz",
"integrity": "sha512-ZZow9HBI5O6EPgSJLUb8n2NKgmVWTwCvHGwFuJlMjvLFqlGG6pjirPhtdsseaLZjSibD8eegzmYpUZwoIlj2cQ==",
✨(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
"dev": true,
"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
"array-includes": "^3.1.6",
"array.prototype.flat": "^1.3.1",
"object.assign": "^4.1.4",
"object.values": "^1.1.6"
✨(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
},
"engines": {
♻️(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
"node": ">=4.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
}
},
♻️(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
"node_modules/keyv": {
"version": "4.5.4",
"resolved": "https://registry.npmjs.org/keyv/-/keyv-4.5.4.tgz",
"integrity": "sha512-oxVHkHR/EJf2CNXnWxRLW6mg7JyCCUcG0DtEGmL2ctUo1PNTin1PUil+r/+4r5MpVgC/fn1kjsx7mjSujKqIpw==",
✨(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
"dev": true,
♻️(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
"dependencies": {
"json-buffer": "3.0.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
}
},
♻️(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
"node_modules/kleur": {
"version": "4.1.5",
"resolved": "https://registry.npmjs.org/kleur/-/kleur-4.1.5.tgz",
"integrity": "sha512-o+NO+8WrRiQEE4/7nwRJhN1HWpVmJm511pBHUxPLtp0BUISzlBplORYSmTclCnJvQq2tKu/sgl3xVpkc7ZWuQQ==",
✨(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
"dev": true,
"engines": {
♻️(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
"node": ">=6"
✨(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) 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
"node_modules/language-subtag-registry": {
"version": "0.3.23",
"resolved": "https://registry.npmjs.org/language-subtag-registry/-/language-subtag-registry-0.3.23.tgz",
"integrity": "sha512-0K65Lea881pHotoGEa5gDlMxt3pctLi2RplBb7Ezh4rRdLEOtgi7n4EwK9lamnUCkKBqaeKRVebTq6BAxSkpXQ==",
✨(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
"dev": true
},
♻️(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
"node_modules/language-tags": {
"version": "1.0.9",
"resolved": "https://registry.npmjs.org/language-tags/-/language-tags-1.0.9.tgz",
"integrity": "sha512-MbjN408fEndfiQXbFQ1vnd+1NoLDsnQW41410oQBXiyXDMYH5z505juWa4KUE1LqxRC7DgOgZDbKLxHIwm27hA==",
✨(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
"dev": true,
♻️(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
"dependencies": {
"language-subtag-registry": "^0.3.20"
},
✨(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
"engines": {
♻️(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
"node": ">=0.10"
✨(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) 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
"node_modules/lead": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/lead/-/lead-4.0.0.tgz",
"integrity": "sha512-DpMa59o5uGUWWjruMp71e6knmwKU3jRBBn1kjuLWN9EeIOxNeSAwvHf03WIl8g/ZMR2oSQC9ej3yeLBwdDc/pg==",
"engines": {
"node": ">=10.13.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
"node_modules/levn": {
"version": "0.4.1",
"resolved": "https://registry.npmjs.org/levn/-/levn-0.4.1.tgz",
"integrity": "sha512-+bT2uH4E5LGE7h/n3evcS/sQlJXCpIp6ym8OWJ5eV6+67Dsql/LaaT7qJBAt2rzfoa/5QBGBhxDix1dMt2kQKQ==",
✨(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
"dev": true,
♻️(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
"dependencies": {
"prelude-ls": "^1.2.1",
"type-check": "~0.4.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
"engines": {
♻️(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
"node": ">= 0.8.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
}
},
♻️(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
"node_modules/lightningcss": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "1.25.1",
"resolved": "https://registry.npmjs.org/lightningcss/-/lightningcss-1.25.1.tgz",
"integrity": "sha512-V0RMVZzK1+rCHpymRv4URK2lNhIRyO8g7U7zOFwVAhJuat74HtkjIQpQRKNCwFEYkRGpafOpmXXLoaoBcyVtBg==",
✨(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
"dev": true,
"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
"detect-libc": "^1.0.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
},
"engines": {
♻️(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
"node": ">= 12.0.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
},
"funding": {
♻️(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
"type": "opencollective",
"url": "https://opencollective.com/parcel"
},
"optionalDependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"lightningcss-darwin-arm64": "1.25.1",
"lightningcss-darwin-x64": "1.25.1",
"lightningcss-freebsd-x64": "1.25.1",
"lightningcss-linux-arm-gnueabihf": "1.25.1",
"lightningcss-linux-arm64-gnu": "1.25.1",
"lightningcss-linux-arm64-musl": "1.25.1",
"lightningcss-linux-x64-gnu": "1.25.1",
"lightningcss-linux-x64-musl": "1.25.1",
"lightningcss-win32-x64-msvc": "1.25.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
}
},
"node_modules/lightningcss-darwin-arm64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "1.25.1",
"resolved": "https://registry.npmjs.org/lightningcss-darwin-arm64/-/lightningcss-darwin-arm64-1.25.1.tgz",
"integrity": "sha512-G4Dcvv85bs5NLENcu/s1f7ehzE3D5ThnlWSDwE190tWXRQCQaqwcuHe+MGSVI/slm0XrxnaayXY+cNl3cSricw==",
♻️(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
"cpu": [
"arm64"
],
✨(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
"dev": true,
♻️(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
"optional": true,
"os": [
"darwin"
],
✨(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
"engines": {
♻️(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
"node": ">= 12.0.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/parcel"
✨(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) 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
"node_modules/lightningcss-darwin-x64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "1.25.1",
"resolved": "https://registry.npmjs.org/lightningcss-darwin-x64/-/lightningcss-darwin-x64-1.25.1.tgz",
"integrity": "sha512-dYWuCzzfqRueDSmto6YU5SoGHvZTMU1Em9xvhcdROpmtOQLorurUZz8+xFxZ51lCO2LnYbfdjZ/gCqWEkwixNg==",
♻️(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
"cpu": [
"x64"
],
✨(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
"dev": true,
♻️(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
"optional": true,
"os": [
"darwin"
],
✨(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
"engines": {
♻️(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
"node": ">= 12.0.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
},
♻️(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
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/parcel"
✨(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) 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
"node_modules/lightningcss-freebsd-x64": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "1.25.1",
"resolved": "https://registry.npmjs.org/lightningcss-freebsd-x64/-/lightningcss-freebsd-x64-1.25.1.tgz",
"integrity": "sha512-hXoy2s9A3KVNAIoKz+Fp6bNeY+h9c3tkcx1J3+pS48CqAt+5bI/R/YY4hxGL57fWAIquRjGKW50arltD6iRt/w==",
♻️(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
"cpu": [
"x64"
],
✨(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
"dev": true,
♻️(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
"optional": true,
"os": [
"freebsd"
],
✨(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
"engines": {
♻️(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
"node": ">= 12.0.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/parcel"
✨(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) 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
"node_modules/lightningcss-linux-arm-gnueabihf": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "1.25.1",
"resolved": "https://registry.npmjs.org/lightningcss-linux-arm-gnueabihf/-/lightningcss-linux-arm-gnueabihf-1.25.1.tgz",
"integrity": "sha512-tWyMgHFlHlp1e5iW3EpqvH5MvsgoN7ZkylBbG2R2LWxnvH3FuWCJOhtGcYx9Ks0Kv0eZOBud789odkYLhyf1ng==",
♻️(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
"cpu": [
"arm"
],
✨(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
"dev": true,
♻️(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
"optional": true,
"os": [
"linux"
],
✨(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
"engines": {
♻️(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
"node": ">= 12.0.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/parcel"
✨(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) 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
"node_modules/lightningcss-linux-arm64-gnu": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "1.25.1",
"resolved": "https://registry.npmjs.org/lightningcss-linux-arm64-gnu/-/lightningcss-linux-arm64-gnu-1.25.1.tgz",
"integrity": "sha512-Xjxsx286OT9/XSnVLIsFEDyDipqe4BcLeB4pXQ/FEA5+2uWCCuAEarUNQumRucnj7k6ftkAHUEph5r821KBccQ==",
♻️(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
"cpu": [
"arm64"
],
✨(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
"dev": true,
♻️(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
"optional": true,
"os": [
"linux"
],
"engines": {
"node": ">= 12.0.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/parcel"
✨(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) 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
"node_modules/lightningcss-linux-arm64-musl": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "1.25.1",
"resolved": "https://registry.npmjs.org/lightningcss-linux-arm64-musl/-/lightningcss-linux-arm64-musl-1.25.1.tgz",
"integrity": "sha512-IhxVFJoTW8wq6yLvxdPvyHv4NjzcpN1B7gjxrY3uaykQNXPHNIpChLB52+wfH+yS58zm1PL4LemUp8u9Cfp6Bw==",
♻️(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
"cpu": [
"arm64"
],
✨(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
"dev": true,
♻️(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
"optional": true,
"os": [
"linux"
],
✨(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
"engines": {
♻️(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
"node": ">= 12.0.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/parcel"
✨(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) 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
"node_modules/lightningcss-linux-x64-gnu": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "1.25.1",
"resolved": "https://registry.npmjs.org/lightningcss-linux-x64-gnu/-/lightningcss-linux-x64-gnu-1.25.1.tgz",
"integrity": "sha512-RXIaru79KrREPEd6WLXfKfIp4QzoppZvD3x7vuTKkDA64PwTzKJ2jaC43RZHRt8BmyIkRRlmywNhTRMbmkPYpA==",
♻️(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
"cpu": [
"x64"
],
✨(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
"dev": true,
♻️(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
"optional": true,
"os": [
"linux"
],
✨(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
"engines": {
♻️(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
"node": ">= 12.0.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/parcel"
✨(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) 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
"node_modules/lightningcss-linux-x64-musl": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "1.25.1",
"resolved": "https://registry.npmjs.org/lightningcss-linux-x64-musl/-/lightningcss-linux-x64-musl-1.25.1.tgz",
"integrity": "sha512-TdcNqFsAENEEFr8fJWg0Y4fZ/nwuqTRsIr7W7t2wmDUlA8eSXVepeeONYcb+gtTj1RaXn/WgNLB45SFkz+XBZA==",
♻️(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
"cpu": [
"x64"
],
✨(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
"dev": true,
♻️(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
"optional": true,
"os": [
"linux"
],
"engines": {
"node": ">= 12.0.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/parcel"
✨(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) 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
"node_modules/lightningcss-win32-x64-msvc": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "1.25.1",
"resolved": "https://registry.npmjs.org/lightningcss-win32-x64-msvc/-/lightningcss-win32-x64-msvc-1.25.1.tgz",
"integrity": "sha512-9KZZkmmy9oGDSrnyHuxP6iMhbsgChUiu/NSgOx+U1I/wTngBStDf2i2aGRCHvFqj19HqqBEI4WuGVQBa2V6e0A==",
♻️(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
"cpu": [
"x64"
],
✨(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
"dev": true,
♻️(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
"optional": true,
"os": [
"win32"
],
✨(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
"engines": {
♻️(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
"node": ">= 12.0.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/parcel"
✨(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) 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
"node_modules/lilconfig": {
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/lilconfig/-/lilconfig-3.1.2.tgz",
"integrity": "sha512-eop+wDAvpItUys0FWkHIKeC9ybYrTGbU41U5K7+bttZZeohvnY7M9dZ5kB21GNWiFT2q1OoPTvncPCgSOVO5ow==",
"engines": {
"node": ">=14"
},
"funding": {
"url": "https://github.com/sponsors/antonk52"
}
},
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"node_modules/livekit-client": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "2.8.1",
"resolved": "https://registry.npmjs.org/livekit-client/-/livekit-client-2.8.1.tgz",
"integrity": "sha512-HPv9iHNrnBANI9ucK7CKZspx0sBZK3hjR2EbwaV08+J3RM9+tNGL2ob2n76nxJLEZG7LzdWlLZdbr4fQBP6Hkg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"dependencies": {
⬆️(frontend) bump LiveKit-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-16 18:42:31 +01:00
"@livekit/mutex": "1.1.1",
"@livekit/protocol": "1.30.0",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"events": "^3.3.0",
"loglevel": "^1.8.0",
"sdp-transform": "^2.14.1",
"ts-debounce": "^4.0.0",
⬆️(frontend) bump LiveKit-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-16 18:42:31 +01:00
"tslib": "2.8.1",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"typed-emitter": "^2.1.0",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"webrtc-adapter": "^9.0.0"
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
}
},
✨(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
"node_modules/locate-path": {
"version": "6.0.0",
"resolved": "https://registry.npmjs.org/locate-path/-/locate-path-6.0.0.tgz",
"integrity": "sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==",
"dev": true,
"dependencies": {
"p-locate": "^5.0.0"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"node_modules/lodash.debounce": {
"version": "4.0.8",
"resolved": "https://registry.npmjs.org/lodash.debounce/-/lodash.debounce-4.0.8.tgz",
♻️(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
"integrity": "sha512-FT1yDzDYEoYWhnSGnpE/4Kj1fLZkDFyqRb7fNt6FdYOSxlUWAtp42Eh6Wb0rGIv/m9Bgo7x4GhQbm5Ys4SG5ow=="
},
"node_modules/lodash.memoize": {
"version": "4.1.2",
"resolved": "https://registry.npmjs.org/lodash.memoize/-/lodash.memoize-4.1.2.tgz",
"integrity": "sha512-t7j+NzmgnQzTAYXcsHYLgimltOV1MXHtlOWf6GjL9Kj8GK5FInw5JotxvbOs+IvV1/Dzo04/fCGfLVs7aXb4Ag==",
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"dev": true,
"license": "MIT"
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
},
✨(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
"node_modules/lodash.merge": {
"version": "4.6.2",
"resolved": "https://registry.npmjs.org/lodash.merge/-/lodash.merge-4.6.2.tgz",
"integrity": "sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==",
"dev": true
},
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"node_modules/lodash.truncate": {
"version": "4.4.2",
"resolved": "https://registry.npmjs.org/lodash.truncate/-/lodash.truncate-4.4.2.tgz",
"integrity": "sha512-jttmRe7bRse52OsWIMDLaXxWqRAmtIUccAQ3garviCqJjafXOfNMO0yMfNpdD6zbGaTU0P5Nz7e7gAT6cKmJRw==",
"dev": true,
"license": "MIT"
},
♻️(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
"node_modules/lodash.uniq": {
"version": "4.5.0",
"resolved": "https://registry.npmjs.org/lodash.uniq/-/lodash.uniq-4.5.0.tgz",
"integrity": "sha512-xfBaXQd9ryd9dlSDvnvI0lvxfLJlYAZzXomUYzLKtUeOQvOP5piqAWuGtrhWeqaXK9hhoM/iyJc5AV+XfsX3HQ==",
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"dev": true,
"license": "MIT"
♻️(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
},
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"node_modules/loglevel": {
"version": "1.9.1",
"resolved": "https://registry.npmjs.org/loglevel/-/loglevel-1.9.1.tgz",
"integrity": "sha512-hP3I3kCrDIMuRwAwHltphhDM1r8i55H33GgqjXbrisuJhF4kRhW1dNuxsRklp4bXl8DSdLaNLuiL4A/LWRfxvg==",
"engines": {
"node": ">= 0.6.0"
},
"funding": {
"type": "tidelift",
"url": "https://tidelift.com/funding/github/npm/loglevel"
}
},
♻️(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
"node_modules/look-it-up": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/look-it-up/-/look-it-up-2.1.0.tgz",
"integrity": "sha512-nMoGWW2HurtuJf6XAL56FWTDCWLOTSsanrgwOyaR5Y4e3zfG5N/0cU5xWZSEU3tBxhQugRbV1xL9jb+ug7yZww==",
"dev": true
},
✨(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
"node_modules/loose-envify": {
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/loose-envify/-/loose-envify-1.4.0.tgz",
"integrity": "sha512-lyuxPGr/Wfhrlem2CL/UcnUc1zcqKAImBDzukY7Y5F/yQiNdko6+fRLevlw1HgMySw7f611UIY408EtxRSoK3Q==",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
✨(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": {
"js-tokens": "^3.0.0 || ^4.0.0"
},
"bin": {
"loose-envify": "cli.js"
}
},
"node_modules/lru-cache": {
"version": "5.1.1",
"resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-5.1.1.tgz",
"integrity": "sha512-KpNARQA3Iwv+jTA0utUVVbrh+Jlrr1Fv0e56GGzAFOXN7dk/FviaDW8LHmK52DlcH4WP2n6gI8vN1aesBFgo9w==",
"dev": true,
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "ISC",
✨(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": {
"yallist": "^3.0.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
"node_modules/magic-string": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "0.30.17",
"resolved": "https://registry.npmjs.org/magic-string/-/magic-string-0.30.17.tgz",
"integrity": "sha512-sNPKHvyjVf7gyjwS4xGTaW/mCnF8wnjtifKBEhxfZ7E/S8tQ0rssrwGNn6q8JH/ohItJfSQp9mBtQYuTlH5QnA==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"@jridgewell/sourcemap-codec": "^1.5.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
}
},
🌐(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
"node_modules/matcher-collection": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/matcher-collection/-/matcher-collection-2.0.1.tgz",
"integrity": "sha512-daE62nS2ZQsDg9raM0IlZzLmI2u+7ZapXBwdoeBUKAYERPDDIc0qNqA8E0Rp2D+gspKR7BgIFP52GeujaGXWeQ==",
"dependencies": {
"@types/minimatch": "^3.0.3",
"minimatch": "^3.0.2"
},
"engines": {
"node": "6.* || 8.* || >= 10.*"
}
},
"node_modules/matcher-collection/node_modules/brace-expansion": {
"version": "1.1.11",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz",
"integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==",
"dependencies": {
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
}
},
"node_modules/matcher-collection/node_modules/minimatch": {
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz",
"integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==",
"dependencies": {
"brace-expansion": "^1.1.7"
},
"engines": {
"node": "*"
}
},
♻️(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
"node_modules/merge-anything": {
"version": "5.1.7",
"resolved": "https://registry.npmjs.org/merge-anything/-/merge-anything-5.1.7.tgz",
"integrity": "sha512-eRtbOb1N5iyH0tkQDAoQ4Ipsp/5qSR79Dzrz8hEPxRX10RWWR/iQXdoKmBSRCThY1Fh5EhISDtpSc93fpxUniQ==",
"dev": true,
"dependencies": {
"is-what": "^4.1.8"
},
"engines": {
"node": ">=12.13"
},
"funding": {
"url": "https://github.com/sponsors/mesqueeb"
}
},
✨(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
"node_modules/merge2": {
"version": "1.4.1",
"resolved": "https://registry.npmjs.org/merge2/-/merge2-1.4.1.tgz",
"integrity": "sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==",
"dev": true,
"engines": {
♻️(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
"node": ">= 8"
}
},
"node_modules/microdiff": {
"version": "1.3.2",
"resolved": "https://registry.npmjs.org/microdiff/-/microdiff-1.3.2.tgz",
"integrity": "sha512-pKy60S2febliZIbwdfEQKTtL5bLNxOyiRRmD400gueYl9XcHyNGxzHSlJWn9IMHwYXT0yohPYL08+bGozVk8cQ==",
"dev": true
},
"node_modules/micromatch": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "4.0.8",
"resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.8.tgz",
"integrity": "sha512-PXwfBhYu0hBCPw8Dn0E+WDYb7af3dSLVWKi3HGv84IdF4TyFoC0ysxFd0Goxw7nSv4T/PzEJQxsYsEiFCKo2BA==",
♻️(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": true,
"dependencies": {
"braces": "^3.0.3",
"picomatch": "^2.3.1"
},
"engines": {
"node": ">=8.6"
}
},
"node_modules/minimatch": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "9.0.5",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-9.0.5.tgz",
"integrity": "sha512-G6T0ZX48xgozx7587koeX9Ys2NYy6Gmv//P89sEte9V9whIapMNF4idKxnW2QtCcLiTWlb/wfCabAtAFWhhBow==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "ISC",
♻️(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
"dependencies": {
"brace-expansion": "^2.0.1"
},
"engines": {
"node": ">=16 || 14 >=14.17"
},
"funding": {
"url": "https://github.com/sponsors/isaacs"
}
},
"node_modules/mitt": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/mitt/-/mitt-3.0.1.tgz",
"integrity": "sha512-vKivATfr97l2/QBCYAkXYDbrIWPM2IIKEl7YPhjCvKlG3kE2gm+uBo6nEXK3M5/Ffh/FLpKExzOQ3JJoJGFKBw=="
},
🌐(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
"node_modules/mktemp": {
"version": "0.4.0",
"resolved": "https://registry.npmjs.org/mktemp/-/mktemp-0.4.0.tgz",
"integrity": "sha512-IXnMcJ6ZyTuhRmJSjzvHSRhlVPiN9Jwc6e59V0bEJ0ba6OBeX2L0E+mRN1QseeOF4mM+F1Rit6Nh7o+rl2Yn/A==",
"engines": {
"node": ">0.9"
}
},
♻️(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
"node_modules/mlly": {
"version": "1.7.1",
"resolved": "https://registry.npmjs.org/mlly/-/mlly-1.7.1.tgz",
"integrity": "sha512-rrVRZRELyQzrIUAVMHxP97kv+G786pHmOKzuFII8zDYahFBS7qnHh2AlYSl1GAHhaMPCz6/oHjVMcfFYgFYHgA==",
"dev": true,
"dependencies": {
"acorn": "^8.11.3",
"pathe": "^1.1.2",
"pkg-types": "^1.1.1",
"ufo": "^1.5.3"
}
},
"node_modules/mlly/node_modules/pkg-types": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/pkg-types/-/pkg-types-1.2.0.tgz",
"integrity": "sha512-+ifYuSSqOQ8CqP4MbZA5hDpb97n3E8SVWdJe+Wms9kj745lmd3b7EZJiqvmLwAlmRfjrI7Hi5z3kdBJ93lFNPA==",
♻️(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": true,
"dependencies": {
"confbox": "^0.1.7",
"mlly": "^1.7.1",
"pathe": "^1.1.2"
}
},
"node_modules/ms": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "2.1.3",
"resolved": "https://registry.npmjs.org/ms/-/ms-2.1.3.tgz",
"integrity": "sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==",
♻️(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": true
},
"node_modules/nanoid": {
🔒️(frontend) bump nanoid from 3.3.7 to 3.3.8 in /src/frontend 3.3.8 fixed a way to break Nano ID by passing non-integer size. Raised as a moderate severity issue by Dependabot.
2024-12-16 23:27:45 +00:00
"version": "3.3.8",
"resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.3.8.tgz",
"integrity": "sha512-WNLf5Sd8oZxOm+TzppcYk8gVOgP+l58xNy58D0nbUnOxOWRWvlcCV4kUF7ltmI6PsrLl/BgKEyS4mqsGChFN0w==",
♻️(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": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/ai"
}
],
"bin": {
"nanoid": "bin/nanoid.cjs"
},
"engines": {
"node": "^10 || ^12 || ^13.7 || ^14 || >=15.0.1"
}
},
"node_modules/natural-compare": {
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/natural-compare/-/natural-compare-1.4.0.tgz",
"integrity": "sha512-OWND8ei3VtNC9h7V60qff3SVobHr996CTwgxubgyQYEpg290h9J0buyECNNJexkFm5sOajh5G116RYA1c8ZMSw==",
"dev": true
},
"node_modules/node-eval": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/node-eval/-/node-eval-2.0.0.tgz",
"integrity": "sha512-Ap+L9HznXAVeJj3TJ1op6M6bg5xtTq8L5CU/PJxtkhea/DrIxdTknGKIECKd/v/Lgql95iuMAYvIzBNd0pmcMg==",
"dev": true,
"dependencies": {
"path-is-absolute": "1.0.1"
},
"engines": {
"node": ">= 4"
}
},
"node_modules/node-releases": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "2.0.19",
"resolved": "https://registry.npmjs.org/node-releases/-/node-releases-2.0.19.tgz",
"integrity": "sha512-xxOWJsBKtzAq7DY0J+DTzuz58K8e7sJbdgwkbMWQe8UYB6ekmsQ45q0M/tJDsGaZmbC+l7n57UV8Hl5tHxO9uw==",
"dev": true,
"license": "MIT"
♻️(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
},
"node_modules/normalize-path": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/normalize-path/-/normalize-path-3.0.0.tgz",
"integrity": "sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==",
🌐(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
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/now-and-later": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/now-and-later/-/now-and-later-3.0.0.tgz",
"integrity": "sha512-pGO4pzSdaxhWTGkfSfHx3hVzJVslFPwBp2Myq9MYN/ChfJZF87ochMAXnvz6/58RJSf5ik2q9tXprBBrk2cpcg==",
"dependencies": {
"once": "^1.4.0"
},
"engines": {
"node": ">= 10.13.0"
}
},
"node_modules/nth-check": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.1.1.tgz",
"integrity": "sha512-lqjrjmaOoAnWfMmBPL+XNnynZh2+swxiX3WUE0s4yEHI6m+AwrK2UZOimIRl3X/4QctVqS8AiZjFqyOGrMXb/w==",
"dependencies": {
"boolbase": "^1.0.0"
},
"funding": {
"url": "https://github.com/fb55/nth-check?sponsor=1"
}
},
"node_modules/object-assign": {
"version": "4.1.1",
"resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.1.1.tgz",
"integrity": "sha512-rJgTQnkUnH1sFw8yT6VSU3zD3sWmu6sZhIseY8VX+GRu3P6F7Fu+JNDoXfklElbLJSnc3FUQHVe4cU5hj+BcUg==",
♻️(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
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/object-inspect": {
"version": "1.13.2",
"resolved": "https://registry.npmjs.org/object-inspect/-/object-inspect-1.13.2.tgz",
"integrity": "sha512-IRZSRuzJiynemAXPYtPe5BoI/RESNYR7TYm50MC5Mqbd3Jmw5y790sErYw3V6SryFJD64b74qQQs9wn5Bg/k3g==",
"dev": true,
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/object-keys": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz",
"integrity": "sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==",
"dev": true,
"engines": {
"node": ">= 0.4"
}
},
"node_modules/object-path": {
"version": "0.11.8",
"resolved": "https://registry.npmjs.org/object-path/-/object-path-0.11.8.tgz",
"integrity": "sha512-YJjNZrlXJFM42wTBn6zgOJVar9KFJvzx6sTWDte8sWZF//cnjl0BxHNpfZx+ZffXX63A9q0b1zsFiBX4g4X5KA==",
"dev": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
♻️(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
"engines": {
"node": ">= 10.12.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
}
},
♻️(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
"node_modules/object.assign": {
"version": "4.1.5",
"resolved": "https://registry.npmjs.org/object.assign/-/object.assign-4.1.5.tgz",
"integrity": "sha512-byy+U7gp+FVwmyzKPYhW2h5l3crpmGsxl7X2s8y43IgxvG4g3QZ6CffDtsNQy1WsmZpQbO+ybo0AlW7TY6DcBQ==",
✨(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
"dev": true,
"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
"call-bind": "^1.0.5",
"define-properties": "^1.2.1",
"has-symbols": "^1.0.3",
"object-keys": "^1.1.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
},
"engines": {
♻️(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
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/object.fromentries": {
"version": "2.0.8",
"resolved": "https://registry.npmjs.org/object.fromentries/-/object.fromentries-2.0.8.tgz",
"integrity": "sha512-k6E21FzySsSK5a21KRADBd/NGneRegFO5pLHfdQLpRDETUNJueLXs3WCzyQ3tFRDYgbq3KHGXfTbi2bs8WQ6rQ==",
✨(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
"dev": true,
"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
"call-bind": "^1.0.7",
"define-properties": "^1.2.1",
"es-abstract": "^1.23.2",
"es-object-atoms": "^1.0.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
},
"engines": {
♻️(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
"node": ">= 0.4"
✨(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
},
"funding": {
♻️(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
"url": "https://github.com/sponsors/ljharb"
✨(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) 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
"node_modules/object.values": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/object.values/-/object.values-1.2.0.tgz",
"integrity": "sha512-yBYjY9QX2hnRmZHAjG/f13MzmBzxzYgQhFrke06TTyKY5zSTEqkOeukBzIdVA3j3ulu8Qa3MbVFShV7T2RmGtQ==",
✨(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
"dev": true,
♻️(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
"dependencies": {
"call-bind": "^1.0.7",
"define-properties": "^1.2.1",
"es-object-atoms": "^1.0.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
},
"engines": {
♻️(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
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
✨(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
}
},
"node_modules/once": {
"version": "1.4.0",
"resolved": "https://registry.npmjs.org/once/-/once-1.4.0.tgz",
"integrity": "sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==",
"dependencies": {
"wrappy": "1"
}
},
"node_modules/optionator": {
"version": "0.9.4",
"resolved": "https://registry.npmjs.org/optionator/-/optionator-0.9.4.tgz",
"integrity": "sha512-6IpQ7mKUxRcZNLIObR0hz7lxsapSSIYNZJwXPGeF0mTVqGKFIXj1DQcMoT22S3ROcLyY/rz0PWaWZ9ayWmad9g==",
"dev": true,
"dependencies": {
"deep-is": "^0.1.3",
"fast-levenshtein": "^2.0.6",
"levn": "^0.4.1",
"prelude-ls": "^1.2.1",
"type-check": "^0.4.0",
"word-wrap": "^1.2.5"
},
"engines": {
"node": ">= 0.8.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
"node_modules/outdent": {
"version": "0.8.0",
"resolved": "https://registry.npmjs.org/outdent/-/outdent-0.8.0.tgz",
"integrity": "sha512-KiOAIsdpUTcAXuykya5fnVVT+/5uS0Q1mrkRHcF89tpieSmY33O/tmc54CqwA+bfhbtEfZUNLHaPUiB9X3jt1A==",
"dev": true
},
✨(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
"node_modules/p-limit": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/p-limit/-/p-limit-3.1.0.tgz",
"integrity": "sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==",
"dev": true,
"dependencies": {
"yocto-queue": "^0.1.0"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
"node_modules/p-locate": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/p-locate/-/p-locate-5.0.0.tgz",
"integrity": "sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==",
"dev": true,
"dependencies": {
"p-limit": "^3.0.2"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/package-manager-detector": {
"version": "0.1.0",
"resolved": "https://registry.npmjs.org/package-manager-detector/-/package-manager-detector-0.1.0.tgz",
"integrity": "sha512-qRwvZgEE7geMY6xPChI3T0qrM0PL4s/AKiLnNVjhg3GdN2/fUUSrpGA5Z8mejMXauT1BS6RJIgWvSGAdqg8NnQ==",
"dev": true
♻️(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
},
✨(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
"node_modules/parent-module": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/parent-module/-/parent-module-1.0.1.tgz",
"integrity": "sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==",
"dev": true,
"dependencies": {
"callsites": "^3.0.0"
},
"engines": {
"node": ">=6"
}
},
🌐(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
"node_modules/parse5": {
"version": "7.1.2",
"resolved": "https://registry.npmjs.org/parse5/-/parse5-7.1.2.tgz",
"integrity": "sha512-Czj1WaSVpaoj0wbhMzLmWD69anp2WH7FXMB9n1Sy8/ZFF9jolSQVMu1Ij5WIyGmcBmhk7EOndpO4mIpihVqAXw==",
"dependencies": {
"entities": "^4.4.0"
},
"funding": {
"url": "https://github.com/inikulin/parse5?sponsor=1"
}
},
"node_modules/parse5-htmlparser2-tree-adapter": {
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/parse5-htmlparser2-tree-adapter/-/parse5-htmlparser2-tree-adapter-7.0.0.tgz",
"integrity": "sha512-B77tOZrqqfUfnVcOrUvfdLbz4pu4RopLD/4vmu3HUPswwTA8OH0EMW9BlWR2B0RCoiZRAHEUu7IxeP1Pd1UU+g==",
"dependencies": {
"domhandler": "^5.0.2",
"parse5": "^7.0.0"
},
"funding": {
"url": "https://github.com/inikulin/parse5?sponsor=1"
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/parse5-parser-stream": {
"version": "7.1.2",
"resolved": "https://registry.npmjs.org/parse5-parser-stream/-/parse5-parser-stream-7.1.2.tgz",
"integrity": "sha512-JyeQc9iwFLn5TbvvqACIF/VXG6abODeB3Fwmv/TGdLk2LfbWkaySGY72at4+Ty7EkPZj854u4CrICqNk2qIbow==",
"dependencies": {
"parse5": "^7.0.0"
},
"funding": {
"url": "https://github.com/inikulin/parse5?sponsor=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
"node_modules/path-browserify": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/path-browserify/-/path-browserify-1.0.1.tgz",
"integrity": "sha512-b7uo2UCUOYZcnF/3ID0lulOJi/bafxa1xPe7ZPsammBSpjSWQkjNxlt635YGS2MiR9GjvuXCtz2emr3jbsz98g==",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"dev": true,
"license": "MIT"
♻️(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
},
✨(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
"node_modules/path-exists": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/path-exists/-/path-exists-4.0.0.tgz",
"integrity": "sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==",
"dev": true,
"engines": {
"node": ">=8"
}
},
"node_modules/path-is-absolute": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.1.tgz",
"integrity": "sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg==",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/path-key": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/path-key/-/path-key-3.1.1.tgz",
"integrity": "sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==",
"dev": true,
"engines": {
"node": ">=8"
}
},
🌐(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
"node_modules/path-posix": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/path-posix/-/path-posix-1.0.0.tgz",
"integrity": "sha512-1gJ0WpNIiYcQydgg3Ed8KzvIqTsDpNwq+cjBCssvBtuTWjEqY1AW+i+OepiEMqDCzyro9B2sLAe4RBPajMYFiA=="
},
♻️(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
"node_modules/pathe": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/pathe/-/pathe-1.1.2.tgz",
"integrity": "sha512-whLdWMYL2TwI08hn8/ZqAbrVemu0LNaNNJZX73O6qaIdCTfXutsLhMkjdENX0qhsQ9uIimo4/aQOmXkoon2nDQ==",
"dev": true
},
"node_modules/perfect-debounce": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/perfect-debounce/-/perfect-debounce-1.0.0.tgz",
"integrity": "sha512-xCy9V055GLEqoFaHoC1SoLIaLmWctgCUaBaWxDZ7/Zx4CTyX7cJQLJOok/orfjZAh9kEYpjJa4d0KcJmCbctZA==",
"dev": true
},
✨(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
"node_modules/picocolors": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/picocolors/-/picocolors-1.1.1.tgz",
"integrity": "sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA==",
"dev": true,
"license": "ISC"
✨(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
},
"node_modules/picomatch": {
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/picomatch/-/picomatch-2.3.1.tgz",
"integrity": "sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==",
"engines": {
"node": ">=8.6"
},
"funding": {
"url": "https://github.com/sponsors/jonschlinkert"
}
},
♻️(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
"node_modules/pkg-types": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/pkg-types/-/pkg-types-1.0.3.tgz",
"integrity": "sha512-nN7pYi0AQqJnoLPC9eHFQ8AcyaixBUOwvqc5TDnIKCMEE6I0y8P7OKA7fPexsXGCGxQDl/cmrLAp26LhcwxZ4A==",
"dev": true,
"dependencies": {
"jsonc-parser": "^3.2.0",
"mlly": "^1.2.0",
"pathe": "^1.1.0"
}
},
"node_modules/pluralize": {
"version": "8.0.0",
"resolved": "https://registry.npmjs.org/pluralize/-/pluralize-8.0.0.tgz",
"integrity": "sha512-Nc3IT5yHzflTfbjgqWcCPpo7DaKy4FnpB0l/zCAW0Tc7jxAiuqSxHasntB3D7887LSrA93kDJ9IXovxJYxyLCA==",
"dev": true,
"engines": {
"node": ">=4"
}
},
"node_modules/possible-typed-array-names": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/possible-typed-array-names/-/possible-typed-array-names-1.0.0.tgz",
"integrity": "sha512-d7Uw+eZoloe0EHDIYoe+bQ5WXnGMOpmiZFTuMWCwpjzzkL2nTjcKiAk4hh8TjnGye2TwWOk3UXucZ+3rbmBa8Q==",
"dev": true,
"engines": {
"node": ">= 0.4"
}
},
✨(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
"node_modules/postcss": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "8.5.1",
"resolved": "https://registry.npmjs.org/postcss/-/postcss-8.5.1.tgz",
"integrity": "sha512-6oz2beyjc5VMn/KV1pPw8fliQkhBXrVn1Z3TVyqZxU8kZpzEKhBdmCFqI6ZbmGtamQvQGuU1sgPTk8ZrXDD7jQ==",
✨(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
"dev": true,
"funding": [
{
"type": "opencollective",
"url": "https://opencollective.com/postcss/"
},
{
"type": "tidelift",
"url": "https://tidelift.com/funding/github/npm/postcss"
},
{
"type": "github",
"url": "https://github.com/sponsors/ai"
}
],
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
✨(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": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"nanoid": "^3.3.8",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"picocolors": "^1.1.1",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"source-map-js": "^1.2.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
},
"engines": {
"node": "^10 || ^12 || >=14"
}
},
♻️(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
"node_modules/postcss-discard-duplicates": {
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"version": "7.0.1",
"resolved": "https://registry.npmjs.org/postcss-discard-duplicates/-/postcss-discard-duplicates-7.0.1.tgz",
"integrity": "sha512-oZA+v8Jkpu1ct/xbbrntHRsfLGuzoP+cpt0nJe5ED2FQF8n8bJtn7Bo28jSmBYwqgqnqkuSXJfSUEE7if4nClQ==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
♻️(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
"engines": {
"node": "^18.12.0 || ^20.9.0 || >=22.0"
},
"peerDependencies": {
"postcss": "^8.4.31"
}
},
"node_modules/postcss-discard-empty": {
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/postcss-discard-empty/-/postcss-discard-empty-7.0.0.tgz",
"integrity": "sha512-e+QzoReTZ8IAwhnSdp/++7gBZ/F+nBq9y6PomfwORfP7q9nBpK5AMP64kOt0bA+lShBFbBDcgpJ3X4etHg4lzA==",
"dev": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
♻️(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
"engines": {
"node": "^18.12.0 || ^20.9.0 || >=22.0"
},
"peerDependencies": {
"postcss": "^8.4.31"
}
},
"node_modules/postcss-merge-rules": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "7.0.4",
"resolved": "https://registry.npmjs.org/postcss-merge-rules/-/postcss-merge-rules-7.0.4.tgz",
"integrity": "sha512-ZsaamiMVu7uBYsIdGtKJ64PkcQt6Pcpep/uO90EpLS3dxJi6OXamIobTYcImyXGoW0Wpugh7DSD3XzxZS9JCPg==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"browserslist": "^4.23.3",
♻️(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
"caniuse-api": "^3.0.0",
"cssnano-utils": "^5.0.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"postcss-selector-parser": "^6.1.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
},
"engines": {
"node": "^18.12.0 || ^20.9.0 || >=22.0"
},
"peerDependencies": {
"postcss": "^8.4.31"
}
},
"node_modules/postcss-minify-selectors": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "7.0.4",
"resolved": "https://registry.npmjs.org/postcss-minify-selectors/-/postcss-minify-selectors-7.0.4.tgz",
"integrity": "sha512-JG55VADcNb4xFCf75hXkzc1rNeURhlo7ugf6JjiiKRfMsKlDzN9CXHZDyiG6x/zGchpjQS+UAgb1d4nqXqOpmA==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cssesc": "^3.0.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"postcss-selector-parser": "^6.1.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
},
"engines": {
"node": "^18.12.0 || ^20.9.0 || >=22.0"
},
"peerDependencies": {
"postcss": "^8.4.31"
}
},
"node_modules/postcss-nested": {
"version": "6.0.1",
"resolved": "https://registry.npmjs.org/postcss-nested/-/postcss-nested-6.0.1.tgz",
"integrity": "sha512-mEp4xPMi5bSWiMbsgoPfcP74lsWLHkQbZc3sY+jWYd65CUwXrUaTp0fmNpa01ZcETKlIgUdFN/MpS2xZtqL9dQ==",
"dev": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
♻️(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
"dependencies": {
"postcss-selector-parser": "^6.0.11"
},
"engines": {
"node": ">=12.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/postcss/"
},
"peerDependencies": {
"postcss": "^8.2.14"
}
},
"node_modules/postcss-normalize-whitespace": {
"version": "7.0.0",
"resolved": "https://registry.npmjs.org/postcss-normalize-whitespace/-/postcss-normalize-whitespace-7.0.0.tgz",
"integrity": "sha512-37/toN4wwZErqohedXYqWgvcHUGlT8O/m2jVkAfAe9Bd4MzRqlBmXrJRePH0e9Wgnz2X7KymTgTOaaFizQe3AQ==",
"dev": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
♻️(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
"dependencies": {
"postcss-value-parser": "^4.2.0"
},
"engines": {
"node": "^18.12.0 || ^20.9.0 || >=22.0"
},
"peerDependencies": {
"postcss": "^8.4.31"
}
},
"node_modules/postcss-selector-parser": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "6.1.2",
"resolved": "https://registry.npmjs.org/postcss-selector-parser/-/postcss-selector-parser-6.1.2.tgz",
"integrity": "sha512-Q8qQfPiZ+THO/3ZrOrO0cJJKfpYCagtMUkXbnEfmgUjwXg6z/WBeOyS9APBBPCTSiDV+s4SwQGu8yFsiMRIudg==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
♻️(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
"dependencies": {
"cssesc": "^3.0.0",
"util-deprecate": "^1.0.2"
},
"engines": {
"node": ">=4"
}
},
"node_modules/postcss-value-parser": {
"version": "4.2.0",
"resolved": "https://registry.npmjs.org/postcss-value-parser/-/postcss-value-parser-4.2.0.tgz",
"integrity": "sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ==",
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"dev": true,
"license": "MIT"
♻️(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
},
➕(frontend) add posthog dependency Posthog is a product analysis tool. Installed the js SDK to track product usage.
2024-09-17 10:45:58 +02:00
"node_modules/posthog-js": {
⬆️(dependencies) update js dependencies
2025-01-27 14:32:11 +00:00
"version": "1.210.2",
"resolved": "https://registry.npmjs.org/posthog-js/-/posthog-js-1.210.2.tgz",
"integrity": "sha512-rIbn/h9ur7uA0PS4dClOr9w6txLfHS94yh9yafA5VM2eXToM951XtMYtIQ6bi6wFzpvpFvTQFeYLQ/9/xZ59AQ==",
⬆️(frontend) update PostHog sdk Required by PostHog app, to benefits from latest survey features.
2024-11-17 22:53:11 +01:00
"license": "MIT",
➕(frontend) add posthog dependency Posthog is a product analysis tool. Installed the js SDK to track product usage.
2024-09-17 10:45:58 +02:00
"dependencies": {
⬆️(frontend) update PostHog sdk Required by PostHog app, to benefits from latest survey features.
2024-11-17 22:53:11 +01:00
"core-js": "^3.38.1",
➕(frontend) add posthog dependency Posthog is a product analysis tool. Installed the js SDK to track product usage.
2024-09-17 10:45:58 +02:00
"fflate": "^0.4.8",
"preact": "^10.19.3",
⬆️(frontend) update PostHog sdk Required by PostHog app, to benefits from latest survey features.
2024-11-17 22:53:11 +01:00
"web-vitals": "^4.2.0"
➕(frontend) add posthog dependency Posthog is a product analysis tool. Installed the js SDK to track product usage.
2024-09-17 10:45:58 +02:00
}
},
"node_modules/preact": {
"version": "10.24.0",
"resolved": "https://registry.npmjs.org/preact/-/preact-10.24.0.tgz",
"integrity": "sha512-aK8Cf+jkfyuZ0ZZRG9FbYqwmEiGQ4y/PUO4SuTWoyWL244nZZh7bd5h2APd4rSNDYTBNghg1L+5iJN3Skxtbsw==",
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/preact"
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/prelude-ls": {
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.2.1.tgz",
"integrity": "sha512-vkcDPrRZo1QZLbn5RLGPpg/WmIQ65qoWWhcGKf/b5eplkkarX0m9z8ppCat4mlOqUsWpyNuYgO3VRyrYHSzX5g==",
✨(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
"dev": true,
"engines": {
"node": ">= 0.8.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
"node_modules/prettier": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "3.4.2",
"resolved": "https://registry.npmjs.org/prettier/-/prettier-3.4.2.tgz",
"integrity": "sha512-e9MewbtFo+Fevyuxn/4rrcDAaq0IYxPGLvObpQjiZBMAzB9IGmzlnG9RZy3FFas+eBMu2vA0CszMeduow5dIuQ==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
♻️(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
"bin": {
"prettier": "bin/prettier.cjs"
},
"engines": {
"node": ">=14"
},
"funding": {
"url": "https://github.com/prettier/prettier?sponsor=1"
}
},
🌐(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
"node_modules/process-nextick-args": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-2.0.1.tgz",
"integrity": "sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag=="
},
"node_modules/promise-map-series": {
"version": "0.3.0",
"resolved": "https://registry.npmjs.org/promise-map-series/-/promise-map-series-0.3.0.tgz",
"integrity": "sha512-3npG2NGhTc8BWBolLLf8l/92OxMGaRLbqvIh9wjCHhDXNvk4zsxaTaCpiCunW09qWPrN2zeNSNwRLVBrQQtutA==",
"engines": {
"node": "10.* || >= 12.*"
}
},
♻️(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
"node_modules/proxy-compare": {
⬆️(dependencies) update js dependencies
2025-01-27 14:32:11 +00:00
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/proxy-compare/-/proxy-compare-3.0.1.tgz",
"integrity": "sha512-V9plBAt3qjMlS1+nC8771KNf6oJ12gExvaxnNzN/9yVRLdTv/lc+oJlnSzrdYDAvBfTStPCoiaCOTmTs0adv7Q==",
"license": "MIT"
♻️(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
},
✨(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
"node_modules/punycode": {
"version": "2.3.1",
"resolved": "https://registry.npmjs.org/punycode/-/punycode-2.3.1.tgz",
"integrity": "sha512-vYt7UD1U9Wg6138shLtLOvdAu+8DsC/ilFtEVHcH+wydcSpNE20AfSOduf6MkRFahL5FY7X1oU7nKVZFtfq8Fg==",
"dev": true,
"engines": {
"node": ">=6"
}
},
"node_modules/queue-microtask": {
"version": "1.2.3",
"resolved": "https://registry.npmjs.org/queue-microtask/-/queue-microtask-1.2.3.tgz",
"integrity": "sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
]
},
🌐(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
"node_modules/queue-tick": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/queue-tick/-/queue-tick-1.0.1.tgz",
"integrity": "sha512-kJt5qhMxoszgU/62PLP1CJytzd2NKetjSRnyuj31fDd3Rlcz3fzlFdFLD1SItunPwyqEOkca6GbV612BWfaBag=="
},
"node_modules/quick-temp": {
"version": "0.1.8",
"resolved": "https://registry.npmjs.org/quick-temp/-/quick-temp-0.1.8.tgz",
"integrity": "sha512-YsmIFfD9j2zaFwJkzI6eMG7y0lQP7YeWzgtFgNl38pGWZBSXJooZbOWwkcRot7Vt0Fg9L23pX0tqWU3VvLDsiA==",
"dependencies": {
"mktemp": "~0.4.0",
"rimraf": "^2.5.4",
"underscore.string": "~3.3.4"
}
},
"node_modules/quick-temp/node_modules/rimraf": {
"version": "2.7.1",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-2.7.1.tgz",
"integrity": "sha512-uWjbaKIK3T1OSVptzX7Nl6PvQ3qAGtKEtVRjRuazjfL3Bx5eI409VZSqgND+4UNnmzLVdPj9FqFJNPqBZFve4w==",
"deprecated": "Rimraf versions prior to v4 are no longer supported",
"dependencies": {
"glob": "^7.1.3"
},
"bin": {
"rimraf": "bin.js"
}
},
✨(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
"node_modules/react": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "18.3.1",
"resolved": "https://registry.npmjs.org/react/-/react-18.3.1.tgz",
"integrity": "sha512-wS+hAgJShR0KhEvPJArfuPVN1+Hz1t0Y6n5jLrGQbkb4urgPE/0Rve+1kMB1v/oWgHgm4WIcV+i7F2pTVj+2iQ==",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
✨(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": {
"loose-envify": "^1.1.0"
},
"engines": {
"node": ">=0.10.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
"node_modules/react-aria": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.37.0",
"resolved": "https://registry.npmjs.org/react-aria/-/react-aria-3.37.0.tgz",
"integrity": "sha512-u3WUEMTcbQFaoHauHO3KhPaBYzEv1o42EdPcLAs05GBw9Q6Axlqwo73UFgMrsc2ElwLAZ4EKpSdWHLo1R5gfiw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
"@internationalized/string": "^3.2.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/breadcrumbs": "^3.5.20",
"@react-aria/button": "^3.11.1",
"@react-aria/calendar": "^3.7.0",
"@react-aria/checkbox": "^3.15.1",
"@react-aria/color": "^3.0.3",
"@react-aria/combobox": "^3.11.1",
"@react-aria/datepicker": "^3.13.0",
"@react-aria/dialog": "^3.5.21",
"@react-aria/disclosure": "^3.0.1",
"@react-aria/dnd": "^3.8.1",
"@react-aria/focus": "^3.19.1",
"@react-aria/gridlist": "^3.10.1",
"@react-aria/i18n": "^3.12.5",
"@react-aria/interactions": "^3.23.0",
"@react-aria/label": "^3.7.14",
"@react-aria/link": "^3.7.8",
"@react-aria/listbox": "^3.14.0",
"@react-aria/menu": "^3.17.0",
"@react-aria/meter": "^3.4.19",
"@react-aria/numberfield": "^3.11.10",
"@react-aria/overlays": "^3.25.0",
"@react-aria/progress": "^3.4.19",
"@react-aria/radio": "^3.10.11",
"@react-aria/searchfield": "^3.8.0",
"@react-aria/select": "^3.15.1",
"@react-aria/selection": "^3.22.0",
"@react-aria/separator": "^3.4.5",
"@react-aria/slider": "^3.7.15",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-aria/ssr": "^3.9.7",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/switch": "^3.6.11",
"@react-aria/table": "^3.16.1",
"@react-aria/tabs": "^3.9.9",
"@react-aria/tag": "^3.4.9",
"@react-aria/textfield": "^3.16.0",
"@react-aria/tooltip": "^3.7.11",
"@react-aria/utils": "^3.27.0",
"@react-aria/visually-hidden": "^3.8.19",
"@react-types/shared": "^3.27.0"
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
},
"peerDependencies": {
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
"node_modules/react-aria-components": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "1.6.0",
"resolved": "https://registry.npmjs.org/react-aria-components/-/react-aria-components-1.6.0.tgz",
"integrity": "sha512-YfG9PUE7XrXtDDAqT4pLTGyYQaiHHTBFdAK/wNgGsypVnQSdzmyYlV3Ty8aHlZJI6hP9RWkbywvosXkU7KcPHg==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@internationalized/date": "^3.7.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@internationalized/string": "^3.2.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/autocomplete": "3.0.0-alpha.37",
"@react-aria/collections": "3.0.0-alpha.7",
"@react-aria/color": "^3.0.3",
"@react-aria/disclosure": "^3.0.1",
"@react-aria/dnd": "^3.8.1",
"@react-aria/focus": "^3.19.1",
"@react-aria/interactions": "^3.23.0",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-aria/live-announcer": "^3.4.1",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-aria/menu": "^3.17.0",
"@react-aria/toolbar": "3.0.0-beta.12",
"@react-aria/tree": "3.0.0-beta.3",
"@react-aria/utils": "^3.27.0",
"@react-aria/virtualizer": "^4.1.1",
"@react-stately/autocomplete": "3.0.0-alpha.0",
"@react-stately/color": "^3.8.2",
"@react-stately/disclosure": "^3.0.1",
"@react-stately/layout": "^4.1.1",
"@react-stately/menu": "^3.9.1",
"@react-stately/selection": "^3.19.0",
"@react-stately/table": "^3.13.1",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"@react-stately/utils": "^3.10.5",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/virtualizer": "^4.2.1",
"@react-types/color": "^3.0.2",
"@react-types/form": "^3.7.9",
"@react-types/grid": "^3.2.11",
"@react-types/shared": "^3.27.0",
"@react-types/table": "^3.10.4",
♻️(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
"@swc/helpers": "^0.5.0",
"client-only": "^0.0.1",
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"react-aria": "^3.37.0",
"react-stately": "^3.35.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
"use-sync-external-store": "^1.2.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1",
"react-dom": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
✨(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
"node_modules/react-dom": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "18.3.1",
"resolved": "https://registry.npmjs.org/react-dom/-/react-dom-18.3.1.tgz",
"integrity": "sha512-5m4nQKp+rZRb09LNH59GM4BxTh9251/ylbKIbpe7TpGxfJ+9kv6BLkLBXIjjspbgbnIBNqlI23tRnTWT0snUIw==",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
✨(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": {
"loose-envify": "^1.1.0",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"scheduler": "^0.23.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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"react": "^18.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
}
},
🌐(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
"node_modules/react-i18next": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "15.1.1",
"resolved": "https://registry.npmjs.org/react-i18next/-/react-i18next-15.1.1.tgz",
"integrity": "sha512-R/Vg9wIli2P3FfeI8o1eNJUJue5LWpFsQePCHdQDmX0Co3zkr6kdT8gAseb/yGeWbNz1Txc4bKDQuZYsC0kQfw==",
"license": "MIT",
🌐(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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"@babel/runtime": "^7.25.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
"html-parse-stringify": "^3.0.1"
},
"peerDependencies": {
"i18next": ">= 23.2.3",
"react": ">= 16.8.0"
},
"peerDependenciesMeta": {
"react-dom": {
"optional": true
},
"react-native": {
"optional": true
}
}
},
✨(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
"node_modules/react-refresh": {
"version": "0.14.2",
"resolved": "https://registry.npmjs.org/react-refresh/-/react-refresh-0.14.2.tgz",
"integrity": "sha512-jCvmsr+1IUSMUyzOkRcvnVbX3ZYC6g9TDrDbFuFmRDq7PD4yaGbLKNQL6k2jnArV8hjYxh7hVhAZB6s9HDGpZA==",
"dev": true,
"engines": {
♻️(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
"node": ">=0.10.0"
}
},
"node_modules/react-stately": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"version": "3.35.0",
"resolved": "https://registry.npmjs.org/react-stately/-/react-stately-3.35.0.tgz",
"integrity": "sha512-1BH21J/TOHpyZe7c+f1BU2bnRWaBDTjLH0WdBuzNfPOXu7RBG3ebPIRvqd7UkPaVfIcol2QJnxe8S0a314JWKA==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.0",
"dependencies": {
⬆️(frontend) bump react-aria-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-20 19:28:44 +01:00
"@react-stately/calendar": "^3.7.0",
"@react-stately/checkbox": "^3.6.11",
"@react-stately/collections": "^3.12.1",
"@react-stately/color": "^3.8.2",
"@react-stately/combobox": "^3.10.2",
"@react-stately/data": "^3.12.1",
"@react-stately/datepicker": "^3.12.0",
"@react-stately/disclosure": "^3.0.1",
"@react-stately/dnd": "^3.5.1",
"@react-stately/form": "^3.1.1",
"@react-stately/list": "^3.11.2",
"@react-stately/menu": "^3.9.1",
"@react-stately/numberfield": "^3.9.9",
"@react-stately/overlays": "^3.6.13",
"@react-stately/radio": "^3.10.10",
"@react-stately/searchfield": "^3.5.9",
"@react-stately/select": "^3.6.10",
"@react-stately/selection": "^3.19.0",
"@react-stately/slider": "^3.6.1",
"@react-stately/table": "^3.13.1",
"@react-stately/tabs": "^3.7.1",
"@react-stately/toggle": "^3.8.1",
"@react-stately/tooltip": "^3.5.1",
"@react-stately/tree": "^3.8.7",
"@react-types/shared": "^3.27.0"
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
},
"peerDependencies": {
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.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
}
},
🌐(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
"node_modules/readable-stream": {
"version": "2.3.8",
"resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.8.tgz",
"integrity": "sha512-8p0AUk4XODgIewSi0l8Epjs+EVnWiK7NoDIEGU0HhE7+ZyY8D1IMY7odu5lRrFXGg71L15KG8QrPmum45RTtdA==",
"dependencies": {
"core-util-is": "~1.0.0",
"inherits": "~2.0.3",
"isarray": "~1.0.0",
"process-nextick-args": "~2.0.0",
"safe-buffer": "~5.1.1",
"string_decoder": "~1.1.1",
"util-deprecate": "~1.0.1"
}
},
"node_modules/readable-stream/node_modules/isarray": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz",
"integrity": "sha512-VLghIWNM6ELQzo7zwmcg0NmTVyWKYjvIeM83yjp0wRDTmUnrM678fQbcKBo6n2CJEF0szoG//ytg+TKla89ALQ=="
},
♻️(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
"node_modules/readdirp": {
"version": "3.6.0",
"resolved": "https://registry.npmjs.org/readdirp/-/readdirp-3.6.0.tgz",
"integrity": "sha512-hOS089on8RduqdbhvQ5Z37A0ESjsqz6qnRcffsMU3495FuTdqSm+7bhJ29JvIOsBDEEnan5DPu9t3To9VRlMzA==",
"dev": true,
"dependencies": {
"picomatch": "^2.2.1"
},
"engines": {
"node": ">=8.10.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
"node_modules/regenerator-runtime": {
"version": "0.14.1",
"resolved": "https://registry.npmjs.org/regenerator-runtime/-/regenerator-runtime-0.14.1.tgz",
"integrity": "sha512-dYnhHh0nJoMfnkZs6GmmhFknAGRrLznOu5nc9ML+EJxGvrx6H7teuevqVqCuPcPK//3eDrrjQhehXVx9cnkGdw=="
},
♻️(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
"node_modules/regexp.prototype.flags": {
"version": "1.5.2",
"resolved": "https://registry.npmjs.org/regexp.prototype.flags/-/regexp.prototype.flags-1.5.2.tgz",
"integrity": "sha512-NcDiDkTLuPR+++OCKB0nWafEmhg/Da8aUPLPMQbK+bxKKCm1/S5he+AqYa4PlMCVBalb4/yxIRub6qkEx5yJbw==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.6",
"define-properties": "^1.2.1",
"es-errors": "^1.3.0",
"set-function-name": "^2.0.1"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/regexparam": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/regexparam/-/regexparam-3.0.0.tgz",
"integrity": "sha512-RSYAtP31mvYLkAHrOlh25pCNQ5hWnT106VukGaaFfuJrZFkGRX5GhUAdPqpSDXxOhA2c4akmRuplv1mRqnBn6Q==",
"engines": {
"node": ">=8"
✨(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) 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
"node_modules/remove-trailing-separator": {
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/remove-trailing-separator/-/remove-trailing-separator-1.1.0.tgz",
"integrity": "sha512-/hS+Y0u3aOfIETiaiirUFwDBDzmXPvO+jAfKTitUngIPzdKc6Z0LoFjM/CK5PL4C+eKwHohlHAb6H0VFfmmUsw=="
},
"node_modules/replace-ext": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/replace-ext/-/replace-ext-2.0.0.tgz",
"integrity": "sha512-UszKE5KVK6JvyD92nzMn9cDapSk6w/CaFZ96CnmDMUqH9oowfxF/ZjRITD25H4DnOQClLA4/j7jLGXXLVKxAug==",
"engines": {
"node": ">= 10"
}
},
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"node_modules/require-from-string": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/require-from-string/-/require-from-string-2.0.2.tgz",
"integrity": "sha512-Xf0nWe6RseziFMu+Ap9biiUbmplq6S9/p+7w7YXP/JBHhrUDDUhwa+vANyubuqfZWTveU//DYVGsDG7RKL/vEw==",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=0.10.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
"node_modules/resolve-from": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-4.0.0.tgz",
"integrity": "sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==",
"dev": true,
"engines": {
"node": ">=4"
}
},
🌐(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
"node_modules/resolve-options": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/resolve-options/-/resolve-options-2.0.0.tgz",
"integrity": "sha512-/FopbmmFOQCfsCx77BRFdKOniglTiHumLgwvd6IDPihy1GKkadZbgQJBcTb2lMzSR1pndzd96b1nZrreZ7+9/A==",
"dependencies": {
"value-or-function": "^4.0.0"
},
"engines": {
"node": ">= 10.13.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
"node_modules/reusify": {
"version": "1.0.4",
"resolved": "https://registry.npmjs.org/reusify/-/reusify-1.0.4.tgz",
"integrity": "sha512-U9nH88a3fc/ekCF1l0/UP1IosiuIjyTh7hBvXVMHYgVcfGvt897Xguj2UOLDeI5BG2m7/uwyaLVT6fbtCwTyzw==",
"engines": {
"iojs": ">=1.0.0",
"node": ">=0.10.0"
}
},
"node_modules/rimraf": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/rimraf/-/rimraf-3.0.2.tgz",
"integrity": "sha512-JZkJMZkAGFFPP2YqXZXPbMlMBgsxzE8ILs4lMIX/2o0L9UBw9O/Y3o6wFw/i9YLapcUJWwqbi3kdxIPdC62TIA==",
"deprecated": "Rimraf versions prior to v4 are no longer supported",
"dependencies": {
"glob": "^7.1.3"
},
"bin": {
"rimraf": "bin.js"
},
"funding": {
"url": "https://github.com/sponsors/isaacs"
}
},
"node_modules/rollup": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"version": "4.24.0",
"resolved": "https://registry.npmjs.org/rollup/-/rollup-4.24.0.tgz",
"integrity": "sha512-DOmrlGSXNk1DM0ljiQA+i+o0rSLhtii1je5wgk60j49d1jHT5YYttBv1iWOnYSTG+fZZESUOSNiAl89SIet+Cg==",
✨(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
"dev": true,
"dependencies": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"@types/estree": "1.0.6"
✨(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
},
"bin": {
"rollup": "dist/bin/rollup"
},
"engines": {
"node": ">=18.0.0",
"npm": ">=8.0.0"
},
"optionalDependencies": {
⬆️(dependencies) update js dependencies
2024-10-09 13:12:37 +00:00
"@rollup/rollup-android-arm-eabi": "4.24.0",
"@rollup/rollup-android-arm64": "4.24.0",
"@rollup/rollup-darwin-arm64": "4.24.0",
"@rollup/rollup-darwin-x64": "4.24.0",
"@rollup/rollup-linux-arm-gnueabihf": "4.24.0",
"@rollup/rollup-linux-arm-musleabihf": "4.24.0",
"@rollup/rollup-linux-arm64-gnu": "4.24.0",
"@rollup/rollup-linux-arm64-musl": "4.24.0",
"@rollup/rollup-linux-powerpc64le-gnu": "4.24.0",
"@rollup/rollup-linux-riscv64-gnu": "4.24.0",
"@rollup/rollup-linux-s390x-gnu": "4.24.0",
"@rollup/rollup-linux-x64-gnu": "4.24.0",
"@rollup/rollup-linux-x64-musl": "4.24.0",
"@rollup/rollup-win32-arm64-msvc": "4.24.0",
"@rollup/rollup-win32-ia32-msvc": "4.24.0",
"@rollup/rollup-win32-x64-msvc": "4.24.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
"fsevents": "~2.3.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
"node_modules/rsvp": {
"version": "4.8.5",
"resolved": "https://registry.npmjs.org/rsvp/-/rsvp-4.8.5.tgz",
"integrity": "sha512-nfMOlASu9OnRJo1mbEk2cz0D56a1MBNrJ7orjRZQG10XDyuvwksKbuXNp6qa+kbn839HwjwhBzhFmdsaEAfauA==",
"engines": {
"node": "6.* || >= 7.*"
}
},
✨(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
"node_modules/run-parallel": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/run-parallel/-/run-parallel-1.2.0.tgz",
"integrity": "sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==",
"dev": true,
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/feross"
},
{
"type": "patreon",
"url": "https://www.patreon.com/feross"
},
{
"type": "consulting",
"url": "https://feross.org/support"
}
],
"dependencies": {
"queue-microtask": "^1.2.2"
}
},
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"node_modules/rxjs": {
"version": "7.8.1",
"resolved": "https://registry.npmjs.org/rxjs/-/rxjs-7.8.1.tgz",
"integrity": "sha512-AA3TVj+0A2iuIoQkWEK/tqFjBq2j+6PO6Y0zJcvzLAFhEFIO3HL0vls9hWLncZbAAbK0mar7oZ4V079I/qPMxg==",
"dependencies": {
"tslib": "^2.1.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
"node_modules/safe-array-concat": {
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/safe-array-concat/-/safe-array-concat-1.1.2.tgz",
"integrity": "sha512-vj6RsCsWBCf19jIeHEfkRMw8DPiBb+DMXklQ/1SGDHOMlHdPUkZXFQ2YdplS23zESTijAcurb1aSgJA3AgMu1Q==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.7",
"get-intrinsic": "^1.2.4",
"has-symbols": "^1.0.3",
"isarray": "^2.0.5"
},
"engines": {
"node": ">=0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
🌐(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
"node_modules/safe-buffer": {
"version": "5.1.2",
"resolved": "https://registry.npmjs.org/safe-buffer/-/safe-buffer-5.1.2.tgz",
"integrity": "sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g=="
},
♻️(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
"node_modules/safe-regex-test": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/safe-regex-test/-/safe-regex-test-1.0.3.tgz",
"integrity": "sha512-CdASjNJPvRa7roO6Ra/gLYBTzYzzPyyBXxIMdGW3USQLyjWEls2RgW5UBTXaQVp+OrpeCK3bLem8smtmheoRuw==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.6",
"es-errors": "^1.3.0",
"is-regex": "^1.1.4"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
🌐(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
"node_modules/safer-buffer": {
"version": "2.1.2",
"resolved": "https://registry.npmjs.org/safer-buffer/-/safer-buffer-2.1.2.tgz",
"integrity": "sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg=="
},
✨(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
"node_modules/scheduler": {
"version": "0.23.2",
"resolved": "https://registry.npmjs.org/scheduler/-/scheduler-0.23.2.tgz",
"integrity": "sha512-UOShsPwz7NrMUqhR6t0hWjFduvOzbtv7toDH1/hIrfRNIDBnnBWd0CwJTGvTpngVlmwGCdP9/Zl/tVrDqcuYzQ==",
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
✨(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": {
"loose-envify": "^1.1.0"
}
},
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"node_modules/sdp": {
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/sdp/-/sdp-3.2.0.tgz",
♻️(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
"integrity": "sha512-d7wDPgDV3DDiqulJjKiV2865wKsJ34YI+NDREbm+FySq6WuKOikwyNQcm+doLAZ1O6ltdO0SeKle2xMpN3Brgw=="
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
},
"node_modules/sdp-transform": {
"version": "2.14.2",
"resolved": "https://registry.npmjs.org/sdp-transform/-/sdp-transform-2.14.2.tgz",
"integrity": "sha512-icY6jVao7MfKCieyo1AyxFYm1baiM+fA00qW/KrNNVlkxHAd34riEKuEkUe4bBb3gJwLJZM+xT60Yj1QL8rHiA==",
"bin": {
"sdp-verify": "checker.js"
}
},
✨(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
"node_modules/semver": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "7.6.3",
"resolved": "https://registry.npmjs.org/semver/-/semver-7.6.3.tgz",
"integrity": "sha512-oVekP1cKtI+CTDvHWYFUcMtsK/00wmAEfyqKfNdARm8u1wNVhSgaX7A8d4UuIlUI5e84iEwOhs7ZPYRmzU9U6A==",
✨(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
"dev": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "ISC",
✨(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
"bin": {
"semver": "bin/semver.js"
},
"engines": {
"node": ">=10"
}
},
♻️(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
"node_modules/set-function-length": {
"version": "1.2.2",
"resolved": "https://registry.npmjs.org/set-function-length/-/set-function-length-1.2.2.tgz",
"integrity": "sha512-pgRc4hJ4/sNjWCSS9AmnS40x3bNMDTknHgL5UaMBTMyJnU90EgWh1Rz+MC9eFu4BuN/UwZjKQuY/1v3rM7HMfg==",
"dev": true,
"dependencies": {
"define-data-property": "^1.1.4",
"es-errors": "^1.3.0",
"function-bind": "^1.1.2",
"get-intrinsic": "^1.2.4",
"gopd": "^1.0.1",
"has-property-descriptors": "^1.0.2"
},
"engines": {
"node": ">= 0.4"
}
},
"node_modules/set-function-name": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/set-function-name/-/set-function-name-2.0.2.tgz",
"integrity": "sha512-7PGFlmtwsEADb0WYyvCMa1t+yke6daIG4Wirafur5kcf+MhUnPms1UeR0CKQdTZD81yESwMHbtn+TR+dMviakQ==",
"dev": true,
"dependencies": {
"define-data-property": "^1.1.4",
"es-errors": "^1.3.0",
"functions-have-names": "^1.2.3",
"has-property-descriptors": "^1.0.2"
},
"engines": {
"node": ">= 0.4"
}
},
✨(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
"node_modules/shebang-command": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/shebang-command/-/shebang-command-2.0.0.tgz",
"integrity": "sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==",
"dev": true,
"dependencies": {
"shebang-regex": "^3.0.0"
},
"engines": {
"node": ">=8"
}
},
"node_modules/shebang-regex": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/shebang-regex/-/shebang-regex-3.0.0.tgz",
"integrity": "sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==",
"dev": true,
"engines": {
"node": ">=8"
}
},
♻️(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
"node_modules/side-channel": {
"version": "1.0.6",
"resolved": "https://registry.npmjs.org/side-channel/-/side-channel-1.0.6.tgz",
"integrity": "sha512-fDW/EZ6Q9RiO8eFG8Hj+7u/oW+XrPTIChwCOM2+th2A6OblDtYYIpve9m+KvI9Z4C9qSEXlaGR6bTEYHReuglA==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.7",
"es-errors": "^1.3.0",
"get-intrinsic": "^1.2.4",
"object-inspect": "^1.13.1"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/sisteransi": {
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/sisteransi/-/sisteransi-1.0.5.tgz",
"integrity": "sha512-bLGGlR1QxBcynn2d5YmDX4MGjlZvy2MRBDRNHLJ8VI6l6+9FUiyTFNJ0IveOSP0bcXgVDPRcfGqA0pjaqUpfVg==",
"dev": true
},
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"node_modules/slice-ansi": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/slice-ansi/-/slice-ansi-4.0.0.tgz",
"integrity": "sha512-qMCMfhY040cVHT43K9BFygqYbUPFZKHOg7K73mtTWJRb8pyP3fzf4Ixd5SzdEJQ6MRUg/WBnOLxghZtKKurENQ==",
"dev": true,
"license": "MIT",
"dependencies": {
"ansi-styles": "^4.0.0",
"astral-regex": "^2.0.0",
"is-fullwidth-code-point": "^3.0.0"
},
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/chalk/slice-ansi?sponsor=1"
}
},
🌐(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
"node_modules/sort-keys": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/sort-keys/-/sort-keys-5.1.0.tgz",
"integrity": "sha512-aSbHV0DaBcr7u0PVHXzM6NbZNAtrr9sF6+Qfs9UUVG7Ll3jQ6hHi8F/xqIIcn2rvIVbr0v/2zyjSdwSV47AgLQ==",
🌐(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
"dependencies": {
"is-plain-obj": "^4.0.0"
},
"engines": {
"node": ">=12"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
✨(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
"node_modules/source-map-js": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "1.2.1",
"resolved": "https://registry.npmjs.org/source-map-js/-/source-map-js-1.2.1.tgz",
"integrity": "sha512-UXWMKhLOwVKb728IUtQPXxfYU+usdybtUrK/8uGE8CQMvrhOpwvzDBwj0QhSL7MQc7vIsISBG8VQ8+IDQxpfQA==",
✨(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
"dev": true,
"engines": {
"node": ">=0.10.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
"node_modules/sprintf-js": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.1.3.tgz",
"integrity": "sha512-Oo+0REFV59/rz3gfJNKQiBlwfHaSESl1pcGyABQsnnIfWOFt6JNj5gCog2U6MLZ//IGYD+nA8nI+mTShREReaA=="
♻️(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
},
🌐(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
"node_modules/stream-composer": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/stream-composer/-/stream-composer-1.0.2.tgz",
"integrity": "sha512-bnBselmwfX5K10AH6L4c8+S5lgZMWI7ZYrz2rvYjCPB2DIMC4Ig8OpxGpNJSxRZ58oti7y1IcNvjBAz9vW5m4w==",
"dependencies": {
"streamx": "^2.13.2"
}
},
"node_modules/streamx": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "2.20.1",
"resolved": "https://registry.npmjs.org/streamx/-/streamx-2.20.1.tgz",
"integrity": "sha512-uTa0mU6WUC65iUvzKH4X9hEdvSW7rbPxPtwfWiLMSj3qTdQbAiUboZTxauKfpFuGIGa1C2BYijZ7wgdUXICJhA==",
🌐(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
"dependencies": {
"fast-fifo": "^1.3.2",
"queue-tick": "^1.0.1",
"text-decoder": "^1.1.0"
},
"optionalDependencies": {
"bare-events": "^2.2.0"
}
},
"node_modules/string_decoder": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-1.1.1.tgz",
"integrity": "sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==",
"dependencies": {
"safe-buffer": "~5.1.0"
}
},
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"node_modules/string-width": {
"version": "4.2.3",
"resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz",
"integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==",
"dev": true,
"license": "MIT",
"dependencies": {
"emoji-regex": "^8.0.0",
"is-fullwidth-code-point": "^3.0.0",
"strip-ansi": "^6.0.1"
},
"engines": {
"node": ">=8"
}
},
"node_modules/string-width/node_modules/emoji-regex": {
"version": "8.0.0",
"resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-8.0.0.tgz",
"integrity": "sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==",
"dev": true,
"license": "MIT"
},
♻️(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
"node_modules/string.prototype.includes": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/string.prototype.includes/-/string.prototype.includes-2.0.1.tgz",
"integrity": "sha512-o7+c9bW6zpAdJHTtujeePODAhkuicdAryFsfVKwA+wGw89wJ4GTY484WTucM9hLtDEOpOvI+aHnzqnC5lHp4Rg==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"call-bind": "^1.0.7",
"define-properties": "^1.2.1",
"es-abstract": "^1.23.3"
},
"engines": {
"node": ">= 0.4"
♻️(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
}
},
"node_modules/string.prototype.trim": {
"version": "1.2.9",
"resolved": "https://registry.npmjs.org/string.prototype.trim/-/string.prototype.trim-1.2.9.tgz",
"integrity": "sha512-klHuCNxiMZ8MlsOihJhJEBJAiMVqU3Z2nEXWfWnIqjN0gEFS9J9+IxKozWWtQGcgoa1WUZzLjKPTr4ZHNFTFxw==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.7",
"define-properties": "^1.2.1",
"es-abstract": "^1.23.0",
"es-object-atoms": "^1.0.0"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/string.prototype.trimend": {
"version": "1.0.8",
"resolved": "https://registry.npmjs.org/string.prototype.trimend/-/string.prototype.trimend-1.0.8.tgz",
"integrity": "sha512-p73uL5VCHCO2BZZ6krwwQE3kCzM7NKmis8S//xEC6fQonchbum4eP6kR4DLEjQFO3Wnj3Fuo8NM0kOSjVdHjZQ==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.7",
"define-properties": "^1.2.1",
"es-object-atoms": "^1.0.0"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/string.prototype.trimstart": {
"version": "1.0.8",
"resolved": "https://registry.npmjs.org/string.prototype.trimstart/-/string.prototype.trimstart-1.0.8.tgz",
"integrity": "sha512-UXSH262CSZY1tfu3G3Secr6uGLCFVPMhIqHjlgCUtCCcgihYc/xKs9djMTMUOb2j1mVSeU8EU6NWc/iQKU6Gfg==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.7",
"define-properties": "^1.2.1",
"es-object-atoms": "^1.0.0"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
✨(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
"node_modules/strip-ansi": {
"version": "6.0.1",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
"integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
"dev": true,
"dependencies": {
"ansi-regex": "^5.0.1"
},
"engines": {
"node": ">=8"
}
},
"node_modules/strip-json-comments": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/strip-json-comments/-/strip-json-comments-3.1.1.tgz",
"integrity": "sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig==",
"dev": true,
"engines": {
"node": ">=8"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
🌐(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
"node_modules/symlink-or-copy": {
"version": "1.3.1",
"resolved": "https://registry.npmjs.org/symlink-or-copy/-/symlink-or-copy-1.3.1.tgz",
"integrity": "sha512-0K91MEXFpBUaywiwSSkmKjnGcasG/rVBXFLJz5DrgGabpYD6N+3yZrfD6uUIfpuTu65DZLHi7N8CizHc07BPZA=="
},
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"node_modules/table": {
"version": "6.9.0",
"resolved": "https://registry.npmjs.org/table/-/table-6.9.0.tgz",
"integrity": "sha512-9kY+CygyYM6j02t5YFHbNz2FN5QmYGv9zAjVp4lCDjlCw7amdckXlEt/bjMhUIfj4ThGRE4gCUH5+yGnNuPo5A==",
"dev": true,
"license": "BSD-3-Clause",
"dependencies": {
"ajv": "^8.0.1",
"lodash.truncate": "^4.4.2",
"slice-ansi": "^4.0.0",
"string-width": "^4.2.3",
"strip-ansi": "^6.0.1"
},
"engines": {
"node": ">=10.0.0"
}
},
"node_modules/table/node_modules/ajv": {
"version": "8.17.1",
"resolved": "https://registry.npmjs.org/ajv/-/ajv-8.17.1.tgz",
"integrity": "sha512-B/gBuNg5SiMTrPkC+A2+cW0RszwxYmn6VYxB/inlBStS5nx6xHIt/ehKRhIMhqusl7a8LjQoZnjCs5vhwxOQ1g==",
"dev": true,
"license": "MIT",
"dependencies": {
"fast-deep-equal": "^3.1.3",
"fast-uri": "^3.0.1",
"json-schema-traverse": "^1.0.0",
"require-from-string": "^2.0.2"
},
"funding": {
"type": "github",
"url": "https://github.com/sponsors/epoberezkin"
}
},
"node_modules/table/node_modules/json-schema-traverse": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-1.0.0.tgz",
"integrity": "sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug==",
"dev": true,
"license": "MIT"
},
🌐(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
"node_modules/teex": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/teex/-/teex-1.0.1.tgz",
"integrity": "sha512-eYE6iEI62Ni1H8oIa7KlDU6uQBtqr4Eajni3wX7rpfXD8ysFx8z0+dri+KWEPWpBsxXfxu58x/0jvTVT1ekOSg==",
"dependencies": {
"streamx": "^2.12.5"
}
},
"node_modules/text-decoder": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/text-decoder/-/text-decoder-1.2.0.tgz",
"integrity": "sha512-n1yg1mOj9DNpk3NeZOx7T6jchTbyJS3i3cucbNN6FcdPriMZx7NsgrGpWWdWZZGxD7ES1XB+3uoqHMgOKaN+fg==",
🌐(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
"dependencies": {
"b4a": "^1.6.4"
}
},
✨(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
"node_modules/text-table": {
"version": "0.2.0",
"resolved": "https://registry.npmjs.org/text-table/-/text-table-0.2.0.tgz",
"integrity": "sha512-N+8UisAXDGk8PFXP4HAzVR9nbfmVJ3zYLAWiTIoqC5v5isinhr+r5uaO8+7r3BMfuNIufIsA7RdpVgacC2cSpw==",
"dev": true
},
🌐(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
"node_modules/through2": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/through2/-/through2-2.0.5.tgz",
"integrity": "sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==",
"dependencies": {
"readable-stream": "~2.3.6",
"xtend": "~4.0.1"
}
},
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"node_modules/tinyglobby": {
"version": "0.2.10",
"resolved": "https://registry.npmjs.org/tinyglobby/-/tinyglobby-0.2.10.tgz",
"integrity": "sha512-Zc+8eJlFMvgatPZTl6A9L/yht8QqdmUNtURHaKZLmKBE12hNPSrqNkUp2cs3M/UKmNVVAMFQYSjYIVHDjW5zew==",
"dev": true,
"license": "MIT",
"dependencies": {
"fdir": "^6.4.2",
"picomatch": "^4.0.2"
},
"engines": {
"node": ">=12.0.0"
}
},
"node_modules/tinyglobby/node_modules/fdir": {
"version": "6.4.3",
"resolved": "https://registry.npmjs.org/fdir/-/fdir-6.4.3.tgz",
"integrity": "sha512-PMXmW2y1hDDfTSRc9gaXIuCCRpuoz3Kaz8cUelp3smouvfT632ozg2vrT6lJsHKKOF59YLbOGfAWGUcKEfRMQw==",
"dev": true,
"license": "MIT",
"peerDependencies": {
"picomatch": "^3 || ^4"
},
"peerDependenciesMeta": {
"picomatch": {
"optional": true
}
}
},
"node_modules/tinyglobby/node_modules/picomatch": {
"version": "4.0.2",
"resolved": "https://registry.npmjs.org/picomatch/-/picomatch-4.0.2.tgz",
"integrity": "sha512-M7BAV6Rlcy5u+m6oPhAPFgJTzAioX/6B0DxyvDlo9l8+T3nLKbrczg2WLUyzd45L8RqfUMyGPzekbMvX2Ldkwg==",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=12"
},
"funding": {
"url": "https://github.com/sponsors/jonschlinkert"
}
},
✨(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
"node_modules/to-regex-range": {
"version": "5.0.1",
"resolved": "https://registry.npmjs.org/to-regex-range/-/to-regex-range-5.0.1.tgz",
"integrity": "sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==",
"dev": true,
"dependencies": {
"is-number": "^7.0.0"
},
"engines": {
"node": ">=8.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
"node_modules/to-through": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/to-through/-/to-through-3.0.0.tgz",
"integrity": "sha512-y8MN937s/HVhEoBU1SxfHC+wxCHkV1a9gW8eAdTadYh/bGyesZIVcbjI+mSpFbSVwQici/XjBjuUyri1dnXwBw==",
"dependencies": {
"streamx": "^2.12.5"
},
"engines": {
"node": ">=10.13.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
"node_modules/ts-api-utils": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/ts-api-utils/-/ts-api-utils-2.0.0.tgz",
"integrity": "sha512-xCt/TOAc+EOHS1XPnijD3/yzpH6qg2xppZO1YDqGoVsNXfQfzHpOdNuXwrwOU8u4ITXJyDCTyt8w5g1sZv9ynQ==",
✨(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
"dev": true,
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
✨(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
"engines": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"node": ">=18.12"
✨(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
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"typescript": ">=4.8.4"
✨(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) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"node_modules/ts-debounce": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/ts-debounce/-/ts-debounce-4.0.0.tgz",
♻️(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
"integrity": "sha512-+1iDGY6NmOGidq7i7xZGA4cm8DAa6fqdYcvO5Z6yBevH++Bdo9Qt/mN0TzHUgcCcKv1gmh9+W5dHqz8pMWbCbg=="
},
"node_modules/ts-evaluator": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/ts-evaluator/-/ts-evaluator-1.2.0.tgz",
"integrity": "sha512-ncSGek1p92bj2ifB7s9UBgryHCkU9vwC5d+Lplt12gT9DH+e41X8dMoHRQjIMeAvyG7j9dEnuHmwgOtuRIQL+Q==",
"dev": true,
⬆️(dependencies) update js dependencies
2024-09-24 08:35:39 +00:00
"license": "MIT",
♻️(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
"dependencies": {
"ansi-colors": "^4.1.3",
"crosspath": "^2.0.0",
"object-path": "^0.11.8"
},
"engines": {
"node": ">=14.19.0"
},
"funding": {
"type": "github",
"url": "https://github.com/wessberg/ts-evaluator?sponsor=1"
},
"peerDependencies": {
"jsdom": ">=14.x || >=15.x || >=16.x || >=17.x || >=18.x || >=19.x || >=20.x || >=21.x || >=22.x",
"typescript": ">=3.2.x || >= 4.x || >= 5.x"
},
"peerDependenciesMeta": {
"jsdom": {
"optional": true
}
}
},
"node_modules/ts-morph": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "24.0.0",
"resolved": "https://registry.npmjs.org/ts-morph/-/ts-morph-24.0.0.tgz",
"integrity": "sha512-2OAOg/Ob5yx9Et7ZX4CvTCc0UFoZHwLEJ+dpDPSUi5TgwwlTlX47w+iFRrEwzUZwYACjq83cgjS/Da50Ga37uw==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"@ts-morph/common": "~0.25.0",
"code-block-writer": "^13.0.3"
♻️(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
}
},
"node_modules/ts-pattern": {
"version": "5.0.8",
"resolved": "https://registry.npmjs.org/ts-pattern/-/ts-pattern-5.0.8.tgz",
"integrity": "sha512-aafbuAQOTEeWmA7wtcL94w6I89EgLD7F+IlWkr596wYxeb0oveWDO5dQpv85YP0CGbxXT/qXBIeV6IYLcoZ2uA==",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"dev": true
},
♻️(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
"node_modules/tsconfck": {
"version": "3.0.2",
"resolved": "https://registry.npmjs.org/tsconfck/-/tsconfck-3.0.2.tgz",
"integrity": "sha512-6lWtFjwuhS3XI4HsX4Zg0izOI3FU/AI9EGVlPEUMDIhvLPMD4wkiof0WCoDgW7qY+Dy198g4d9miAqUHWHFH6Q==",
"dev": true,
"bin": {
"tsconfck": "bin/tsconfck.js"
},
"engines": {
"node": "^18 || >=20"
},
"peerDependencies": {
"typescript": "^5.0.0"
},
"peerDependenciesMeta": {
"typescript": {
"optional": true
}
}
},
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"node_modules/tslib": {
⬆️(frontend) bump LiveKit-related dependencies No major / breaking change in these few releases. Quickly tested all features, everything seems alright
2025-01-16 18:42:31 +01:00
"version": "2.8.1",
"resolved": "https://registry.npmjs.org/tslib/-/tslib-2.8.1.tgz",
"integrity": "sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w==",
"license": "0BSD"
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
},
✨(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
"node_modules/type-check": {
"version": "0.4.0",
"resolved": "https://registry.npmjs.org/type-check/-/type-check-0.4.0.tgz",
"integrity": "sha512-XleUoc9uwGXqjWwXaUTZAmzMcFZ5858QA2vvx1Ur5xIcixXIP+8LnFDgRplU30us6teqdlskFfu+ae4K79Ooew==",
"dev": true,
"dependencies": {
"prelude-ls": "^1.2.1"
},
"engines": {
"node": ">= 0.8.0"
}
},
"node_modules/type-fest": {
"version": "0.20.2",
"resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.20.2.tgz",
"integrity": "sha512-Ne+eE4r0/iWnpAxD852z3A+N0Bt5RN//NjJwRd2VFHEmrywxf5vsZlh4R6lixl6B+wz/8d+maTSAkN1FIkI3LQ==",
"dev": true,
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
},
♻️(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
"node_modules/typed-array-buffer": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/typed-array-buffer/-/typed-array-buffer-1.0.2.tgz",
"integrity": "sha512-gEymJYKZtKXzzBzM4jqa9w6Q1Jjm7x2d+sh19AdsD4wqnMPDYyvwpsIc2Q/835kHuo3BEQ7CjelGhfTsoBb2MQ==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.7",
"es-errors": "^1.3.0",
"is-typed-array": "^1.1.13"
},
"engines": {
"node": ">= 0.4"
}
},
"node_modules/typed-array-byte-length": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/typed-array-byte-length/-/typed-array-byte-length-1.0.1.tgz",
"integrity": "sha512-3iMJ9q0ao7WE9tWcaYKIptkNBuOIcZCCT0d4MRvuuH88fEoEH62IuQe0OtraD3ebQEoTRk8XCBoknUNc1Y67pw==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.7",
"for-each": "^0.3.3",
"gopd": "^1.0.1",
"has-proto": "^1.0.3",
"is-typed-array": "^1.1.13"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/typed-array-byte-offset": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/typed-array-byte-offset/-/typed-array-byte-offset-1.0.2.tgz",
"integrity": "sha512-Ous0vodHa56FviZucS2E63zkgtgrACj7omjwd/8lTEMEPFFyjfixMZ1ZXenpgCFBBt4EC1J2XsyVS2gkG0eTFA==",
"dev": true,
"dependencies": {
"available-typed-arrays": "^1.0.7",
"call-bind": "^1.0.7",
"for-each": "^0.3.3",
"gopd": "^1.0.1",
"has-proto": "^1.0.3",
"is-typed-array": "^1.1.13"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/typed-array-length": {
"version": "1.0.6",
"resolved": "https://registry.npmjs.org/typed-array-length/-/typed-array-length-1.0.6.tgz",
"integrity": "sha512-/OxDN6OtAk5KBpGb28T+HZc2M+ADtvRxXrKKbUwtsLgdoxgX13hyy7ek6bFRl5+aBs2yZzB0c4CnQfAtVypW/g==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.7",
"for-each": "^0.3.3",
"gopd": "^1.0.1",
"has-proto": "^1.0.3",
"is-typed-array": "^1.1.13",
"possible-typed-array-names": "^1.0.0"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"node_modules/typed-emitter": {
"version": "2.1.0",
"resolved": "https://registry.npmjs.org/typed-emitter/-/typed-emitter-2.1.0.tgz",
"integrity": "sha512-g/KzbYKbH5C2vPkaXGu8DJlHrGKHLsM25Zg9WuC9pMGfuvT+X25tZQWo5fK1BjBm8+UrVE9LDCvaY0CQk+fXDA==",
"optionalDependencies": {
"rxjs": "*"
}
},
✨(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
"node_modules/typescript": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "5.7.3",
"resolved": "https://registry.npmjs.org/typescript/-/typescript-5.7.3.tgz",
"integrity": "sha512-84MVSjMEHP+FQRPy3pX9sTVV/INIex71s9TL2Gm5FG/WG1SqXeKyZ0k7/blY/4FdOzI12CBy1vGc4og/eus0fw==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "Apache-2.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
"bin": {
"tsc": "bin/tsc",
"tsserver": "bin/tsserver"
},
"engines": {
"node": ">=14.17"
}
},
♻️(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
"node_modules/ufo": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "1.5.4",
"resolved": "https://registry.npmjs.org/ufo/-/ufo-1.5.4.tgz",
"integrity": "sha512-UsUk3byDzKd04EyoZ7U4DOlxQaD14JUKQl6/P7wiX4FNvUfm3XL246n9W5AmqwW5RSFJ27NAuM0iLscAOYUiGQ==",
♻️(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": true
},
"node_modules/unbox-primitive": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/unbox-primitive/-/unbox-primitive-1.0.2.tgz",
"integrity": "sha512-61pPlCD9h51VoreyJ0BReideM3MDKMKnh6+V9L08331ipq6Q8OFXZYiqP6n/tbHx4s5I9uRhcye6BrbkizkBDw==",
"dev": true,
"dependencies": {
"call-bind": "^1.0.2",
"has-bigints": "^1.0.2",
"has-symbols": "^1.0.3",
"which-boxed-primitive": "^1.0.2"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
🌐(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
"node_modules/underscore.string": {
"version": "3.3.6",
"resolved": "https://registry.npmjs.org/underscore.string/-/underscore.string-3.3.6.tgz",
"integrity": "sha512-VoC83HWXmCrF6rgkyxS9GHv8W9Q5nhMKho+OadDJGzL2oDYbYEppBaCMH6pFlwLeqj2QS+hhkw2kpXkSdD1JxQ==",
"dependencies": {
"sprintf-js": "^1.1.1",
"util-deprecate": "^1.0.2"
},
"engines": {
"node": "*"
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/undici": {
"version": "6.19.8",
"resolved": "https://registry.npmjs.org/undici/-/undici-6.19.8.tgz",
"integrity": "sha512-U8uCCl2x9TK3WANvmBavymRzxbfFYG+tAu+fgx3zxQy3qdagQqBLwJVrdyO1TBfUXvfKveMKJZhpvUYoOjM+4g==",
"engines": {
"node": ">=18.17"
}
🌐(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
},
🔧(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
"node_modules/undici-types": {
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"version": "6.20.0",
"resolved": "https://registry.npmjs.org/undici-types/-/undici-types-6.20.0.tgz",
"integrity": "sha512-Ny6QZ2Nju20vw1SRHe3d9jVu6gJ+4e3+MMpqu7pqE5HT6WsTSlce++GQmK5UXS8mzV8DSYHrQH+Xrf2jVcuKNg==",
"dev": true,
"license": "MIT"
🔧(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
},
♻️(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
"node_modules/universalify": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/universalify/-/universalify-2.0.1.tgz",
"integrity": "sha512-gptHNQghINnc/vTGIk0SOFGFNXw7JVrlRUtConJRlvaw6DuX0wO5Jeko9sWrMBhh+PsYAZ7oXAiOnf/UKogyiw==",
"engines": {
"node": ">= 10.0.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
"node_modules/update-browserslist-db": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/update-browserslist-db/-/update-browserslist-db-1.1.2.tgz",
"integrity": "sha512-PPypAm5qvlD7XMZC3BujecnaOxwhrtoFR+Dqkk5Aa/6DssiH0ibKoketaj9w8LP7Bont1rYeoV5plxD7RTEPRg==",
✨(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
"dev": true,
"funding": [
{
"type": "opencollective",
"url": "https://opencollective.com/browserslist"
},
{
"type": "tidelift",
"url": "https://tidelift.com/funding/github/npm/browserslist"
},
{
"type": "github",
"url": "https://github.com/sponsors/ai"
}
],
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"license": "MIT",
✨(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) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"escalade": "^3.2.0",
"picocolors": "^1.1.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
},
"bin": {
"update-browserslist-db": "cli.js"
},
"peerDependencies": {
"browserslist": ">= 4.21.0"
}
},
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node_modules/update-browserslist-db/node_modules/escalade": {
"version": "3.2.0",
"resolved": "https://registry.npmjs.org/escalade/-/escalade-3.2.0.tgz",
"integrity": "sha512-WUj2qlxaQtO4g6Pq5c29GTcWGDyd8itL8zTlipgECz3JesAiiOKotd8JU6otB3PACgG6xkJUyVhboMS+bje/jA==",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=6"
}
},
✨(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
"node_modules/uri-js": {
"version": "4.4.1",
"resolved": "https://registry.npmjs.org/uri-js/-/uri-js-4.4.1.tgz",
"integrity": "sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==",
"dev": true,
"dependencies": {
"punycode": "^2.1.0"
}
},
🚸(frontend) draft sound design on notifications More a brainsto idea inspired from Gmeet than a polished feature. Try adding sound notification to add a new dimension on the user experience.
2024-09-11 12:02:01 +02:00
"node_modules/use-sound": {
"version": "4.0.3",
"resolved": "https://registry.npmjs.org/use-sound/-/use-sound-4.0.3.tgz",
"integrity": "sha512-L205pEUFIrLsGYsCUKHQVCt0ajs//YQOFbEQeNwaWaqQj3y3st4SuR+rvpMHLmv8hgTcfUFlvMQawZNI3OE18w==",
"dependencies": {
"howler": "^2.1.3"
},
"peerDependencies": {
"react": ">=16.8"
}
},
♻️(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
"node_modules/use-sync-external-store": {
"version": "1.2.2",
"resolved": "https://registry.npmjs.org/use-sync-external-store/-/use-sync-external-store-1.2.2.tgz",
"integrity": "sha512-PElTlVMwpblvbNqQ82d2n6RjStvdSoNe9FG28kNfz3WiXilJm4DdNkEzRhCZuIDwY8U08WVihhGR5iRqAwfDiw==",
"peerDependencies": {
"react": "^16.8.0 || ^17.0.0 || ^18.0.0"
}
},
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"node_modules/usehooks-ts": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/usehooks-ts/-/usehooks-ts-3.1.0.tgz",
"integrity": "sha512-bBIa7yUyPhE1BCc0GmR96VU/15l/9gP1Ch5mYdLcFBaFGQsdmXkvjV0TtOqW1yUd6VjIwDunm+flSciCQXujiw==",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"dependencies": {
"lodash.debounce": "^4.0.8"
},
"engines": {
"node": ">=16.15.0"
},
"peerDependencies": {
"react": "^16.8.0 || ^17 || ^18"
}
},
♻️(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
"node_modules/util-deprecate": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
🌐(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
"integrity": "sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw=="
},
♻️(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
"node_modules/valtio": {
⬆️(dependencies) update js dependencies
2025-01-27 14:32:11 +00:00
"version": "2.1.3",
"resolved": "https://registry.npmjs.org/valtio/-/valtio-2.1.3.tgz",
"integrity": "sha512-q+dVczY5zf7kO39JPVq2qR0VXMeEpF1t+P1njHU7hAhwgtyVa/p38YmgyHZq2IQYwnkNrkvh412k4sfDmcIJ2g==",
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
♻️(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
"dependencies": {
⬆️(dependencies) update js dependencies
2025-01-27 14:32:11 +00:00
"proxy-compare": "^3.0.1"
♻️(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
},
"engines": {
"node": ">=12.20.0"
},
"peerDependencies": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"@types/react": ">=18.0.0",
"react": ">=18.0.0"
♻️(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
},
"peerDependenciesMeta": {
"@types/react": {
"optional": true
},
"react": {
"optional": true
}
}
},
🌐(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
"node_modules/value-or-function": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/value-or-function/-/value-or-function-4.0.0.tgz",
"integrity": "sha512-aeVK81SIuT6aMJfNo9Vte8Dw0/FZINGBV8BfCraGtqVxIeLAEhJyoWs8SmvRVmXfGss2PmmOwZCuBPbZR+IYWg==",
"engines": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node": ">= 10.13.0"
}
},
"node_modules/vinyl": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/vinyl/-/vinyl-3.0.0.tgz",
"integrity": "sha512-rC2VRfAVVCGEgjnxHUnpIVh3AGuk62rP3tqVrn+yab0YH7UULisC085+NYH+mnqf3Wx4SpSi1RQMwudL89N03g==",
"dependencies": {
"clone": "^2.1.2",
"clone-stats": "^1.0.0",
"remove-trailing-separator": "^1.1.0",
"replace-ext": "^2.0.0",
"teex": "^1.0.1"
},
"engines": {
"node": ">=10.13.0"
}
},
"node_modules/vinyl-contents": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/vinyl-contents/-/vinyl-contents-2.0.0.tgz",
"integrity": "sha512-cHq6NnGyi2pZ7xwdHSW1v4Jfnho4TEGtxZHw01cmnc8+i7jgR6bRnED/LbrKan/Q7CvVLbnvA5OepnhbpjBZ5Q==",
"dependencies": {
"bl": "^5.0.0",
"vinyl": "^3.0.0"
},
"engines": {
"node": ">=10.13.0"
}
},
"node_modules/vinyl-fs": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/vinyl-fs/-/vinyl-fs-4.0.0.tgz",
"integrity": "sha512-7GbgBnYfaquMk3Qu9g22x000vbYkOex32930rBnc3qByw6HfMEAoELjCjoJv4HuEQxHAurT+nvMHm6MnJllFLw==",
"dependencies": {
"fs-mkdirp-stream": "^2.0.1",
"glob-stream": "^8.0.0",
"graceful-fs": "^4.2.11",
"iconv-lite": "^0.6.3",
"is-valid-glob": "^1.0.0",
"lead": "^4.0.0",
"normalize-path": "3.0.0",
"resolve-options": "^2.0.0",
"stream-composer": "^1.0.2",
"streamx": "^2.14.0",
"to-through": "^3.0.0",
"value-or-function": "^4.0.0",
"vinyl": "^3.0.0",
"vinyl-sourcemap": "^2.0.0"
},
"engines": {
"node": ">=10.13.0"
}
},
"node_modules/vinyl-sourcemap": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/vinyl-sourcemap/-/vinyl-sourcemap-2.0.0.tgz",
"integrity": "sha512-BAEvWxbBUXvlNoFQVFVHpybBbjW1r03WhohJzJDSfgrrK5xVYIDTan6xN14DlyImShgDRv2gl9qhM6irVMsV0Q==",
"dependencies": {
"convert-source-map": "^2.0.0",
"graceful-fs": "^4.2.10",
"now-and-later": "^3.0.0",
"streamx": "^2.12.5",
"vinyl": "^3.0.0",
"vinyl-contents": "^2.0.0"
},
"engines": {
"node": ">=10.13.0"
}
},
"node_modules/vite": {
⬆️(dependencies) update js dependencies
2025-01-27 14:32:11 +00:00
"version": "6.0.11",
"resolved": "https://registry.npmjs.org/vite/-/vite-6.0.11.tgz",
"integrity": "sha512-4VL9mQPKoHy4+FE0NnRE/kbY51TOfaknxAjt3fJbGJxhIpBZiqVzlZDEesWWsuREXHwNdAoOFZ9MkPEVXczHwg==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dev": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"esbuild": "^0.24.2",
"postcss": "^8.4.49",
"rollup": "^4.23.0"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
},
"bin": {
"vite": "bin/vite.js"
},
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": "^18.0.0 || ^20.0.0 || >=22.0.0"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
},
"funding": {
"url": "https://github.com/vitejs/vite?sponsor=1"
},
"optionalDependencies": {
"fsevents": "~2.3.3"
},
"peerDependencies": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@types/node": "^18.0.0 || ^20.0.0 || >=22.0.0",
"jiti": ">=1.21.0",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"less": "*",
"lightningcss": "^1.21.0",
"sass": "*",
"sass-embedded": "*",
"stylus": "*",
"sugarss": "*",
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"terser": "^5.16.0",
"tsx": "^4.8.1",
"yaml": "^2.4.2"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
},
"peerDependenciesMeta": {
"@types/node": {
"optional": true
},
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"jiti": {
"optional": true
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"less": {
"optional": true
},
"lightningcss": {
"optional": true
},
"sass": {
"optional": true
},
"sass-embedded": {
"optional": true
},
"stylus": {
"optional": true
},
"sugarss": {
"optional": true
},
"terser": {
"optional": true
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
},
"tsx": {
"optional": true
},
"yaml": {
"optional": true
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
}
},
"node_modules/vite-tsconfig-paths": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "5.1.4",
"resolved": "https://registry.npmjs.org/vite-tsconfig-paths/-/vite-tsconfig-paths-5.1.4.tgz",
"integrity": "sha512-cYj0LRuLV2c2sMqhqhGpaO3LretdtMn/BVX4cPLanIZuwwrkVl+lK84E/miEXkCHWXuq65rhNN4rXsBcOB3S4w==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dev": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dependencies": {
"debug": "^4.1.1",
"globrex": "^0.1.2",
"tsconfck": "^3.0.3"
},
"peerDependencies": {
"vite": "*"
},
"peerDependenciesMeta": {
"vite": {
"optional": true
}
}
},
"node_modules/vite-tsconfig-paths/node_modules/tsconfck": {
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"version": "3.1.4",
"resolved": "https://registry.npmjs.org/tsconfck/-/tsconfck-3.1.4.tgz",
"integrity": "sha512-kdqWFGVJqe+KGYvlSO9NIaWn9jT1Ny4oKVzAJsKii5eoE9snzTJzL4+MMVOMn+fikWGFmKEylcXL710V/kIPJQ==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"dev": true,
⬆️(dependencies) update js dependencies
2024-11-25 10:36:44 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"bin": {
"tsconfck": "bin/tsconfck.js"
},
"engines": {
"node": "^18 || >=20"
},
"peerDependencies": {
"typescript": "^5.0.0"
},
"peerDependenciesMeta": {
"typescript": {
"optional": true
}
}
},
"node_modules/vite/node_modules/@esbuild/aix-ppc64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/aix-ppc64/-/aix-ppc64-0.24.2.tgz",
"integrity": "sha512-thpVCb/rhxE/BnMLQ7GReQLLN8q9qbHmI55F4489/ByVg2aQaQ6kbcLb6FHkocZzQhxc4gx0sCk0tJkKBFzDhA==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"ppc64"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"aix"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/vite/node_modules/@esbuild/android-arm": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/android-arm/-/android-arm-0.24.2.tgz",
"integrity": "sha512-tmwl4hJkCfNHwFB3nBa8z1Uy3ypZpxqxfTQOcHX+xRByyYgunVbZ9MzUUfb0RxaHIMnbHagwAxuTL+tnNM+1/Q==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"arm"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"android"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/vite/node_modules/@esbuild/android-arm64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/android-arm64/-/android-arm64-0.24.2.tgz",
"integrity": "sha512-cNLgeqCqV8WxfcTIOeL4OAtSmL8JjcN6m09XIgro1Wi7cF4t/THaWEa7eL5CMoMBdjoHOTh/vwTO/o2TRXIyzg==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"arm64"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"android"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/vite/node_modules/@esbuild/android-x64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/android-x64/-/android-x64-0.24.2.tgz",
"integrity": "sha512-B6Q0YQDqMx9D7rvIcsXfmJfvUYLoP722bgfBlO5cGvNVb5V/+Y7nhBE3mHV9OpxBf4eAS2S68KZztiPaWq4XYw==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"x64"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"android"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/vite/node_modules/@esbuild/darwin-arm64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/darwin-arm64/-/darwin-arm64-0.24.2.tgz",
"integrity": "sha512-kj3AnYWc+CekmZnS5IPu9D+HWtUI49hbnyqk0FLEJDbzCIQt7hg7ucF1SQAilhtYpIujfaHr6O0UHlzzSPdOeA==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"arm64"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"darwin"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/vite/node_modules/@esbuild/darwin-x64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/darwin-x64/-/darwin-x64-0.24.2.tgz",
"integrity": "sha512-WeSrmwwHaPkNR5H3yYfowhZcbriGqooyu3zI/3GGpF8AyUdsrrP0X6KumITGA9WOyiJavnGZUwPGvxvwfWPHIA==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"x64"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"darwin"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/vite/node_modules/@esbuild/freebsd-arm64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/freebsd-arm64/-/freebsd-arm64-0.24.2.tgz",
"integrity": "sha512-UN8HXjtJ0k/Mj6a9+5u6+2eZ2ERD7Edt1Q9IZiB5UZAIdPnVKDoG7mdTVGhHJIeEml60JteamR3qhsr1r8gXvg==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"arm64"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"freebsd"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/vite/node_modules/@esbuild/freebsd-x64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/freebsd-x64/-/freebsd-x64-0.24.2.tgz",
"integrity": "sha512-TvW7wE/89PYW+IevEJXZ5sF6gJRDY/14hyIGFXdIucxCsbRmLUcjseQu1SyTko+2idmCw94TgyaEZi9HUSOe3Q==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"x64"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"freebsd"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/vite/node_modules/@esbuild/linux-arm": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-arm/-/linux-arm-0.24.2.tgz",
"integrity": "sha512-n0WRM/gWIdU29J57hJyUdIsk0WarGd6To0s+Y+LwvlC55wt+GT/OgkwoXCXvIue1i1sSNWblHEig00GBWiJgfA==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"arm"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/vite/node_modules/@esbuild/linux-arm64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-arm64/-/linux-arm64-0.24.2.tgz",
"integrity": "sha512-7HnAD6074BW43YvvUmE/35Id9/NB7BeX5EoNkK9obndmZBUk8xmJJeU7DwmUeN7tkysslb2eSl6CTrYz6oEMQg==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"arm64"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/vite/node_modules/@esbuild/linux-ia32": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-ia32/-/linux-ia32-0.24.2.tgz",
"integrity": "sha512-sfv0tGPQhcZOgTKO3oBE9xpHuUqguHvSo4jl+wjnKwFpapx+vUDcawbwPNuBIAYdRAvIDBfZVvXprIj3HA+Ugw==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"ia32"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/vite/node_modules/@esbuild/linux-loong64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-loong64/-/linux-loong64-0.24.2.tgz",
"integrity": "sha512-CN9AZr8kEndGooS35ntToZLTQLHEjtVB5n7dl8ZcTZMonJ7CCfStrYhrzF97eAecqVbVJ7APOEe18RPI4KLhwQ==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"loong64"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/vite/node_modules/@esbuild/linux-mips64el": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-mips64el/-/linux-mips64el-0.24.2.tgz",
"integrity": "sha512-iMkk7qr/wl3exJATwkISxI7kTcmHKE+BlymIAbHO8xanq/TjHaaVThFF6ipWzPHryoFsesNQJPE/3wFJw4+huw==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"mips64el"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/vite/node_modules/@esbuild/linux-ppc64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-ppc64/-/linux-ppc64-0.24.2.tgz",
"integrity": "sha512-shsVrgCZ57Vr2L8mm39kO5PPIb+843FStGt7sGGoqiiWYconSxwTiuswC1VJZLCjNiMLAMh34jg4VSEQb+iEbw==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"ppc64"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/vite/node_modules/@esbuild/linux-riscv64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-riscv64/-/linux-riscv64-0.24.2.tgz",
"integrity": "sha512-4eSFWnU9Hhd68fW16GD0TINewo1L6dRrB+oLNNbYyMUAeOD2yCK5KXGK1GH4qD/kT+bTEXjsyTCiJGHPZ3eM9Q==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"riscv64"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/vite/node_modules/@esbuild/linux-s390x": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-s390x/-/linux-s390x-0.24.2.tgz",
"integrity": "sha512-S0Bh0A53b0YHL2XEXC20bHLuGMOhFDO6GN4b3YjRLK//Ep3ql3erpNcPlEFed93hsQAjAQDNsvcK+hV90FubSw==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"s390x"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
}
},
"node_modules/vite/node_modules/@esbuild/linux-x64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/linux-x64/-/linux-x64-0.24.2.tgz",
"integrity": "sha512-8Qi4nQcCTbLnK9WoMjdC9NiTG6/E38RNICU6sUNqK0QFxCYgoARqVqxdFmWkdonVsvGqWhmm7MO0jyTqLqwj0Q==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"x64"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"linux"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
🌐(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/vite/node_modules/@esbuild/netbsd-x64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/netbsd-x64/-/netbsd-x64-0.24.2.tgz",
"integrity": "sha512-VefFaQUc4FMmJuAxmIHgUmfNiLXY438XrL4GDNV1Y1H/RW3qow68xTwjZKfj/+Plp9NANmzbH5R40Meudu8mmw==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"x64"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"netbsd"
],
🌐(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
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/vite/node_modules/@esbuild/openbsd-x64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/openbsd-x64/-/openbsd-x64-0.24.2.tgz",
"integrity": "sha512-+iDS6zpNM6EnJyWv0bMGLWSWeXGN/HTaF/LXHXHwejGsVi+ooqDfMCCTerNFxEkM3wYVcExkeGXNqshc9iMaOA==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"x64"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"openbsd"
],
🌐(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
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
🌐(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/vite/node_modules/@esbuild/sunos-x64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/sunos-x64/-/sunos-x64-0.24.2.tgz",
"integrity": "sha512-hTdsW27jcktEvpwNHJU4ZwWFGkz2zRJUz8pvddmXPtXDzVKTTINmlmga3ZzwcuMpUvLw7JkLy9QLKyGpD2Yxig==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"x64"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"sunos"
],
🌐(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
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
🌐(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/vite/node_modules/@esbuild/win32-arm64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/win32-arm64/-/win32-arm64-0.24.2.tgz",
"integrity": "sha512-LihEQ2BBKVFLOC9ZItT9iFprsE9tqjDjnbulhHoFxYQtQfai7qfluVODIYxt1PgdoyQkz23+01rzwNwYfutxUQ==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"arm64"
],
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"win32"
],
🌐(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
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
🌐(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
}
♻️(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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/vite/node_modules/@esbuild/win32-ia32": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/win32-ia32/-/win32-ia32-0.24.2.tgz",
"integrity": "sha512-q+iGUwfs8tncmFC9pcnD5IvRHAzmbwQ3GPS5/ceCyHdjXubwQWI12MKWSNSMYLJMq23/IUCvJMS76PDqXe1fxA==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"ia32"
],
✨(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
"dev": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"win32"
],
✨(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
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
✨(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) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/vite/node_modules/@esbuild/win32-x64": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/@esbuild/win32-x64/-/win32-x64-0.24.2.tgz",
"integrity": "sha512-7VTgWzgMGvup6aSqDPLiW5zHaxYJGTO4OokMjIlrCtf+VpEL+cXKtCvg723iguPYI5oaUNdS+/V7OU2gvXVWEg==",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"cpu": [
"x64"
],
♻️(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": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optional": true,
"os": [
"win32"
],
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
♻️(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
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/vite/node_modules/esbuild": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"version": "0.24.2",
"resolved": "https://registry.npmjs.org/esbuild/-/esbuild-0.24.2.tgz",
"integrity": "sha512-+9egpBW8I3CD5XPe0n6BfT5fxLzxrlDzqydF3aviG+9ni1lDC/OvMHcxqEFV0+LANZG5R1bFMWfUrjVsdwxJvA==",
♻️(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": true,
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"hasInstallScript": true,
⬆️(dependencies) update vite to v5.4.6 [SECURITY]
2024-10-09 12:59:22 +00:00
"license": "MIT",
♻️(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
"bin": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"esbuild": "bin/esbuild"
♻️(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
},
"engines": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"node": ">=18"
♻️(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
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"optionalDependencies": {
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"@esbuild/aix-ppc64": "0.24.2",
"@esbuild/android-arm": "0.24.2",
"@esbuild/android-arm64": "0.24.2",
"@esbuild/android-x64": "0.24.2",
"@esbuild/darwin-arm64": "0.24.2",
"@esbuild/darwin-x64": "0.24.2",
"@esbuild/freebsd-arm64": "0.24.2",
"@esbuild/freebsd-x64": "0.24.2",
"@esbuild/linux-arm": "0.24.2",
"@esbuild/linux-arm64": "0.24.2",
"@esbuild/linux-ia32": "0.24.2",
"@esbuild/linux-loong64": "0.24.2",
"@esbuild/linux-mips64el": "0.24.2",
"@esbuild/linux-ppc64": "0.24.2",
"@esbuild/linux-riscv64": "0.24.2",
"@esbuild/linux-s390x": "0.24.2",
"@esbuild/linux-x64": "0.24.2",
"@esbuild/netbsd-arm64": "0.24.2",
"@esbuild/netbsd-x64": "0.24.2",
"@esbuild/openbsd-arm64": "0.24.2",
"@esbuild/openbsd-x64": "0.24.2",
"@esbuild/sunos-x64": "0.24.2",
"@esbuild/win32-arm64": "0.24.2",
"@esbuild/win32-ia32": "0.24.2",
"@esbuild/win32-x64": "0.24.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
}
},
🌐(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
"node_modules/void-elements": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/void-elements/-/void-elements-3.1.0.tgz",
"integrity": "sha512-Dhxzh5HZuiHQhbvTW9AMetFfBHDMYpo23Uo9btPXgdYP+3T5S+p+jgNy7spra+veYhBP2dCSgxR/i2Y02h5/6w==",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/walk-sync": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/walk-sync/-/walk-sync-2.2.0.tgz",
"integrity": "sha512-IC8sL7aB4/ZgFcGI2T1LczZeFWZ06b3zoHH7jBPyHxOtIIz1jppWHjjEXkOFvFojBVAK9pV7g47xOZ4LW3QLfg==",
"dependencies": {
"@types/minimatch": "^3.0.3",
"ensure-posix-path": "^1.1.0",
"matcher-collection": "^2.0.0",
"minimatch": "^3.0.4"
},
"engines": {
"node": "8.* || >= 10.*"
}
},
"node_modules/walk-sync/node_modules/brace-expansion": {
"version": "1.1.11",
"resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz",
"integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==",
"dependencies": {
"balanced-match": "^1.0.0",
"concat-map": "0.0.1"
}
},
"node_modules/walk-sync/node_modules/minimatch": {
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz",
"integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==",
"dependencies": {
"brace-expansion": "^1.1.7"
},
"engines": {
"node": "*"
}
},
➕(frontend) add posthog dependency Posthog is a product analysis tool. Installed the js SDK to track product usage.
2024-09-17 10:45:58 +02:00
"node_modules/web-vitals": {
"version": "4.2.3",
"resolved": "https://registry.npmjs.org/web-vitals/-/web-vitals-4.2.3.tgz",
"integrity": "sha512-/CFAm1mNxSmOj6i0Co+iGFJ58OS4NRGVP+AWS/l509uIK5a1bSoIVaHz/ZumpHTfHSZBpgrJ+wjfpAOrTHok5Q=="
},
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"node_modules/webrtc-adapter": {
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"version": "9.0.1",
"resolved": "https://registry.npmjs.org/webrtc-adapter/-/webrtc-adapter-9.0.1.tgz",
"integrity": "sha512-1AQO+d4ElfVSXyzNVTOewgGT/tAomwwztX/6e3totvyyzXPvXIIuUUjAmyZGbKBKbZOXauuJooZm3g6IuFuiNQ==",
➕(frontend) add LiveKit dependencies LiveKit offers various React components as building blocks to build any video or audio conference tools. It also requires to install a LiveKit client, as the users will connect to the LiveKit server once the backend have issued an Access Token, directly from their web browsers.
2024-06-25 12:17:53 +02:00
"dependencies": {
"sdp": "^3.2.0"
},
"engines": {
"node": ">=6.0.0",
"npm": ">=3.10.0"
}
},
⬆️(dependencies) update js dependencies
2024-09-15 14:48:08 +00:00
"node_modules/whatwg-encoding": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/whatwg-encoding/-/whatwg-encoding-3.1.1.tgz",
"integrity": "sha512-6qN4hJdMwfYBtE3YBTTHhoeuUrDBPZmbQaxWAqSALV/MeEnR5z1xd8UKud2RAkFoPkmB+hli1TZSnyi84xz1vQ==",
"dependencies": {
"iconv-lite": "0.6.3"
},
"engines": {
"node": ">=18"
}
},
"node_modules/whatwg-mimetype": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/whatwg-mimetype/-/whatwg-mimetype-4.0.0.tgz",
"integrity": "sha512-QaKxh0eNIi2mE9p2vEdzfagOKHCcj1pJ56EEHGQOVxp8r9/iszLUUV7v89x9O1p/T+NlTM5W7jW6+cz4Fq1YVg==",
"engines": {
"node": ">=18"
}
},
✨(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
"node_modules/which": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/which/-/which-2.0.2.tgz",
"integrity": "sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==",
"dev": true,
"dependencies": {
"isexe": "^2.0.0"
},
"bin": {
"node-which": "bin/node-which"
},
"engines": {
"node": ">= 8"
}
},
♻️(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
"node_modules/which-boxed-primitive": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/which-boxed-primitive/-/which-boxed-primitive-1.0.2.tgz",
"integrity": "sha512-bwZdv0AKLpplFY2KZRX6TvyuN7ojjr7lwkg6ml0roIy9YeuSr7JS372qlNW18UQYzgYK9ziGcerWqZOmEn9VNg==",
"dev": true,
"dependencies": {
"is-bigint": "^1.0.1",
"is-boolean-object": "^1.1.0",
"is-number-object": "^1.0.4",
"is-string": "^1.0.5",
"is-symbol": "^1.0.3"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
"node_modules/which-typed-array": {
"version": "1.1.15",
"resolved": "https://registry.npmjs.org/which-typed-array/-/which-typed-array-1.1.15.tgz",
"integrity": "sha512-oV0jmFtUky6CXfkqehVvBP/LSWJ2sy4vWMioiENyJLePrBO/yKyV9OyJySfAKosh+RYkIl5zJCNZ8/4JncrpdA==",
"dev": true,
"dependencies": {
"available-typed-arrays": "^1.0.7",
"call-bind": "^1.0.7",
"for-each": "^0.3.3",
"gopd": "^1.0.1",
"has-tostringtag": "^1.0.2"
},
"engines": {
"node": ">= 0.4"
},
"funding": {
"url": "https://github.com/sponsors/ljharb"
}
},
✨(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
"node_modules/word-wrap": {
"version": "1.2.5",
"resolved": "https://registry.npmjs.org/word-wrap/-/word-wrap-1.2.5.tgz",
"integrity": "sha512-BN22B5eaMMI9UMtjrGd5g5eCYPpCPDUy0FJXbYsaT5zYxjFOckS53SQDE3pWkVoWpHXVb3BrYcEN4Twa55B5cA==",
"dev": true,
"engines": {
"node": ">=0.10.0"
}
},
⬆️(dependencies) update js dependencies
2025-01-20 21:47:59 +00:00
"node_modules/wordwrapjs": {
"version": "5.1.0",
"resolved": "https://registry.npmjs.org/wordwrapjs/-/wordwrapjs-5.1.0.tgz",
"integrity": "sha512-JNjcULU2e4KJwUNv6CHgI46UvDGitb6dGryHajXTDiLgg1/RiGoPSDw4kZfYnwGtEXf2ZMeIewDQgFGzkCB2Sg==",
"dev": true,
"license": "MIT",
"engines": {
"node": ">=12.17"
}
},
♻️(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
"node_modules/wouter": {
⬆️(dependencies) update js dependencies
2025-01-27 14:32:11 +00:00
"version": "3.4.0",
"resolved": "https://registry.npmjs.org/wouter/-/wouter-3.4.0.tgz",
"integrity": "sha512-Qx4L+EnYk7AF+pNU9TM+lQtkceL5Qm+oDZU9720DUx+/7K6v7fnlHnRLI78KjEbCqdGFeroW5P0M1t8WYSloQA==",
"license": "Unlicense",
♻️(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
"dependencies": {
"mitt": "^3.0.1",
"regexparam": "^3.0.0",
"use-sync-external-store": "^1.0.0"
},
"peerDependencies": {
"react": ">=16.8.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
"node_modules/wrappy": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.2.tgz",
🌐(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
"integrity": "sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ=="
},
"node_modules/xtend": {
"version": "4.0.2",
"resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.2.tgz",
"integrity": "sha512-LKYU1iAXJXUgAXn9URjiu+MWhyUXHsvfp7mcuYm9dSUKK0/CjtrUwFAxD82/mCWbtLsGjFIad0wIsod4zrTAEQ==",
"engines": {
"node": ">=0.4"
}
✨(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
},
"node_modules/yallist": {
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/yallist/-/yallist-3.1.1.tgz",
"integrity": "sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g==",
⬆️(frontend) bump vite to v6.0.7 Updates build configuration to support new major version. This might introduce some breaking changes. I've read their migration guide, everything seems okay.
2025-01-16 18:12:07 +01:00
"dev": true,
"license": "ISC"
✨(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
},
"node_modules/yocto-queue": {
"version": "0.1.0",
"resolved": "https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz",
"integrity": "sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==",
"dev": true,
"engines": {
"node": ">=10"
},
"funding": {
"url": "https://github.com/sponsors/sindresorhus"
}
}
}
}
Reference in New Issue Copy Permalink