fix incorrect default export type as mentioned in issue #33 #38
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned in Issue #33 , the typing in
index.d.ts
incorrectly declared a default export, butindex.js
has no default export. This caused issues with Node16/CommonJS module settings and having esModuleInterop set to false. (More details.)This fix deliberately changes only the type definition (to be exact, the generator for the type definition).
Because the package also exports types, the fix suggested in #33 was not enough. To be able to export types with the old syntax, I had to add a namespace declaration in which the exported types are nested.
As a drive-by change, the tsd dependency (tool for testing type definitions) was also updated to the newest version.
This change might break clients that applied one of the suggested workarounds in issue #33 as the types are now correct.
Clients not affected should see no changes.