Refactor JS Folder to Enable Per-Network Package Separation and Deployment #15
Description
JS Folder Now Has Core/Main Components
- Blockchain.Abstractions
- TemporalHelper
- Data
These folders are separate packages and are intended to be referenced by any network implementation. Then we have specific network implementations, like:
- Blockchain.Starknet
Currently, the separation of these packages is not properly done. The entire js folder is being built together, including all dependencies. As a result, different Docker images are being produced—for example, one for Starknet, one for Fuel, etc.
What Needs to Be Done
We need to properly separate the packages so that we can build and deploy only the necessary parts. For example, we should be able to build and deploy Starknet along with its dependencies without building or deploying Fuel-related code.