Fixes _types
generation and modernizes module resolution.
#56
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.
Currently, the
_types
is built usingnode
module resolution, which results in this project generating invalid types. Details about the TypeScript bug can be found at microsoft/TypeScript#60930 (comment) and there are no plans to fix it sincenode
(which is equivalent tonode10
) is being deprecated in TypeScript soon.The way this bug manifests is in files like
src/_types/core/P256.d.ts
where it would previously generate code like:when it should have generated code like this (which is what is generated after this change):
For the cjs build command, I changed from
node
tonode10
to be more explicit/clear, sincenode
was just an alias fornode10
.For the esm build command, I changed it to use the tsconfig so it is less likely to get out of sync with the generated types.
Also updated .gitignore to ignore
.pnpm-store
which had 30,000 files it wanted to commit after I didpnpm install
using the recommended version ofpnpm
.