You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
@metamask/accounts-controller 18.2.1
Changed
Bump @metamask/eth-snap-keyring from ^4.3.1 to ^4.3.3 (#4689)
Bump @metamask/snaps-sdk from ^6.1.1 to ^6.5.0 (#4689)
Bump @metamask/snaps-utils from ^7.8.1 to ^8.1.1 (#4689)
Bump peer dependency @metamask/snaps-controllers from ^9.3.0 to ^9.7.0 (#4689)
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.
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.
@metamask/address-book-controller 6.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.
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.
@metamask/announcement-controller 7.0.1
Changed
Bump TypeScript from ~4.9.5 to ~5.2.2 and set moduleResolution option to Node16 (#3645, #4576, #4584)
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.
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.
@metamask/approval-controller 7.0.4
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.
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.
@metamask/assets-controllers 38.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.
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.
Don't update currency rates on transient errors (#4662)
In CurrencyRateController if unexpected errors occur during requests to
crypto compare, the conversion rate in state will remain unchanged instead
of being set to null.
Fix fallback conversion rate for token market data (#4615)
On networks where the native currency is not ETH, token market data is now
correctly priced in the native currency.
@metamask/base-controller 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.
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.
@metamask/build-utils 3.0.1
Changed
Bump @metamask/utils from ^8.3.0 to ^9.1.0 (#4516, #4529)
Bump @metamask/rpc-errors from ^6.2.1 to ^6.3.1 (#4516)
Bump TypeScript from ~4.9.5 to ~5.2.2 and set moduleResolution option to Node16 (#3645, #4576, #4584)
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.
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.
@metamask/chain-controller 0.1.2
Changed
Bump @metamask/keyring-api from ^8.0.1 to ^8.1.0 (#4594)
Bump TypeScript from ~4.9.5 to ~5.2.2 and set moduleResolution option to Node16 (#3645, #4576, #4584)
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.
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.
@metamask/composable-controller 9.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.
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.
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.
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.
@metamask/ens-controller 14.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.
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.
@metamask/eth-json-rpc-provider 4.1.4
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.
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.
@metamask/gas-fee-controller 20.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.
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.
@metamask/json-rpc-engine 9.0.3
Changed
Bump TypeScript from ~5.0.4 to ~5.2.2 (#4576, #4584)
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.
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.
@metamask/json-rpc-middleware-stream 8.0.3
Changed
Bump TypeScript from ~5.0.4 to ~5.2.2 (#4576, #4584)
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.
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.
@metamask/keyring-controller 17.2.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.
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.
@metamask/logging-controller 6.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.
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.
@metamask/message-manager 10.1.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.
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.
@metamask/name-controller 8.0.1
Changed
Bump @metamask/utils from ^8.3.0 to ^9.1.0 (#4516, #4529)
Bump @metamask/rpc-errors from ^6.2.1 to ^6.3.1 (#4516)
Bump TypeScript from ~4.9.5 to ~5.2.2 and set moduleResolution option to Node16 (#3645, #4576, #4584)
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.
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.
@metamask/network-controller 21.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.
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.
@metamask/notification-controller 6.0.1
Changed
Bump @metamask/utils from ^8.3.0 to ^9.1.0 (#4516, #4529)
Bump @metamask/rpc-errors from ^6.2.1 to ^6.3.1 (#4516)
Bump TypeScript from ~4.9.5 to ~5.2.2 and set moduleResolution option to Node16 (#3645, #4576, #4584)
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.
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.
@metamask/notification-services-controller 0.5.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.
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.
@metamask/permission-controller 11.0.2
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.
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.
@metamask/permission-log-controller 3.0.1
Changed
Bump @metamask/utils from ^8.3.0 to ^9.1.0 (#4516, #4529)
Bump @metamask/rpc-errors from ^6.2.1 to ^6.3.1 (#4516)
Bump TypeScript from ~4.9.5 to ~5.2.2 and set moduleResolution option to Node16 (#3645, #4576, #4584)
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.
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.
@metamask/phishing-controller 12.0.3
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.
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.
@metamask/polling-controller 10.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.
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.
@metamask/preferences-controller 13.0.3
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.
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.
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.
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.
Remove extra slash when constructing user storage url (#4702)
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.
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.
Remove extra slash when constructing user storage url (#4702)
@metamask/rate-limit-controller 6.0.1
Changed
Bump @metamask/utils from ^8.3.0 to ^9.1.0 (#4516, #4529)
Bump @metamask/rpc-errors from ^6.2.1 to ^6.3.1 (#4516)
Bump TypeScript from ~4.9.5 to ~5.2.2 and set moduleResolution option to Node16 (#3645, #4576, #4584)
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.
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.
When the default RPC endpoint changes for a network, domains that were
referencing a network client id on that network are redirected to the new
default RPC endpoint.
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.
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.
@metamask/signature-controller 19.1.0
Added
Add initial tracing to SignatureController (#4655)
Adds an optional trace callback to the constructor, and an optional traceContext option to the newUnsignedTypedMessage and newUnsignedPersonalMessage methods.
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.
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.
@metamask/transaction-controller 37.0.0
Changed
Remove unapproved transactions during initialisation (#4658)
Fail approved and signed transactions during initialisation (#4658)
Remove TraceContext, TraceRequest, and TraceCallback types (#4655)
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.
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.
@metamask/user-operation-controller 15.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.
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.