@stacksjs/types 0.74.70 → 0.75.1

package/dist/analytics.d.ts

@@ -8,6 +8,8 @@
 export declare interface AnalyticsOptions {
   driver: 'google-analytics' | 'fathom' | 'plausible' | 'self-hosted' | 'analyticshq'
   capturePageviews?: boolean
+  enabled?: boolean
+  environments?: readonly string[]
   drivers: {
     analyticshq?: {
       siteId: string

package/dist/request.d.ts

@@ -11,27 +11,35 @@ import type { UploadedFile } from '@stacksjs/storage';
  * depends on this package again. A types package sits at the bottom of a
  * stack or it drags whatever it imports down there with it.
  *
- * Nothing is lost in practice. The old type was intersected with
- * `Record<string, any>` already, because the model proxy attaches trait
- * methods ahead of time and an application's own User columns are its own -
- * so every property access resolved through the index signature regardless.
+ * The index signature is `unknown`, not `any`. It was `any`, on the reasoning
+ * that the old type was intersected with `Record<string, any>` anyway, so
+ * "every property access resolved through the index signature regardless".
+ * That was the problem, not the excuse. Every field and every method was
+ * accepted unchecked, so apps wrote `(user as any).name` and never learned
+ * whether `name` existed, and the framework's own payment actions called
+ * `user.asStripeUser()`, `user.paymentIntent()` and five other methods no
+ * user has ever had - each one a `TypeError: ... is not a function` at
+ * runtime that the compiler waved through. With `unknown`, reading a field this interface does
+ * not declare still compiles, but using it means saying what it is.
  *
- * It is an interface so an application can have the precision back where it
- * wants it:
+ * An application rarely has to: `storage/framework/types/authenticated-user.d.ts`
+ * augments this interface with the columns of the app's own User model (and
+ * its billable methods, when it declares the trait), derived from the model
+ * so there is nothing to keep in step. It is an interface so anything else
+ * can be declared the same way:
  *
  * ```ts
  * declare module '@stacksjs/types' {
  *   interface AuthenticatedUser {
- *     email: string
  *     team_id: number
  *   }
  * }
  * ```
  */
 export declare interface AuthenticatedUser {
-  id: number
+  id: number | string
   email: string
-  [key: string]: any
+  [key: string]: unknown
 }
 declare interface RequestData {
   [key: string]: any

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@stacksjs/types",
   "type": "module",
-  "version": "0.74.70",
+  "version": "0.75.1",
   "description": "The Stacks framework types.",
   "author": "Chris Breuer",
   "contributors": [
@@ -58,8 +58,8 @@
   "dependencies": {
     "@stacksjs/bunpress": "^0.2.8",
     "@stacksjs/clapp": "^0.2.12",
-    "@stacksjs/events": "0.74.70",
-    "@stacksjs/strings": "0.74.70",
+    "@stacksjs/events": "0.75.1",
+    "@stacksjs/strings": "0.75.1",
     "@stacksjs/stx": "^0.2.307",
     "@stacksjs/ts-validation": "^0.5.6",
     "bun-query-builder": "^0.2.70"
@@ -73,7 +73,7 @@
     }
   },
   "devDependencies": {
-    "@stacksjs/validation": "0.74.70",
+    "@stacksjs/validation": "0.75.1",
     "better-dx": "^0.2.24",
     "meilisearch": "^0.59.0"
   },