Using different docx based libraries do not function well together.

[mayank1513]

The root cause is some sort of internal mapping when new nodes are craeted.

For example

new Documnet({
   sections: [
    children: {
       Object.assign({}, new Paragraph("some text"));
    }
  ]
})

Produced an invalid document.

[mayank1513]

More details here - https://stackoverflow.com/questions/79501040/why-is-docx-library-generating-invalid-doc-file-when-creating-a-different-copy-o

[mayank1513]

Possible solution - move relationship tracking logic to packer. Keep the rest of the classes free from relationship ids

[mayank1513]

To reproduce the exact issue check out this - https://github.com/tiny-md/mdast2docx/blob/8324415880de84638ed2a985949d33feb6067576/lib/src/section.ts#L106

[mayank1513]

@dolanmiu, any action plan for this? Can you help me understand how to fix this? It seems the compiler is heavily using the relationships created at the time of creating the elements, i.e., new Paragraph, new Run, etc.

Instead, if we could count/create fresh relationships at packer step, I could generate elements anywhere and add them to the document.