brian/activist
1
0
Fork 0
Code Activity Actions
activist/package.json

59 lines
1.6 KiB
JSON
Raw Permalink Normal View History

initial commit
2024-11-16 11:40:53 -05:00
{
"name": "designer",
"version": "0.0.0",
"private": true,
"type": "module",
"scripts": {
Replace server.js with json-server. Replace uuid with id most places.
2024-12-08 14:40:46 -05:00
"server": "npx json-server --port 8000 db.json",
initial commit
2024-11-16 11:40:53 -05:00
"dev": "vite",
"build": "run-p type-check \"build-only {@}\" --",
"preview": "vite preview",
"test:unit": "vitest",
"build-only": "vite build",
"type-check": "vue-tsc --build --force",
"lint": "eslint . --fix",
"format": "prettier --write src/"
},
"dependencies": {
Upgrade dependencies. Use user_id in places we were using username. Still debating this. Start getting this working with API backend, until there were calls to /api/sticker which don't exist in the API yet. Then I rediscovered the local json-server. So now there are 2 api backends. We'll incrementally migrate from the first version to the second. SCSS and tailwind weren't working for nav-items.css. The browser just saw the raw version. So for now, just inlined that. Probably these nav items will become components (if they are shared).
2025-10-22 09:19:37 -04:00
"@pinia/colada": "^0.17.6",
Add forms.
2024-11-16 23:02:23 -05:00
"@primevue/forms": "^4.2.2",
Upgrade dependencies. Use user_id in places we were using username. Still debating this. Start getting this working with API backend, until there were calls to /api/sticker which don't exist in the API yet. Then I rediscovered the local json-server. So now there are 2 api backends. We'll incrementally migrate from the first version to the second. SCSS and tailwind weren't working for nav-items.css. The browser just saw the raw version. So for now, just inlined that. Probably these nav items will become components (if they are shared).
2025-10-22 09:19:37 -04:00
"@primevue/themes": "^4.4.1",
"@tailwindcss/postcss": "^4.1.15",
"pinia": "^3.0.3",
Use PrimeBlocks layout and move navigation into it.
2024-11-16 14:29:03 -05:00
"primeicons": "^7.0.0",
Upgrade dependencies. Use user_id in places we were using username. Still debating this. Start getting this working with API backend, until there were calls to /api/sticker which don't exist in the API yet. Then I rediscovered the local json-server. So now there are 2 api backends. We'll incrementally migrate from the first version to the second. SCSS and tailwind weren't working for nav-items.css. The browser just saw the raw version. So for now, just inlined that. Probably these nav items will become components (if they are shared).
2025-10-22 09:19:37 -04:00
"primevue": "^4.4.1",
"tailwindcss-primeui": "^0.6.1",
Live QR Codes
2024-12-23 16:14:22 -05:00
"uqr": "^0.1.2",
Upgrade dependencies. Use user_id in places we were using username. Still debating this. Start getting this working with API backend, until there were calls to /api/sticker which don't exist in the API yet. Then I rediscovered the local json-server. So now there are 2 api backends. We'll incrementally migrate from the first version to the second. SCSS and tailwind weren't working for nav-items.css. The browser just saw the raw version. So for now, just inlined that. Probably these nav items will become components (if they are shared).
2025-10-22 09:19:37 -04:00
"vue": "^3.5.22",
initial commit
2024-11-16 11:40:53 -05:00
"vue-router": "^4.4.5"
},
"devDependencies": {
Upgrade dependencies. Use user_id in places we were using username. Still debating this. Start getting this working with API backend, until there were calls to /api/sticker which don't exist in the API yet. Then I rediscovered the local json-server. So now there are 2 api backends. We'll incrementally migrate from the first version to the second. SCSS and tailwind weren't working for nav-items.css. The browser just saw the raw version. So for now, just inlined that. Probably these nav items will become components (if they are shared).
2025-10-22 09:19:37 -04:00
"@tailwindcss/vite": "^4.1.15",
initial commit
2024-11-16 11:40:53 -05:00
"@tsconfig/node22": "^22.0.0",
Upgrade dependencies. Use user_id in places we were using username. Still debating this. Start getting this working with API backend, until there were calls to /api/sticker which don't exist in the API yet. Then I rediscovered the local json-server. So now there are 2 api backends. We'll incrementally migrate from the first version to the second. SCSS and tailwind weren't working for nav-items.css. The browser just saw the raw version. So for now, just inlined that. Probably these nav items will become components (if they are shared).
2025-10-22 09:19:37 -04:00
"@types/jsdom": "^27.0.0",
"@types/node": "^24.9.0",
"@vitejs/plugin-vue": "^6.0.1",
"@vitest/eslint-plugin": "1.3.23",
initial commit
2024-11-16 11:40:53 -05:00
"@vue/eslint-config-prettier": "^10.1.0",
"@vue/eslint-config-typescript": "^14.1.3",
Upgrade dependencies. Use user_id in places we were using username. Still debating this. Start getting this working with API backend, until there were calls to /api/sticker which don't exist in the API yet. Then I rediscovered the local json-server. So now there are 2 api backends. We'll incrementally migrate from the first version to the second. SCSS and tailwind weren't working for nav-items.css. The browser just saw the raw version. So for now, just inlined that. Probably these nav items will become components (if they are shared).
2025-10-22 09:19:37 -04:00
"@vue/language-server": "^3.1.1",
initial commit
2024-11-16 11:40:53 -05:00
"@vue/test-utils": "^2.4.6",
Upgrade dependencies. Use user_id in places we were using username. Still debating this. Start getting this working with API backend, until there were calls to /api/sticker which don't exist in the API yet. Then I rediscovered the local json-server. So now there are 2 api backends. We'll incrementally migrate from the first version to the second. SCSS and tailwind weren't working for nav-items.css. The browser just saw the raw version. So for now, just inlined that. Probably these nav items will become components (if they are shared).
2025-10-22 09:19:37 -04:00
"@vue/tsconfig": "^0.8.1",
Use PrimeBlocks layout and move navigation into it.
2024-11-16 14:29:03 -05:00
"autoprefixer": "^10.4.20",
initial commit
2024-11-16 11:40:53 -05:00
"eslint": "^9.14.0",
Upgrade dependencies. Use user_id in places we were using username. Still debating this. Start getting this working with API backend, until there were calls to /api/sticker which don't exist in the API yet. Then I rediscovered the local json-server. So now there are 2 api backends. We'll incrementally migrate from the first version to the second. SCSS and tailwind weren't working for nav-items.css. The browser just saw the raw version. So for now, just inlined that. Probably these nav items will become components (if they are shared).
2025-10-22 09:19:37 -04:00
"eslint-plugin-vue": "^10.5.1",
"jsdom": "^27.0.1",
Replace server.js with json-server. Replace uuid with id most places.
2024-12-08 14:40:46 -05:00
"json-server": "^1.0.0-beta.3",
Upgrade dependencies. Use user_id in places we were using username. Still debating this. Start getting this working with API backend, until there were calls to /api/sticker which don't exist in the API yet. Then I rediscovered the local json-server. So now there are 2 api backends. We'll incrementally migrate from the first version to the second. SCSS and tailwind weren't working for nav-items.css. The browser just saw the raw version. So for now, just inlined that. Probably these nav items will become components (if they are shared).
2025-10-22 09:19:37 -04:00
"npm-run-all2": "^8.0.4",
Use PrimeBlocks layout and move navigation into it.
2024-11-16 14:29:03 -05:00
"postcss": "^8.4.49",
initial commit
2024-11-16 11:40:53 -05:00
"prettier": "^3.3.3",
Use PrimeBlocks layout and move navigation into it.
2024-11-16 14:29:03 -05:00
"sass-embedded": "^1.81.0",
Upgrade dependencies. Use user_id in places we were using username. Still debating this. Start getting this working with API backend, until there were calls to /api/sticker which don't exist in the API yet. Then I rediscovered the local json-server. So now there are 2 api backends. We'll incrementally migrate from the first version to the second. SCSS and tailwind weren't working for nav-items.css. The browser just saw the raw version. So for now, just inlined that. Probably these nav items will become components (if they are shared).
2025-10-22 09:19:37 -04:00
"tailwindcss": "^4.1.15",
"typescript": "~5.9.3",
"vite": "^7.1.11",
"vite-plugin-vue-devtools": "^8.0.3",
"vitest": "^3.2.4",
"vue-tsc": "^3.1.1"
initial commit
2024-11-16 11:40:53 -05:00
}
}
Copy permalink