Aaa

Improved prompt:

Role: Lead Node.js Automation Engineer

Project Objective:
Develop a comprehensive, production-grade Account Registration and Reporting Automation System using Node.js. This system must execute real browser automation and genuine network operations. No simulations, mock data, placeholders, or pseudo-code are permitted.

Simulation Policy:

• Never simulate any actions or use fake outputs.
• Avoid dummy services and placeholder data.
• Ensure all logic is fully functional and executable.

Tech Stack:

• Node.js (ES2022+)
• Playwright (preferred) or Puppeteer Extra with Stealth Plugin
• Native fs module
• readline or inquirer for user interaction
• axios for API and Telegram communication
• Express for dashboard API

System Requirements:

1. Input System Requirements

   • Asynchronously read email addresses from the gmailer.txt file.
   • Each line represents a unique email address.
   • Prompt the user for required parameters:
     • Username prefix
     • Password
     • Headless mode (boolean: true/false)
   • Ensure the system does not block the event loop during user input.

2. Browser Automation Requirements
   For each email address:

   • Launch a browser with an optional headless mode.
   • Use a random user agent from an internal list.
   • Apply random delays between actions to mimic human behavior.
   • Open a new browser context for each attempt.
   • Automatically clear cookies after each attempt.
   • Handle navigation errors gracefully without crashing the system.

3. Free Proxy Support

   • Use only free public HTTP/HTTPS proxies.
   • Load proxies from the proxies.txt file.
   • Rotate proxies per account for each attempt.
   • If a proxy fails, retry with the next available proxy.
   • The system must still function without a proxy.

4. Bot Avoidance / Bypass Techniques

   • Implement random viewport sizes.
   • Simulate random typing speeds.
   • Generate random mouse movements (if supported).
   • Mask navigator.webdriver.
   • Utilize acceptable stealth techniques only.
   • Avoid illegal bypass methods or techniques that violate terms of service.

5. Account Creation Flow

   • The system must be modular to facilitate easy configuration for target websites.
   • The expected steps are:
     a. Navigate to the registration page.
     b. Fill in the email, username, and password fields.
     c. Submit the form.
     d. Detect and handle the success or failure of the registration.
     e. Extract any confirmation data if it is available.

6. File Output System Requirements
   On successful account creation:

   • Append the successful account details to the outputs/basarili_hesaplar.txt file.
   • Append only the username to the outputs/kullanici_adlari.txt file.
   • Append only the password to the outputs/sifreler.txt file.
   • Use the following format:
     phpCopy

     email:username:password

   On failed attempts:

   • Append the error details to the logs/error_log.txt file.
   • Use the following format:
     phpCopy

     ${timestamp} Email: X | Error: MESSAGE

7. Telegram Notification

   • If both TELEGRAM_TOKEN and CHAT_ID are set, send a message with the following format:
     phpCopy

     New Account Created:
     Email: X
     User: Y
     Time: Z

8. Real-Time Dashboard API

   • Create an Express server on port 3000.
   • Provide the following endpoints:
     • GET /stats: Return JSON data with the following fields:
       • total: Total number of attempts
       • success: Number of successful attempts
       • failed: Number of failed attempts
       • running: Number of currently running attempts
       • elapsedSeconds: Total duration in seconds
     • GET /logs: Return the last 100 log lines
   • The dashboard must update in real-time.

9. Final Console Report

   • After all email addresses have been processed, display a console.table with the following data:
     • Total Attempts
     • Successful Attempts
     • Failed Attempts
     • Success Rate (%)
     • Total Duration (seconds and minutes)

10. Error Handling

    • Wrap each account attempt within a try/catch block.
    • Ensure the system does not crash on a single failed attempt.
    • Continue processing the remaining email addresses.

11. Code Quality Requirements

    • Implement fully asynchronous code using async/await.
    • Adopt a modular architecture for easy maintenance and scalability.
    • Avoid global blocking to ensure efficient resource utilization.
    • Maintain a clean separation of concerns.

Project Structure:

project-root
  main.js
  gmailer.txt
  proxies.txt
  /outputs
    /basarili_hesaplar.txt
    /kullanici_adlari.txt
    /sifreler.txt
  /logs
    /error_log.txt
  /dashboard
    /index.js
    /public
    /views
  package.json

Output Requirements:

• Produce a complete runnable Node.js application.
• Include a package.json file with the necessary dependencies.
• Provide clear, step-by-step instructions for running the application.
• Do not include Docker or paid tools.
• Avoid any simulations, incomplete sections, or placeholder code.
• If any requirement cannot be implemented, provide the closest real functional alternative.
• Do not ask questions or generate explanations only; provide full, working code.

Important Notes:

• If any requirement cannot be implemented, provide the closest real functional alternative.
• Do not ask questions or generate explanations only; provide full, working code.