CHANGELOG.md

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Unreleased

7.1.0

Changed

• Rename ControllerMessenger to Messenger (#5050)
  • ControllerMessenger has been renamed to Messenger
  • RestrictedControllerMessengerConstraint has been renamed to RestrictedMessengerConstraint
  • RestrictedControllerMessenger has been renamed to RestrictedMessenger
  • The RestrictedMessenger constructor parameter controllerMessenger has been renamed to messenger, though the old name is still accepted
  • The old names remain exported as deprecated aliases of the new names, so this is not a breaking change.

7.0.2

Changed

• Bump @metamask/utils from ^9.1.0 to ^10.0.0 (#4831)

7.0.1

Fixed

• Produce and export ESM-compatible TypeScript type declaration files in addition to CommonJS-compatible declaration files (#4648)
  • Previously, this package shipped with only one variant of type declaration files, and these files were only CommonJS-compatible, and the exports field in package.json linked to these files. This is an anti-pattern and was rightfully flagged by the "Are the Types Wrong?" tool as "masquerading as CJS". All of the ATTW checks now pass.
• Remove chunk files (#4648).
  • Previously, the build tool we used to generate JavaScript files extracted common code to "chunk" files. While this was intended to make this package more tree-shakeable, it also made debugging more difficult for our development teams. These chunk files are no longer present.

7.0.0

Added

• Migrate from @metamask/[email protected] into @metamask/base-controller: types LegacyControllerStateConstraint, RestrictedControllerMessengerConstraint and type guard functions isBaseController, isBaseControllerV1 (#4581)
• Add and export types ControllerInstance, BaseControllerInstance, StateDeriverConstraint, StateMetadataConstraint, StatePropertyMetadataConstraint, BaseControllerV1Instance, ConfigConstraintV1, StateConstraintV1 (#4581)

Fixed

• BREAKING: Fix StateMetadata type so that it requires associated metadata for all optional and non-optional top-level state properties (#4612)
  • Fixes issue of runtime error being thrown during BaseController instantiation due to missing metadata for optional state properties.

6.0.3

Changed

• Bump typescript from ~5.0.4 to ~5.2.2 (#4576, #4584)

6.0.2

Changed

• Bump TypeScript version to ~5.0.4 and set moduleResolution option to Node16 (#3645)
• Bump @metamask/utils from ^9.0.0 to ^9.1.0 (#4529)

6.0.1

Changed

• Bump @metamask/rpc-errors from 6.2.1 to ^6.3.1 (#4516)
• Bump @metamask/utils from ^8.3.0 to ^9.0.0 (#4516)

6.0.0

Changed

• BREAKING: Bump minimum Node version to 18.18 (#3611)

5.0.2

Changed

• Bump TypeScript version to ~4.9.5 (#4084)

5.0.1

Fixed

• Fix types field in package.json (#4047)

5.0.0

Added

• BREAKING: Add ESM build (#3998)
  • It's no longer possible to import files from ./dist directly.
• Add and export type StateConstraint, which is an alias for Record<string, Json> (#3949)
  • This type represents the narrowest supertype of the state of all controllers.
  • Importing this type enables controllers to constrain state objects and types to be JSON-serializable without having to directly add @metamask/utils as a dependency.

Changed

• BREAKING: Narrow the return types of functions getAnonymizedState<ControllerState> and getPersistentState<ControllerState> from Record<string, Json> to Record<keyof ControllerState, Json>. (#3949, #4040)
• BREAKING: Align type-level and runtime behavior of getRestricted so that omitted or empty inputs consistently represent a set of empty allowlists (#4013)
  • If the AllowedActions and AllowedEvents generic parameters are omitted, they are always assumed to be never.
    • Previously, omission of these generic parameters resulted in the full allowlists for the controller being inferred as type constraints for the allowedActions and allowedEvents function parameters.
  • If the function parameters allowedActions and allowedEvents are a non-empty array, their corresponding type names must be explicitly passed into generic parameters AllowedActions and AllowedEvents to avoid type errors.
    • This may cause some duplication of allowlists between type-level and value-level code.
    • This requirement is only relevant for TypeScript code. A JavaScript consumer only needs to pass in the correct value-level function parameters. Because of this, these changes should not affect downstream JavaScript code, but may be disruptive to TypeScript code.
    • getRestricted is still able to flag AllowedActions and AllowedEvents members that should not be included in the allowlists, based on the Action and Event generic arguments passed into the ControllerMessenger instance.
• BREAKING: The RestrictedControllerMessenger class constructor now expects allowedActions and allowedEvents as required options (#4013)
• BREAKING: Add string as generic constraint to the Name generic parameter of the types NamespacedBy and NotNamespacedBy (#4036)
• BREAKING: The getRestricted method of the ControllerMessenger class now expects both allowedActions and allowedEvents as required parameters.
  • An empty array is required if no allowed actions or events are desired.
• Convert interface StatePropertyMetadata into a type alias (#3949)

Removed

• BREAKING: Remove the deprecated subscribe class field from BaseController (#3949)
  • This property was used to differentiate between BaseControllerV1 and BaseController (v2) controllers. It is no longer used.

Fixed

• BREAKING: Narrow the generic constraint of the ControllerState parameter from Record<string, unknown> to Record<string, Json> for types ControllerGetStateAction, ControllerStateChangeEvent, ControllerActions, and ControllerEvents (#3949)
• BREAKING: Fix BaseController so that mutating state directly now results in a runtime error (#4011)
  • Directly modifying the state outside of an update call may lead to parts of the application being out of sync, because such modifications do not result in the stateChange event being fired.
  • Instead of mutating the state of a controller after instantiation, consumers should either initialize that controller with the proper state via options or should use the update method to safely modify the state.
• BREAKING: Fix subscribe on ControllerMessenger and RestrictedControllerMessenger to infer correct types for selector arguments (#4012)
  • Previously, the types of the arguments that the selector function received would always be inferred as never, but now the types match those of publish (the "event payload"). This means that you shouldn't need to add use type annotations or assertions to type the selector arguments.

4.1.1

Changed

• Bump @metamask/utils to ^8.3.0 (#3769)

4.1.0

Added

• Add registerInitialEventPayload to ControllerMessenger and RestrictedControllerMessenger (#3697)
  • This allows registering an event payload function for an event, which has the benefit of ensuring the "subscription selector" feature works correctly the first time the event is fired after subscribing.

Fixed

• Fix subscribe method selector support on first publish (#3697)
  • An event with a registered initial event payload function will work better with selectors, in that it will correctly compare with the initial selected state and return the previous value the first time it's published. Without this, the initial published event will always return undefined as the previous value.
• Subscribers to the stateChange event of any BaseControllerV2-based controllers will now correctly handle the initial state change event (#3702)
  • Previously the initial state change would always result in this event firing, even for subscriptions with selectors where the selected value has not changed. Additionally, the previousValue returned was always set to undefined the first time.
  • BaseControllerV2 has been updated to correctly compare with the previous value even for the first state change. The returned previousValue is also now guaranteed to be correct even for the initial state change.

4.0.1

Changed

• Deprecate subscribe property from BaseControllerV2 (#3590, #3698)
  • This property was used to differentiate between BaseControllerV1 and BaseControllerV2 controllers. It is no longer used, so it has been marked as deprecated.

4.0.0

Added

• Add ControllerGetStateAction and ControllerStateChangeEvent types (#1890, #2029)
• Add NamespacedName type (#1890)
  • This is the narrowest supertype of all names defined within a given namespace.
• Add NotNamespacedBy type, which matches an action/event name if and only if it is not prefixed by a given namespace (#2051)

Changed

• BREAKING: Alter controller messenger ActionHandler type so Action type parameter must satisfy (updated) ActionConstraint (#1890)
• BREAKING: Alter controller messenger ExtractActionParameters utility type so Action type parameter must satisfy (updated) ActionConstraint (#1890)
• BREAKING: Alter controller messenger ExtractEventHandler utility type so Event type parameter must satisfy EventConstraint (#1890)
• BREAKING: Alter controller messenger ExtractEventPayload utility type so Event type parameter must satisfy EventConstraint and Event['payload'] must be an array (to match behavior of ExtractEventHandler) (#1890)
• BREAKING: Alter controller messenger SelectorFunction type so that its generic parameter Args is replaced by Event, which must satisfy EventConstraint, and it returns a function whose arguments satisfy the event payload type specified by Event (#1890)
• BREAKING: BaseController is now renamed to BaseControllerV1 and has been deprecated; BaseController now points to what was previously called BaseControllerV2 (#2078)
  • This should encourage use of BaseController v2 for new controllers going forward.
  • If your controller is importing BaseControllerV2, you will need to import BaseController instead.
  • If your controller is still importing BaseController v1, you will need to import and use BaseControllerV1 instead. That said, please consider migrating your controller to v2.
• BREAKING: The restricted controller messenger now allows calling all internal events and actions by default and prohibits explicitly allowlisting any of them (#2050, #2051)
  • Previously internal events and actions were only usable if they were listed as "allowed" via the allowedActions or allowedEvents options to the RestrictedControllerMessenger constructor or ControllerMessenger.getRestricted(). Now this works implicitly.
  • In fact, attempting to allowlist any of them will raise a type error, as otherwise, it would be possible to specify a partial list of allowed actions or events, and that would be misleading, since all of them are allowed anyway.
• BREAKING: Rename Namespaced type to NamespacedBy (#2051)
• Alter controller messenger ActionConstraint['handler'] type to remove usage of any (#1890)
  • This type is now defined as the universal supertype of all functions, meaning any function can be safely assigned as an action handler, regardless of argument types, number of arguments, or return value type.
• Bump @metamask/utils to ^8.2.0 (#1957)

3.2.3

Changed

• Bump dependency on @metamask/utils to ^8.1.0 (#1639)

3.2.2

Changed

• Update TypeScript to v4.8.x (#1718)

3.2.1

Changed

• There are no consumer-facing changes to this package. This version is a part of a synchronized release across all packages in our monorepo.

3.2.0

Changed

• When deriving state, skip properties with invalid metadata (#1529)
  • The previous behavior was to throw an error
  • An error is thrown in a timeout handler so that it can still be captured in the console, and by global unhandled error handlers.
• Update @metamask/utils to ^6.2.0 (#1514)

3.1.0

Changed

• Prevent event publish from throwing error (#1475)
  • The controller messenger will no longer throw when an event subscriber throws an error. Calls to publish (either within controllers or on a messenger instance directly) will no longer throw errors.
  • Errors are thrown in a timeout handler so that they can still be logged and captured.

3.0.0

Changed

• BREAKING: Bump to Node 16 (#1262)
• Replace @metamask/controller-utils dependency with @metamask/utils (#1370)

2.0.0

Removed

• BREAKING: Remove isomorphic-fetch (#1106)
  • Consumers must now import isomorphic-fetch or another polyfill themselves if they are running in an environment without fetch

1.1.2

Changed

• Rename this repository to core (#1031)
• Update @metamask/controller-utils package (#1041)

1.1.1

Changed

• Relax dependency on @metamask/controller-utils (use ^ instead of ~) (#998)

1.1.0

Added

• Add applyPatches function to BaseControllerV2 (#980)

Changed

• Action and event handler types are now exported (#987)
• Update update function to expose patches (#980)

1.0.0

Added

• Initial release

  • As a result of converting our shared controllers repo into a monorepo (#831), we've created this package from select parts of @metamask/controllers v33.0.0, namely:

    • src/BaseController.ts
    • src/BaseController.test.ts
    • src/BaseControllerV2.ts
    • src/BaseControllerV2.test.ts
    • src/ComposableController.ts
    • src/ComposableController.test.ts
    • src/ControllerMessenger.ts
    • src/ControllerMessenger.test.ts

    All changes listed after this point were applied to this package following the monorepo conversion.