Improve Support for TypeScript NodeNext/Node16 Module Resolution #742
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.
If you update your TypeScript settings to use the new NodeNext moduleResolution setting, you can't use the Docxtemplater class without add an extra
.default
access:This problem is explained more generally here.
In Docxtemplater's case, this would likely crash at runtime, since there is no explicit
.default
property on the export.This PR uses the recommended guidance to make the types compatible with NodeNext (confirmed still compatible with the previous non-NodeNext/Node16 resolution). It also adds an explicit
.default
attribute on the export for improved compatibility with those not using the TypeScriptesModuleInterop: true
setting.