@cleanweb/react 1.1.1-beta.13 → 1.1.1-beta.14

package/build/base/methods.d.ts

@@ -1,8 +1,12 @@
 import type { TCleanState, TStateData } from './state';
-export declare class ComponentMethods<TProps extends object, TState extends TStateData> {
+export declare class ComponentMethods<TProps extends object = {}, TState extends TStateData | null = null> {
     props: TProps;
-    state: TCleanState<TState>;
+    state: TState extends TStateData ? TCleanState<TState> : null;
 }
-type UseMethods = <Class extends typeof ComponentMethods<object, object>>(Methods: Class & Constructor<InstanceType<Class>>, props: InstanceType<Class>['props'], state: InstanceType<Class>['state']) => InstanceType<Class>;
-export declare const useMethods: UseMethods;
-export {};
+type UseMethods = {
+    <Class extends typeof ComponentMethods<object, TStateData>>(Methods: Class & Constructor<InstanceType<Class>>, props: InstanceType<Class>['props'], state: InstanceType<Class>['state']): InstanceType<Class>;
+    <Class extends typeof ComponentMethods<object, null>>(Methods: Class & Constructor<InstanceType<Class>>, props: InstanceType<Class>['props'], state?: null): InstanceType<Class>;
+    <Class extends typeof ComponentMethods<HardEmptyObject, null>>(Methods: Class & Constructor<InstanceType<Class>>): InstanceType<Class>;
+};
+declare const useMethods: UseMethods;
+export { useMethods };

package/build/base/methods.js

@@ -60,16 +60,23 @@ var ComponentMethods = /** @class */ (function () {
 }());
 exports.ComponentMethods = ComponentMethods;
 ;
-var useMethods = function (Methods, props, state) {
-    // @todo Switch to useRef. Vite HMR seems to sometimes reinitialize useMemo calls after a hot update,
-    // causing the instance to be unexpectedly recreated in the middle of the components lifecycle.
+var useMethods = function () {
+    var args = [];
+    for (var _i = 0; _i < arguments.length; _i++) {
+        args[_i] = arguments[_i];
+    }
+    var Methods = args[0], _a = args[1], props = _a === void 0 ? {} : _a, state = args[2];
+    // Vite HMR seems to sometimes reinitialize useMemo calls after a hot update,
+    // causing the instance to be unexpectedly recreated in the middle of the component's lifecycle.
     // But useRef and useState values appear to always be preserved whenever this happens.
     // So those two are the only cross-render-persistence methods we can consider safe.
+    // @todo Provide a way for users to reflect updated methods code on the existing instance after HMR.
     var methods = (0, react_1.useRef)((0, react_1.useMemo)(function () {
         return new Methods();
     }, [])).current;
     methods.props = props;
-    methods.state = state;
+    if (state)
+        methods.state = state;
     return methods;
 };
 exports.useMethods = useMethods;
@@ -91,7 +98,8 @@ testing: {
                     return [4 /*yield*/, import('./state.js')];
                 case 1:
                     useCleanState = (_a.sent()).useCleanState;
-                    self = (0, exports.useMethods)(MyMethods, {}, useCleanState({}));
+                    self = useMethods(MyMethods, {});
+                    self.state;
                     return [2 /*return*/];
             }
         });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cleanweb/react",
-  "version": "1.1.1-beta.13",
+  "version": "1.1.1-beta.14",
   "description": "A suite of helpers for writing cleaner React function components.",
   "engines": {
     "node": ">=18"