Fix: imports nodes/tags only when needed

[tcmhoang]

This is my initial attempt to address the tree-shaking issue. I've focused on minimizing changes in the codebase while ensuring functional parity. However, some adjustments need to be made in the test suite, I have not touched anything in that folder yet.

[TorstenDittmann]

Hehe, nice timing. I just finished my PoC :-D

I got something working too, however - the partials are super annoying. Because used nodes & tags are not part of the node AST. Means for each partial used, we need to walk down the tree recursively.

[TorstenDittmann]

I'll try and see to review this weekend 👍🏻

fyi, here is my poc #146 and I stopped when I realized the partials part.

[tcmhoang]

Good news 🎉. I think I've solved the issue with partials. The demo website works great now.

I noticed the changes in the PR #146 , using the extended type Schema & {...} to support alias import (Not sure how to call it in Typescript though 🤔). While it's interesting, I went with direct imports. That also solves these issues.

I think the direct import is safe, and it makes the implementation much more easier 😃

[TorstenDittmann]

Good news 🎉. I think I've solved the issue with partials. The demo website works great now.

I noticed the changes in the PR #146 , using the extended type Schema & {...} to support alias import (Not sure how to call it in Typescript though 🤔). While it's interesting, I went with direct imports. That also solves these issues.

I think the direct import is safe, and it makes the implementation much more easier 😃

direct imports also fix the issue with barrel files (https://vitejs.dev/guide/performance#avoid-barrel-files). I'll try and see if I can review it tomorrow :-)

[tcmhoang]

Hey @TorstenDittmann , I've updated the test suite. Everything should be passing now, but there are a couple of matrix environments where it's still failing. Would you mind taking a peek at those? . NVM, I've fixed it. It looks like a champ. Do you mind giving it a quick once over?