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.
env-paths
Get paths for storing things like data, config, cache, etc
Uses the correct OS-specific paths. Most developers get this wrong.
Install
$ npm install env-paths
Usage
const envPaths = require('env-paths');
const paths = envPaths('MyApp');
paths.data;
//=> '/home/sindresorhus/.local/share/MyApp-nodejs'
paths.config
//=> '/home/sindresorhus/.config/MyApp-nodejs'
API
paths = envPaths(name, options?)
Note: It only generates the path strings. It doesn't create the directories for you. You could use make-dir to create the directories.
name
Type: string
Name of your project. Used to generate the paths.
options
Type: object
suffix
Type: string
Default: 'nodejs'
Don't use this option unless you really have to!
Suffix appended to the project name to avoid name conflicts with native
apps. Pass an empty string to disable it.
paths.data
Directory for data files.
Example locations (with the default nodejs suffix):
- macOS:
~/Library/Application Support/MyApp-nodejs - Windows:
%LOCALAPPDATA%\MyApp-nodejs\Data(for example,C:\Users\USERNAME\AppData\Local\MyApp-nodejs\Data) - Linux:
~/.local/share/MyApp-nodejs(or$XDG_DATA_HOME/MyApp-nodejs)
paths.config
Directory for config files.
Example locations (with the default nodejs suffix):
- macOS:
~/Library/Preferences/MyApp-nodejs - Windows:
%APPDATA%\MyApp-nodejs\Config(for example,C:\Users\USERNAME\AppData\Roaming\MyApp-nodejs\Config) - Linux:
~/.config/MyApp-nodejs(or$XDG_CONFIG_HOME/MyApp-nodejs)
paths.cache
Directory for non-essential data files.
Example locations (with the default nodejs suffix):
- macOS:
~/Library/Caches/MyApp-nodejs - Windows:
%LOCALAPPDATA%\MyApp-nodejs\Cache(for example,C:\Users\USERNAME\AppData\Local\MyApp-nodejs\Cache) - Linux:
~/.cache/MyApp-nodejs(or$XDG_CACHE_HOME/MyApp-nodejs)
paths.log
Directory for log files.
Example locations (with the default nodejs suffix):
- macOS:
~/Library/Logs/MyApp-nodejs - Windows:
%LOCALAPPDATA%\MyApp-nodejs\Log(for example,C:\Users\USERNAME\AppData\Local\MyApp-nodejs\Log) - Linux:
~/.local/state/MyApp-nodejs(or$XDG_STATE_HOME/MyApp-nodejs)
paths.temp
Directory for temporary files.
Example locations (with the default nodejs suffix):
- macOS:
/var/folders/jf/f2twvvvs5jl_m49tf034ffpw0000gn/T/MyApp-nodejs - Windows:
%LOCALAPPDATA%\Temp\MyApp-nodejs(for example,C:\Users\USERNAME\AppData\Local\Temp\MyApp-nodejs) - Linux:
/tmp/USERNAME/MyApp-nodejs
Tidelift helps make open source sustainable for maintainers while giving companies
assurances about security, maintenance, and licensing for their dependencies.