[Bug]: type imports not working in v2

[OrmEmbaar]

SDK Version

2.0.0

Environment

Node 22

Describe the Bug

The types imports appear to be broken for v2. createHelius should returned a defined HeliusClient type. However, the returned value has a type of any. When inspecting the installed package in node_modules, it seems the old v1 types are still present and that package.json types field is pointing at those types.

Steps to Reproduce

import { createHelius, type HeliusClient } from 'helius-sdk'

const helius = createHelius({ apiKey: process.env.HELIUS_API_KEY! });

helius.hahaThisIsNotAMethod('foooo'); // builds without error

Expected Behavior

The package types should work properly with typescript.

Logs/Screenshots

Additional Checks

• I have searched for existing issues and this is not a duplicate.
• I have tested with the latest version.

[0xIchigo]

Ah @OrmEmbaar, nice catch! Looks like some of the v1 types got left in with the migration. I'll open a PR to address this, thanks!

[OrmEmbaar]

@0xIchigo The fix is also broken; it's now not possible to import the package at all. Looks to me like the issue is broken import paths. The package.json references ./dist/src/rpc/index.js, but I think it should be ./dist/rpc/index.js (there is no src directory in the build dir).

[0xIchigo]

Damn, that's my b @OrmEmbaar—forgot to push the other commit since it's flattened. Cutting a new release now. Thanks!

[0xIchigo]

@OrmEmbaar, thank you again for your help! Everything is now fixed in version 2.0.2 🥳

[OrmEmbaar]

Sorry @0xIchigo but this still isn't working. Intellisense gives me type HeliusClient = any when I hover HeliusClient in dist/index.d.ts. I think ResolvedHeliusRpcApi is resolving to any, forcing the HeliusClient intersection type to any.

[0xIchigo]

Ah. I took another look @OrmEmbaar, and it seems that ResolvedHeliusRpcApi gets resolved to any in intellisense instead of its current type, causing the entire intersection to degrade to any. Will open another PR for this so it's fixed in the next release

[OrmEmbaar]

@0xIchigo what is your release schedule for this fix?