Running Bulletproof on a Next.js build produces an unexpected result

[alfonsograziano]

I created a simple Next.js application with a single page. The page is dynamic and contains an await of 1000ms before showing content to the user.

Expected Behavior

By running clinic doctor --autocannon [ / --method GET ] -- node ./node_modules/.bin/next start after the build, Doctor correctly recognize an issue in the cpu usage, suggesting to use Bulletproof to find the bottleneck.

Current Behavior

At this point, I try to run clinic bulletproof --autocannon [ / --method GET ] -- node ./node_modules/.bin/next start and the analysis produces this graph. I'm not sure if that's the expected result, but it is not very helpful in identifying potential issues. I'm not sure if Bulletproof is just not the best tool for performing this type of analysis on Next.js or if this is an actual bug in the graph generation. I'll investigate a little bit

Steps to Reproduce

1. Clone this repo
2. Build the appwith npm run build
3. Run clinic bulletproof --autocannon [ / --method GET ] -- node ./node_modules/.bin/next start

Environment

• Bulletproof version: v10.0.0
• Node.js version: v20.7.0