Too many packages need to upgrade after lumos upgrading

[homura]

Lumos has more than 15 scoped child packages @ckb-lumos/* in it, although Lumos provides an entry package @ckb-lumos/lumos to integrate them into one, however, it still doesn't meet its target of just importing one entry package, because not all exported modules in child packages are included.

We need to improve the @ckb-lumos/lumos to make the entry package more convenient for developers, so they don't need to import too many @ckb-lumos/*

[homura]

In the beginning, the first idea was to change @ckb-lumos/lumos's exports by migrating its export mode via the esmodule way. After a simple survey, I found that developers are more likely to use a default tsconfig.json without modifying its moduleResolution. Therefore, switching to esmodule directly isn't a feasible solution for the problem.

An option to consider is modifying @ckb-lumos/lumos's build script to generate compiled .js files in its root instead of in the lib directory, also exporting modules that are not exported but commonly used. So we can use it like this

import { Uint32, Uint64 } from '@ckb-lumos/lumos/codec/number'
import { option } from '@ckb-lumos/lumos/codec/molecule'

const DynamicNumberCodec = union({
  Uint32,
  Uint64
}, ['Uint32', 'Uint64'])

Wait, the @ckb-lumos/lumos is a bit too long, maybe we can change it to ckb-lumos, which I noticed is currently unregistered on npm. So we can just import lumos like this

import { Uint32, Uint64 } from 'ckb-lumos/codec/number'
import { helpers, utils } from 'ckb-lumos'