ScaffoldHub
  • Introduction
  • Modeling
  • Setup
    • NextJS
    • File Storage
    • Payments with Stripe
  • Debugging
  • End-to-end and Unit Tests
  • Deployment
    • Deploy to Vercel
  • Features
    • Projects
    • Preview
    • Tenants
    • Subscriptions and Payments
    • Security
    • File Storage
    • Authentication
      • Sign-in and Sign-up and Social Sign-in
      • Invitation
      • Password Reset
      • Password Change
      • Email Verification
    • Entity
      • Form
      • Filter and List
      • Export
      • Import
    • Audit Logs
    • Internationalization (I18n)
    • API Keys
    • API Documentation
  • Package.json
  • Support
  • Changelog
    • Documentation
    • Scaffolds
  • Custom Development
  • Legacy Scaffolds
  • Go to ScaffoldHub
Powered by GitBook
On this page
  • Frontend
  • Backend

Debugging

PreviousPayments with StripeNextEnd-to-end and Unit Tests

Last updated 1 year ago

Frontend

The easiest way to debug the frontend is by using .

On the frontend code, place adebugger where you want the code to stop.

When the application reaches some debugger, it will stop and you can inspect the application state at that point.

Backend

  1. Click on the Debugger tab (left).

  2. Launch the Program.

  3. Open the Debug Console tab (bottom).

Now that the application is running, you can place a debugger anywhere on the backend code and it will stop when it reaches the breakpoint so you can insect the application state.

Make sure your project path doesn't contain spaces. For some reason, VSCode started crashing the debug process when the project path contains spaces like /path/to/project with spaces. Instead use /path/to/projectwithoutspaces.

More about VSCode debugging:

Then on Google Chrome, open the .

To debug the backend, you must use the .

Google DevTools
VSCode editor
Google DevTools
https://code.visualstudio.com/docs/editor/debuggingcode.visualstudio.com