fix: P-1203 unified npm package version

[higherordertech]

Context

Fixing conflicting npm package.

Labels

Please apply following PR-related labels when appropriate:

• C0-breaking: if your change could break the existing client, e.g. API change, critical logic change
• C1-noteworthy: if your change is non-breaking, but is still worth noticing for the client, e.g. reference code improvement

How (Optional)

Testing Evidences

Please attach any relevant evidences if applicable

[linear]

P-1203 Resolve conflicting packages in ts-tests.

[Kailai-Wang]

@0xverin please review it : )

[0xverin]

1. After deleting pnpm-lock.yaml and node_modules, there are still many unmet peers when running pnpm install. I think the lock file should be deleted(at least at this update) and then update the package for testing, otherwise, it's impossible to know the correct version range of the package, as the locked version is used during pnpm install.

2. ts-tests still have unmet peers (tested without deleting pnpm-lock.yaml).

3. Can you find a way to run all the tests in CI (like adding a console.log in tests to triggle ci or something), the CI passed, but actually none of the tests were run?I am worried that with version modifications, some methods may become ineffective. thank you.

[higherordertech]

1. After deleting pnpm-lock.yaml and node_modules, there are still many unmet peers when running pnpm install. I think the lock file should be deleted(at least at this update) and then update the package for testing, otherwise, it's impossible to know the correct version range of the package, as the locked version is used during pnpm install.

2. ts-tests still have unmet peers (tested without deleting pnpm-lock.yaml). 3. Can you find a way to run all the tests in CI (like adding a console.log in tests to triggle ci or something), the CI passed, but actually none of the tests were run?I am worried that with version modifications, some methods may become ineffective. thank you.

fixed now.

[0xverin]

1. After deleting pnpm-lock.yaml and node_modules, there are still many unmet peers when running pnpm install. I think the lock file should be deleted(at least at this update) and then update the package for testing, otherwise, it's impossible to know the correct version range of the package, as the locked version is used during pnpm install.

2. ts-tests still have unmet peers (tested without deleting pnpm-lock.yaml). 3. Can you find a way to run all the tests in CI (like adding a console.log in tests to triggle ci or something), the CI passed, but actually none of the tests were run?I am worried that with version modifications, some methods may become ineffective. thank you.

fixed now.

I also fixed the issues after the solc upgrade In parachain ts-tests.