refactor: use types
consistently instead of typings
#130
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.
Summary
Rename
typings
fields and directories totypes
Follow-up to #126
Details
since
typings
is now considered a legacy alias and can't be used inside ofexports
(as I discovered in fix(pkg): addtypes
topackage.json#exports
#126 (comment)), update all references to consistently usetypes
package.json#typings
->types
typings
folder ->types
for similar reasons, use consistent relative path
./
inpackage.json
types
matchesexports.types
,main
matchesexports.require
, andmodule
matchesexports.import
exactly