Ordered lists split up after 10th item

[brianzaubar]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and discussions and couldn’t find anything (or linked relevant results below)

Affected package

2.0.2

Steps to reproduce

We are running a web-server with nuxt.js and vue.js.
My example list:

1. **Header 1**
   - header 1 item 1
   - header 1 item 2
2. **Header 2**
   - header 2 item 1
   - header 2 item 2
3. **Header 3**
   - header 3 item 1
   - header 3 item 2
4. **Header 4**
   - header 4 item 1
   - header 4 item 2
5. **Header 5**
   - header 5 item 1
   - header 5 item 2
6. **Header 6**
   - header 6 item 1
   - header 6 item 2
7. **Header 7**
   - header 7 item 1
   - header 7 item 2
8. **Header 8**
   - header 8 item 1
   - header 8 item 2
9. **Header 9**
   - header 9 item 1
   - header 9 item 2
10. **Header 10**
   - header 10 item 1
   - header 10 item 2
11. **Header 11**
   - header 11 item 1
   - header 11 item 2

Actual behavior

Ordered lists always break up after the 10th items. Meaning the ast tree will have several items of type "list" as siblings even though they belong to one list.
Here you can see too many entries:

Expected behavior

This behaviour does not happen in unordered lists. I expect the ordered list to be one item and not several after the 10th item.

Runtime

node@20.16.0, Chrome 134.0.6998.166

Package manager

bun@1.1.29, npm@10.8.1

Operating system

macOS Sequoia 15.3.2

Build and bundle tools

other (please specify in steps to reproduce)

[remcohaszing]

This is expected behaviour. It happens on GitHub too.

1. Header 1
   • header 1 item 1
   • header 1 item 2
2. Header 2
   • header 2 item 1
   • header 2 item 2
3. Header 3
   • header 3 item 1
   • header 3 item 2
4. Header 4
   • header 4 item 1
   • header 4 item 2
5. Header 5
   • header 5 item 1
   • header 5 item 2
6. Header 6
   • header 6 item 1
   • header 6 item 2
7. Header 7
   • header 7 item 1
   • header 7 item 2
8. Header 8
   • header 8 item 1
   • header 8 item 2
9. Header 9
   • header 9 item 1
   • header 9 item 2
10. Header 10

• header 10 item 1
• header 10 item 2

11. Header 11

• header 11 item 1
• header 11 item 2

You need to properly indent list items:

1. **Header 1**
   - header 1 item 1
   - header 1 item 2
2. **Header 2**
   - header 2 item 1
   - header 2 item 2
3. **Header 3**
   - header 3 item 1
   - header 3 item 2
4. **Header 4**
   - header 4 item 1
   - header 4 item 2
5. **Header 5**
   - header 5 item 1
   - header 5 item 2
6. **Header 6**
   - header 6 item 1
   - header 6 item 2
7. **Header 7**
   - header 7 item 1
   - header 7 item 2
8. **Header 8**
   - header 8 item 1
   - header 8 item 2
9. **Header 9**
   - header 9 item 1
   - header 9 item 2
10. **Header 10**
    - header 10 item 1
    - header 10 item 2
11. **Header 11**
    - header 11 item 1
    - header 11 item 2

1. Header 1
   • header 1 item 1
   • header 1 item 2
2. Header 2
   • header 2 item 1
   • header 2 item 2
3. Header 3
   • header 3 item 1
   • header 3 item 2
4. Header 4
   • header 4 item 1
   • header 4 item 2
5. Header 5
   • header 5 item 1
   • header 5 item 2
6. Header 6
   • header 6 item 1
   • header 6 item 2
7. Header 7
   • header 7 item 1
   • header 7 item 2
8. Header 8
   • header 8 item 1
   • header 8 item 2
9. Header 9
   • header 9 item 1
   • header 9 item 2
10. Header 10
    • header 10 item 1
    • header 10 item 2
11. Header 11
    • header 11 item 1
    • header 11 item 2

[github-actions]

Hi! This was closed. Team: If this was fixed, please add phase/solved. Otherwise, please add one of the no/* labels.

[github-actions]

Hi! Thanks for reaching out! Because we treat issues as our backlog, we close issues that are questions since they don’t represent a task to be completed.

See our support docs for how and where to ask questions.

Thanks,
— bb

[brianzaubar]

Ah alright. Okay thanks. Interesting behaviour.

[liangxiwei]

you know, some markdown text is generated by AI. And the markdown is not always standard. If we do not adapt it, it will alway has bug.

[JounQin]

It's AI's bug, not here. Markdown has a standard spec: commonmark.

[ChristianMurphy]

Markdown has a standard.

Train your AI.

Use LLM guidance like https://github.com/guidance-ai/guidance, https://github.com/outlines-dev/outlines, https://github.com/stanfordnlp/dspy, https://github.com/eth-sri/lmql, https://github.com/instructor-ai/instructor, and many others. Which can ensure the model generates valid markdown.