mirror of https://github.com/ChainSafe/lodestar.git synced 2026-01-10 08:08:16 -05:00

Files

Nazar Hussain a0d00ac6dc chore: cleanup types exports for all packages (#8434 )

**Motivation**

Make the types exports consistent for all packages. 

All modern runtimes support [conditional
exports](https://nodejs.org/api/packages.html#conditional-exports) and
there are caveats when we have both conditional exports and normal
exports present in a package.json. This PR tend to make all exports
follow same consistent and modern pattern.

**Description**

- We were using subpath exports for some packages and module exports for
other
- Keep all the types export consistent as subpath exports.
- Remove "types" and "exports` directive from package.json 
- Remove `typesVersions`, this is useful only if we have different
version of types for different versions of Typescript. Or having
different types files for different file paths.


**Steps to test or reproduce**

- Run all CI

2025-10-20 09:03:08 -04:00

src

feat: update networking config to match CL spec (#8510 )

2025-10-13 14:44:41 +01:00

test

feat: add gloas containers (#8464 )

2025-09-26 17:02:42 +01:00

LICENSE

Rename package-level directories (#2230 )

2021-03-23 17:44:17 -05:00

package.json

chore: cleanup types exports for all packages (#8434 )

2025-10-20 09:03:08 -04:00

README.md

chore: update beacon api and consensus spec refs post electra (#7804 )

2025-05-07 15:16:48 -04:00

tsconfig.build.json

deps: upgrade tyepscript to 5.7 (#7160 )

2025-02-25 14:24:14 +01:00

tsconfig.json

chore: fix broken type check for test files (#7567 )

2025-03-13 13:47:22 +00:00

README.md

lodestar-params

This package is part of ChainSafe's Lodestar project

Lodestar defines all constants and presets defined in the Ethereum Consensus spec. This can be used in conjunction with other Lodestar libraries to interact with the Ethereum consensus.

Installation

npm install @lodestar/params

Usage

The Lodestar params package contains several items used in all downstream Lodestar libraries:

Fork names
Constants
Presets

Fork names

Many downstream components are namespaced on fork names, or otherwise rely on knowing the fork names ahead of time. The Lodestar params package exports an enum ForkName the enumerates all known fork names.

import {ForkName} from "@lodestar/params";

// dummy data
let forkName = "phase0";

switch (forkName) {
  case ForkName.phase0:
  case ForkName.altair:
  case ForkName.bellatrix:
  default:
}

Constants

All constants defined in the spec are exported verbatim.

import {GENESIS_SLOT} from "@lodestar/params";

Presets

Presets are defined in the spec as "constantish" and can only be configured at build-time. These are meant to be treated as constants, and indeed are treated as constants by all downstream Lodestar libraries. The default preset is mainnet. The only other preset defined is minimal, used only in testing environments.

The active preset is exported under the ACTIVE_PRESET named export.

import {ACTIVE_PRESET, SLOTS_PER_EPOCH} from "@lodestar/params";

The preset may be set in one of two ways:

by setting the LODESTAR_PRESET environment variable
by executing the setActivePreset(preset: Preset) function

Important Notes:

Interacting with and understanding the active preset is only necessary in very limited testing environments, like for ephemeral testnets
The minimal preset is NOT compatible with the mainnet preset.
using setActivePreset may be dangerous, and only should be run once before loading any other libraries. All downstream Lodestar libraries expect the active preset to never change.
Preset values can be overridden by executing setActivePreset(presetName: PresetName, overrides?: Partial<BeaconPreset>) and supplying values to override.
The Lodestar CLI exposes setActivePreset through --presetFile flag which allows to override the active preset with custom values from file.

License

Apache-2.0 ChainSafe Systems