Fix/prevent render after unmount

[ZvozdaB]

Summary

Resolves #33

• Add _destroyed flag set in $onDestroy to guard against late lifecycle calls
• Guard $doCheck and $onChanges with early return when _destroyed is true
• Prevents React 19 "Cannot update an unmounted root" error when AngularJS fires $onChanges after $onDestroy in the same digest cycle
• Improve TypeScript declarations: replace incorrect React.Element with ComponentType<TProps>, add generic bindings constraint
• Bump version 18.0.0 → 18.0.1

Problem

AngularJS does not guarantee that $onChanges won't fire after $onDestroy when both a binding change and component destruction occur in the same digest cycle. This causes root.render() to be called on an already-unmounted React root.

Changes

src/index.js (3 lines added):

          this.$doCheck = () => {
+           if (this._destroyed) return;
            for (let previousKey of Object.keys(previous)) {

          this.$onChanges = () => {
+           if (this._destroyed) return;
            this.root.render(React.createElement(Component, this));
          };

          this.$onDestroy = () => {
+           this._destroyed = true;
            this.root.unmount();
          };

index.d.ts — improved type declarations:

• React.Element → ComponentType<TProps> (was incorrectly typed as JSX element instead of component)
• bindings: any → { [K in keyof TProps]?: '<' | '=' | '@' | '&' } (type-safe mapping of component props to AngularJS binding types)
• Added generic <TProps> to link component props with bindings

index.js — regenerated via npm run build
package.json — version bump to 18.0.1

Test plan

• Verify angularized component renders normally with < and = bindings
• Trigger simultaneous binding change + route navigation in same digest — confirm no "Cannot update an unmounted root" error
• Verify component cleanup still works (no memory leaks from orphaned roots)
• Verify TypeScript compilation with new type declarations