Smart Contract Integration: Typed npm Package with TypeScript and CI/CD

The contract is deployed, and the frontend developer wants to work with it. The first option is to manually copy the ABI JSON and write calls via ethers.Contract with casting to any. The second is an npm package for smart contracts with typed wrappers imported in one line, providing autocomplete in the IDE. We specialize in the second approach: in 5+ years of working with Solidity and TypeScript, we have delivered over 30 such packages for DeFi protocols, NFT marketplaces, and L2 bridges.

The difference is especially noticeable during contract upgrades: in the first case, you have to find all places with the old ABI and hope you didn't miss any; in the second, just update the package version. If the contract changes a function signature, TypeScript throws compilation errors in all usage locations. According to our internal data, using a typed package reduces integration time by 5x (from 4 hours to 30 minutes) and lowers bug count by 70%.

Problems We Solve

Typical technical challenges teams face:

• Manual ABI copying — in a project with 50+ screens, the ABI may be pasted into 10 different files. Every deployment requires syncing all copies — one typo breaks the transaction.
• No autocomplete — developers spend up to 3 minutes per function constantly checking documentation. At team scale, that's hours per week.
• Type errors — casting with as any misses parameter mismatches; the transaction fails at gas estimation, debugging takes half a day.
• Address dispersion — contract addresses in .env or JSON, easy to mix up networks. In one project, a Sepolia address was accidentally used on mainnet — losing $15,000 worth of ETH.

Our packages eliminate these issues: ABI is automatically generated from build artifacts, addresses are centralized in a chainId → address map, types are checked at compile time.

How an npm Package Accelerates Smart Contract Integration

Consider a typical Foundry project. After forge build, artifacts are in out/. We use TypeChain with the Foundry adapter:

forge build npx typechain --target ethers-v5 --out-dir src/typechain 'out/**/!(*.dbg).json' 

This produces src/typechain/factories/MyContract__factory.ts with a typed connect() method. Then we build the npm package for smart contracts using tsup — it provides dual CJS/ESM output out of the box:

{ "main": "./dist/index.cjs", "module": "./dist/index.js", "types": "./dist/index.d.ts", "exports": { ".": { "import": "./dist/index.js", "require": "./dist/index.cjs" } } } 

In one project, we added React hooks via wagmi CLI: the wagmi generate command with the foundry plugin generated ready-to-use read/write hooks. Frontend developers could call useReadMyContract() without writing a single line of ABI interaction. Result: integration time dropped from 4 hours to 30 minutes — 8x faster.

What's Included

When ordering the development of an npm package for smart contracts, you get:

1. Source code with typed wrappers (TypeChain or viem).
2. Address map for all networks (mainnet, testnet, L2).
3. Dual build (ESM + CJS) via tsup.
4. CI/CD on GitHub Actions: automated tests, build, and publishing on tag push.
5. README documentation with import and usage examples.
6. Integration support — we help set up imports.

@myorg:registry=https://npm.pkg.github.com