refactor: move brother_node development artifact to dev/test-nodes subdirectory
Development Artifact Cleanup: ✅ BROTHER_NODE REORGANIZATION: Moved development test node to appropriate location - dev/test-nodes/brother_node/: Moved from root directory for better organization - Contains development configuration, test logs, and test chain data - No impact on production systems - purely development/testing artifact ✅ DEVELOPMENT ARTIFACTS IDENTIFIED: - Chain ID: aitbc-brother-chain (test/development chain) - Ports: 8010 (P2P) and 8011 (RPC) - different from production - Environment: .env file with test configuration - Logs: rpc.log and node.log from development testing session (March 15, 2026) ✅ ROOT DIRECTORY CLEANUP: Removed development clutter from production directory - brother_node/ moved to dev/test-nodes/brother_node/ - Root directory now contains only production-ready components - Development artifacts properly organized in dev/ subdirectory DIRECTORY STRUCTURE IMPROVEMENT: 📁 dev/test-nodes/: Development and testing node configurations 🏗️ Root Directory: Clean production structure with only essential components 🧪 Development Isolation: Test environments separated from production BENEFITS: ✅ Clean Production Directory: No development artifacts in root ✅ Better Organization: Development nodes grouped in dev/ subdirectory ✅ Clear Separation: Production vs development environments clearly distinguished ✅ Maintainability: Easier to identify and manage development components RESULT: Successfully moved brother_node development artifact to dev/test-nodes/ subdirectory, cleaning up the root directory while preserving development testing environment for future use.
This commit is contained in:
41
dev/env/node_modules/ethers/src.ts/abi/index.ts
generated
vendored
Executable file
41
dev/env/node_modules/ethers/src.ts/abi/index.ts
generated
vendored
Executable file
@@ -0,0 +1,41 @@
|
||||
/**
|
||||
* The Application Binary Interface (ABI) describes how method input
|
||||
* parameters should be encoded, their results decoded, and how to
|
||||
* decode events and errors.
|
||||
*
|
||||
* See [About ABIs](docs-abi) for more details how they are used.
|
||||
*
|
||||
* @_section api/abi:Application Binary Interface [about-abi]
|
||||
* @_navTitle: ABI
|
||||
*/
|
||||
|
||||
|
||||
//////
|
||||
export { AbiCoder } from "./abi-coder.js";
|
||||
|
||||
export { decodeBytes32String, encodeBytes32String } from "./bytes32.js";
|
||||
|
||||
export {
|
||||
ConstructorFragment, ErrorFragment, EventFragment, FallbackFragment,
|
||||
Fragment, FunctionFragment, NamedFragment, ParamType, StructFragment,
|
||||
} from "./fragments.js";
|
||||
|
||||
export {
|
||||
checkResultErrors,
|
||||
Indexed,
|
||||
Interface,
|
||||
ErrorDescription, LogDescription, TransactionDescription,
|
||||
Result
|
||||
} from "./interface.js";
|
||||
|
||||
export { Typed } from "./typed.js";
|
||||
|
||||
export type {
|
||||
JsonFragment, JsonFragmentType,
|
||||
FormatType, FragmentType, ParamTypeWalkAsyncFunc, ParamTypeWalkFunc
|
||||
} from "./fragments.js";
|
||||
|
||||
export type {
|
||||
InterfaceAbi,
|
||||
} from "./interface.js";
|
||||
|
||||
Reference in New Issue
Block a user