-
Notifications
You must be signed in to change notification settings - Fork 931
Cascade Bumping of dependencies after release cause typing error while rebuilding #2533
Comments
Same bug here. |
Same bug here |
same bug here |
For now, adding an override in package.json seems to be enough to solve the issue.
spl-token library got updated in the last realease and it brings some broken references in. |
Help me understand a bit more about what's going on here:
Things I know: |
As far as i managed to understand, |
Additionally, the package got updated litterally 4 hours ago, so it might be fixed by now. |
I tried typechecking with |
Also possible: The TypeScript feature (const type parameters) in the OP was introduced in TypeScript 5. If you're on 4 you should upgrade. |
I am running into this same issue (0.4.6 of spl-token)
The dependency resolution for me was to: https://www.npmjs.com/package/@solana/codecs-data-structures/v/2.0.0-preview.2
what options do we have if we cannot upgrade to typescript 5? |
You could consider |
Because there has been no activity on this issue for 7 days since it was closed, it has been automatically locked. Please open a new issue if it requires a follow up. |
Overview
Hi,
While trying to reinstall the packages of my typescript application using npm v10.5.0 (node v20.12.1) I came across an issue that led me not to be able to build (using ./node_modules/typescript/bin/tsc). solana-web3.js has had a really recent release and it seems like the update of solana-web3.js create a cascade of dependencies update that leads me to the following kind of error:
Steps to reproduce
In a typescript app that contains "@solana/web3.js" as a dependencies in the package.json and which was not already updated after the recent release:
delete node_modules folder,
delete package-lock.json file,
run npm i,
run ./node_modules/typescript/bin/tsc
You should obtain the same kind of error as shown before.
Description of bug
When running ./node_modules/typescript/bin/tsc after installing back my node_modules I got the errors provided earlier. I expect not to get these errors just by installing back my packages
Thanks in advance for your help
The text was updated successfully, but these errors were encountered: