Even with inlineSourceMap and inlineSources in tsconfig.json debugging does not stop on breakpoint #4248
Replies: 3 comments
-
I also tried DevTools ("dev": "NODE_OPTIONS='--inspect' blitz dev"). $ curl http://localhost:3000 gives me a bunch of html, but nothing renders, again makes me think it is server side code that is broken. I tried Auto Attach Smart and All, no change there either. |
Beta Was this translation helpful? Give feedback.
-
No help here? |
Beta Was this translation helpful? Give feedback.
-
My fault in the end. I normally check the vibrancy of a community before I adopt the use of a project. I won't be recommending it to anyone anytime soon. |
Beta Was this translation helpful? Give feedback.
-
I am unable to debug my blitz app. The console gives nothing and the browser doesn't even have a response header. Completely opaque behaviour.
I use the following VS Code launch:
My tsconfig.json:
{
"compilerOptions": {
"target": "es5",
"lib": ["dom", "dom.iterable", "esnext"],
"baseUrl": ".",
"allowJs": true,
"skipLibCheck": true,
"strict": false,
"strictNullChecks": true,
"forceConsistentCasingInFileNames": true,
"noEmit": true,
"noUncheckedIndexedAccess": true,
"esModuleInterop": true,
"module": "esnext",
"moduleResolution": "node",
"resolveJsonModule": true,
"isolatedModules": true,
"jsx": "preserve",
"incremental": true,
"tsBuildInfoFile": ".tsbuildinfo",
"inlineSourceMap": true,
"inlineSources": true
},
"exclude": ["node_modules", "/*.e2e.ts", "cypress"],
"include": ["next-env.d.ts", "/.ts", "**/.tsx", "types", "./types.d.ts"]
}
I added a debugger statement in my index.tsx and tried browser debug. No luck. It makes me realise this must be server side code causing an issue? But how can it do that without at least something output to console?
Spent 3 days on this now, read everything I could find. I really need to progress, so will pull the plug and try streamlit next after another day of effort on this.
Beta Was this translation helpful? Give feedback.
All reactions