feat: Export public interfaces of Node, File and Folder

[susnux]

I would like to discuss this issue:

If you using those classes in Vue (e.g. in data) they will cause errors, as Vue unrefs data deeply and this causes all private fields to be stripped off from the interface. Passing one of those classes from data to a function that expects e.g. Node will then cause a Typescript error because the passed value is lacking the private fields.

So instead this provides interfaces that can be used whenever a parameter should be of one of those types.

Example of one of those errors:

---

Alternative: Cast them every time you use them, like

data() {
  return { content: [] as Node[] }
},
methods: {
  handleConflicts() {
    getConflicts(nodes, this.content as Node[])
  },
},

[codecov]

Bundle Report

Bundle size has no change ✅

[ShGKme]

If you using those classes in Vue (e.g. in data) they will cause errors

Do we need to store them as deep reactive objects?

[ShGKme]

In Vue classes instances (except data classes) aren't usually used in reactive data.

• Technically - incompatibility with reactivity mechanisms
• By Vue concept - data storing and data management should be separated

IMO, if we don't consider these object Vue-related entities, we should only work with them as non-reactive, marking raw if needed.

Then, if they are mutable and we need to react on the mutation (e.g. attributes or _data change), we need to either make them reactive initially (by making them Vue-related) or provide a way to handle changes with a wrapper/subscribers.

That's why I asked if we need them to be reactive if we are using them as mutable objects in server/apps.

[susnux]

Well mostly I would say no we do not need the node to be reactive but only the wrapping array.
So a shallowRef or shallowReactive would be good enough, though I do not know if you can use them in Options API without setup?

[ShGKme]

toRaw must work in data in Vue 3, and we can emulate it by adding something like __v_RAW to these classes initially, but I never tested it in Vue 2.

[ShGKme]

Adding __v_skip: true for both Vue 2 and Vue 3 to these classes will remove them from being observed/mutated/reactive anywhere in Vue

[susnux]

I adjusted the dialogs file picker as a first step by using shallowRef and shallowReactive which should be good enough.

[ShGKme]

I think, this PR may still make sense to use, where we don't need an actual Node/File instance