Related issue: markdown-it/markdown-it#1082

The error:

The error:

I was able to resolve the issue on my end by removing --turbo
I am using NextJs 15 with Turbo.

You may also want to downgrade markdown-it to [email protected]

The error:

I was able to resolve the issue on my end by removing --turbo I am using NextJs 15 with Turbo.

You may also want to downgrade markdown-it to [email protected]

Yes but, how can I use the latest markdown-it WITH turbo?

Dug into this and found a minimal reproduction:

// app/assert.js
export function assert(a, b) {
  if (a !== b) {
    throw new Error(`Assertion failed: ${a} !== ${b}`);
  }
}

// app/page.js
import { assert } from "./assert";

const ch = 0x10;

function test() {
  for (;;) {
    // found valid marker
    if (ch === 0x29 /* ) */ || ch === 0x2e /* . */) {
      break;
    }

    return -1;
  }

  if (1 < 2) {
    if (!assert(1, 1)) {
      // " 1.test " - is not a list item
      return -1;
    }
  }
  return pos;
}

export default function Page() {
  return <h1>{test()}</h1>;
}

It's very similar to this issue: #77083

My current thinking is that the analysis seems to detect a case where return would be unconditional so the rest would be dead code, however it's not considering break that would break out of the loop or block, causing it to not replace the import for the helper.