Add exports field to fix webpack errors #1617
Merged
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.
Description
Adds a
exports
field to direct bundlers (mainly webpack) to the correct entry point. Having that entry in there is good practice anyway, and the other@inversifyjs/*
packages already have anexports
field.Related Issue
#1616
Motivation and Context
I assume other people will have a similar issue when it comes to using webpack and CJS (i.e.
require
) of inversify.How Has This Been Tested?
Applying this change to my local environment has fixed the issue reported in #1616.
Types of changes
Checklist: