nucleus-core-ts 0.9.927 → 0.9.929

package/dist/.build-ok

@@ -1 +1 @@
-0.9.927
+0.9.929

package/dist/dist/index.d.ts

@@ -25,6 +25,7 @@ export function usePubSub(config: any): {
     getEventsByTopic: (topic: any) => never[];
 };
 export var serverFetch: ServerFetch;
+export function requiredBodyCeiling(input: any): number | null;
 declare function parseCron2(expression: any): {
     ok: boolean;
     error: string;

package/dist/index.d.ts

@@ -2,6 +2,16 @@ import 'reflect-metadata';
 export * from './src/Client';
 export type { SystemAddressEntity, SystemClaimEntity, SystemFileEntity, SystemMonitoringMetricEntity, SystemPaymentCustomerEntity, SystemPaymentInvoiceEntity, SystemPaymentMethodEntity, SystemPaymentPriceEntity, SystemPaymentProductEntity, SystemPaymentSubscriptionEntity, SystemPaymentTransactionEntity, SystemPaymentWebhookLogEntity, SystemPhoneEntity, SystemProfileEntity, SystemRoleClaimEntity, SystemRoleEntity, SystemUserCohortEntity, SystemUserEntity, SystemUserRoleEntity, } from './src/Client/ApiCaller/types';
 export { NucleusElysiaPlugin } from './src/ElysiaPlugin';
+/**
+ * The request-body ceiling an install's own upload settings imply.
+ *
+ * Exported because only the HOST constructs the Elysia instance, and Bun's
+ * body limit is a constructor argument: `new Elysia({ serve: { maxRequestBodySize } })`.
+ * Without it Bun's 128 MiB default applies below every configured number, and
+ * a large upload dies on the wire with nothing to show. The plugin says so at
+ * boot when it is missing; this is what makes it easy to get right.
+ */
+export { requiredBodyCeiling } from './src/ElysiaPlugin/routes/shared/bodyCeiling';
 export type { NucleusContext, NucleusRuntime } from './src/ElysiaPlugin/runtime';
 export type { AuthorizationCheckResult, AuthorizationConfig, Claim, Role, RoleClaim, UserRole, } from './src/Services/Authorization/types';
 export type { AzureEmailServiceConfig } from './src/Services/Email/AzureEmailService';