add lazy loaders for .cjs file

[glitch003]

I don't know how this actually works, I just asked cursor to fix the problem of including all the ABIs. we should prob test that this actually fixes the problem.

---

Anson:

WHAT

• update the script to generate lazily require individual network artifacts and signature bundles instead of loading them eagerly
• add sideEffects: false to package metadata so bundlers can tree-shake unused contract outputs

Example

// BEFORE
const { nagaStaging } = require('@lit-protocol/contracts');
console.log(nagaStaging); // loads every network artifact up front

// AFTER
const contracts = require('@lit-protocol/contracts');
console.log(nagaStaging); // bundler/runtime only pulls naga-staging when accessed

TEST

Snapshots are released here, but they are NOT tested yet. (Note: @lit-protocol/contracts is backward-compatible, so we can use the same version for Datil, V7)

🦋  success packages published successfully:
🦋  @lit-protocol/[email protected]
🦋  @lit-protocol/[email protected]
🦋  @lit-protocol/[email protected]
🦋  @lit-protocol/[email protected]
🦋  @lit-protocol/[email protected]

[Copilot]

Pull Request Overview

This PR implements lazy loading for CJS modules to avoid eagerly loading all ABIs when requiring the contracts package. The changes introduce a lazy loading mechanism using property getters and mark the package as side-effect free for better bundler optimization.

• Replaces direct require() calls with lazy getters that defer loading until accessed
• Adds a __defineLazy helper function to create property getters for module exports
• Marks the package as having no side effects in package.json

Reviewed Changes

Copilot reviewed 2 out of 7 changed files in this pull request and generated 2 comments.

File	Description
packages/contracts/src/sync.ts	Implements lazy loading mechanism with __defineLazy helper and updates module export generation
packages/contracts/package.json	Adds sideEffects: false to enable better tree-shaking optimization

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The function parameters lack type annotations. In a TypeScript file, parameters should be typed for better type safety and IDE support.

Suggested change

	function __defineLazy(target, key, getter) {
	function __defineLazy(target: object, key: string | symbol, getter: () => any): void {

[Copilot]

The __exports object lacks type annotation. Consider typing it as Record<string, any> or a more specific interface to maintain type safety.

Suggested change

	const __exports = {};
	const __exports: Record<string, any> = {};

[Ansonhkg]

I'm not sure this will work, this only approves the CJS lazy getters do their job at run time, sadly not when it bundles... If the bundler starts from CommonJS root, it will still drag in every network..

[glitch003]

I'm not sure this will work, this only approves the CJS lazy getters do their job at run time, sadly not when it bundles... If the bundler starts from CommonJS root, it will still drag in every network..

I think you're right. I made a little test repo here: https://github.com/LIT-Protocol/contract-shrinkage-test

it seems like it worked for ESM, which I think is due to adding sideEffects: false to the package.json in this PR. But the CJS version is the same.

I'm not sure how to fix this in the CJS version tbh.

[Ansonhkg]

I'm not sure this will work, this only approves the CJS lazy getters do their job at run time, sadly not when it bundles... If the bundler starts from CommonJS root, it will still drag in every network..

I think you're right. I made a little test repo here: https://github.com/LIT-Protocol/contract-shrinkage-test

it seems like it worked for ESM, which I think is due to adding sideEffects: false to the package.json in this PR. But the CJS version is the same.

I'm not sure how to fix this in the CJS version tbh.

The issue I think is actually from this mapper file:

• naga mapper.ts
• datil mapper.ts

import { datilDev, datilTest, datil } from '@lit-protocol/contracts';

This line resolves to the CJS root, so any build that runs through this file sees the whole contracts package and bundles every network blob.

Since we already expose each contract bundle (in @lit-protocol/contracts) and its signatures as explicit export-map subpaths like this:

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

I THINK, in the mapper we can do:

  import { datil } from '@lit-protocol/contracts/prod/datil';
  import { datilDev } from '@lit-protocol/contracts/prod/datil-dev';
  import { datilTest } from '@lit-protocol/contracts/prod/datil-test.';

That keeps the existing mapper pattern, but allows bundlers to include just the network a consumer uses. I think the fix might be simplier than we thought? need to test though.

[Ansonhkg]

Closing this in favour of this #963