Jacky Zhao
Jacky Zhao
you could use memoization here for the mapping of directory to rss feed and only compute if it hasnt already been computed (i think we shouldnt need recursion here)
First problem is because we don't do dependency tracing in the emit step. Emitters take in an array of content so on rebuild it re-emits everything. @MoskalenkoDev this shouldn't happen...
Can you re-record that while running it in verbose mode? `npx quartz build --serve --verbose`, this should help us figure out what its getting stuck on
What type of disk do you have? This shouldn't happen on modern SSDs. The bottleneck here isn't the processing speed, it's likely something to do with your underlying disk IO....
I also have a ~2 year old laptop and don't have the same problems on a much larger vault 🤷 (this trace is from editing the same file over and...
You can try upgrading your Node version, that has helped my performance in the past
I've thought about the initial issue a bit more, here are my intermediate notes. Dumping it here for tracking context but I likely won't have time to make a change...
imo shouldn't need this feature/would hold off until we have the loading skeleton, what HTML file is big enough this is a concern?
?? 3mb is like all of shakespeares works what do you have in there that should be git ignored anyways
@aarnphm this is an actual bug as we kinda do assume that components are singletons and maybe we should revisit that assumption?