-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): bumped Typescript version #2797
chore(deps): bumped Typescript version #2797
Conversation
Signed-off-by: ivaylogarnev-limechain <[email protected]>
Signed-off-by: ivaylogarnev-limechain <[email protected]>
…ed some type errors Signed-off-by: ivaylogarnev-limechain <[email protected]>
Signed-off-by: ivaylogarnev-limechain <[email protected]>
Not a huge fan of these patch fixes with the |
I tried using Another potential solution would be to refactor the code to meet the new type constraints. However, given that this is legacy code within the cryptography package, a refactor doesn’t seem like a practical solution at this stage. Furthermore, I’ve noticed that |
Okay, can you just update the package.json and its LGTM. |
Signed-off-by: ivaylogarnev-limechain <[email protected]>
Signed-off-by: ivaylogarnev-limechain <[email protected]>
Description:
This PR updates the TypeScript versions to the latest stable releases across various TypeScript directories within the project and resolves any resulting type-related errors.
Related issue(s):
#2665
Checklist