Update package.json: Remove typings #340
Open
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.
1)The typings field is an outdated field used in earlier versions of TypeScript (before ~2.0) as an alternative to types. It served the same purpose, but with the release of TypeScript 2.0 and later, types became the standard, and typings became deprecated. TypeScript still supports typings for backward compatibility, but its use is not recommended.
2)Having two fields pointing to the same file does not add functionality but increases the likelihood of confusion. For example, if you update the path in types in the future but forget to update typings, it could lead to inconsistencies, and some tools might attempt to use the outdated path.
PR-Codex overview
This PR focuses on updating the
package.json
file in theagw-client
package to streamline type definitions and exports.Detailed summary
"typings"
field frompackage.json
."types"
field still points to./dist/types/exports/index.d.ts
."exports"
field for module resolution.