aitbc
816e258d4c
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.
25 lines
1.4 KiB
Markdown
Executable File
25 lines
1.4 KiB
Markdown
Executable File
# Templates
|
|
|
|
This directory contains `hardhat --init` templates. A template serves as a blueprint for initializing a new project.
|
|
|
|
Each template is a directory with a `package.json` file and other template files.
|
|
|
|
The `package.json` file contains the template's metadata. The following fields are used during project initialization:
|
|
|
|
- `description`: A short description of the template which is displayed to the user during template selection.
|
|
- `devDependencies`: The list of dependencies that should be installed in the project.
|
|
- `peerDependencies`: The list of dependencies that should also be installed in the project as dev dependencies if the used package manager does not install peer dependencies by default.
|
|
|
|
Note that the `workspace:` prefix is stripped from the version of the template dependencies during project initialization.
|
|
|
|
The other template files are copied to the project during project initialization.
|
|
|
|
#### .gitignore files
|
|
|
|
Due to a limitation in npm, `.gitignore` files are always ignored during project packing/publishing (see https://github.com/npm/npm/issues/3763).
|
|
|
|
To work around this, we use the following convention:
|
|
|
|
- if a template file is named `gitignore`, it is copied to the project workspace as `.gitignore`;
|
|
- if a template file is named `.gitignore`, it is ignored during the project initialization (this should only affect local development, or future versions of `npm` if the aforementioned issue is resolved).
|