flingit 0.0.18 → 0.0.19

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "flingit",
3
- "version": "0.0.18",
3
+ "version": "0.0.19",
4
4
  "description": "Personal Software Platform - Build and deploy personal tools through conversation",
5
5
  "type": "module",
6
6
  "engines": {
@@ -67,7 +67,8 @@
67
67
  "dotenv": "^17.2.3",
68
68
  "esbuild": "^0.27.2",
69
69
  "hono": "^4.11.7",
70
- "tsx": "^4.19.0"
70
+ "tsx": "^4.19.0",
71
+ "zod": "^3.25.76"
71
72
  },
72
73
  "devDependencies": {
73
74
  "@eslint/js": "^9.39.2",
@@ -1 +1 @@
1
- 48c43a6cab25d1a064e710509399ca76
1
+ 0c819de03c00959a7d8ccbeeb548a9f4
@@ -249,6 +249,13 @@ Slugs must be:
249
249
  - All other paths serve static assets from `dist/client/`
250
250
  - If no asset matches, `index.html` is served (SPA fallback)
251
251
 
252
+ ## Security
253
+
254
+ If the user does not want their app to be published because of security issues, or asks about that, offer implementing proper backend-supported security. In particular, suggest these two auth methods first:
255
+
256
+ - Login with Google, with a filter on which emails/domains are allowed
257
+ - Simple password-based auth, where the backend has a list of allowed passwords (hashed)
258
+
252
259
  ## Collaborating with Others
253
260
 
254
261
  If the user asks how to collaborate with another user on their Fling project, the best approach is: