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
Currently, all the bindings and associated types from the C# solution are dumped to a single file (index.mjs and bindings.g.d.ts) and are grouped via TypeScript namespaces. This is sub-optimal for both the DX and performance.
For DX it's preferable to group the exports under sub-modules instead of TypeScript namespaces, so that they can be imported in a more granular way, eg:
Additionally, TypeScript namespaces usage is generally discouraged in favor of ES modules.
For performance, TypeScript compilers and linters prefer multiple smaller declaration files instead of a single large one. This also benefits tree shaking.
The text was updated successfully, but these errors were encountered:
Currently, all the bindings and associated types from the C# solution are dumped to a single file (
index.mjs
andbindings.g.d.ts
) and are grouped via TypeScript namespaces. This is sub-optimal for both the DX and performance.For DX it's preferable to group the exports under sub-modules instead of TypeScript namespaces, so that they can be imported in a more granular way, eg:
— instead of the current:
Additionally, TypeScript namespaces usage is generally discouraged in favor of ES modules.
For performance, TypeScript compilers and linters prefer multiple smaller declaration files instead of a single large one. This also benefits tree shaking.
The text was updated successfully, but these errors were encountered: