ScaffoldHub - v2
  • Introduction
  • Modeling
    • Two-way Relationships
  • Setup
    • Backend
    • Frontend
    • File Storage
    • Emails with SendGrid
    • Payments with Stripe
  • Debugging
  • Deployment
    • Database
      • SQL
      • MongoDB
    • Backend
      • Google Cloud - App Engine
      • Google Cloud - Run
      • Under construction...
    • Frontend
      • Firebase Hosting
      • Heroku w/ Subdomains
      • Under construction...
  • Features
    • Projects
    • Preview
    • Tenants
      • Single-Tenant
      • Multi-Tenant
      • Multi-Tenant (w/ subdomains)
    • Payments
    • Security
    • Authentication
      • Sign-in and Sign-up
      • Invitation
      • Password Reset
      • Password Change
      • Email Verification
    • Audit Logs
    • Settings
    • Internationalization (I18n)
    • Entity
      • Form
      • Filter and List
      • Export
      • Import
    • API Documentation
  • Architecture
    • Security
    • File Storage
    • Internationalization (I18n)
    • Payments
    • Typescript Support
    • Rate limiting
    • Technologies Versions
    • Under construction...
  • Recipes
    • Testing the API with Postman
    • Enterprise sign-in with WorkOS
    • Under construction...
  • Support
  • Changelog
    • Documentation
    • Scaffolds
  • Custom Development
  • Legacy Scaffolds
  • Go to ScaffoldHub
Powered by GitBook
On this page
  • Frontend
  • Backend

Was this helpful?

Debugging

PreviousPayments with StripeNextDeployment

Last updated 3 years ago

Was this helpful?

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

ScaffoldHub has already the VSCode debugging configurations settings in place, you just need to open VSCode inside the backend folder. You will know that you opened it correctly if the toolbar is pink.

  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