Interesting? ๐ค
According to my history, the project started at:
"@solidjs/meta": "^0.29.4",
"@solidjs/router": "^0.15.0",
"@solidjs/start": "^1.0.10",
"solid-js": "^1.9.3",
We originally were using pnPm but migrated to Deno in the past few months. This is the first time we have ever used the .with function out of the entire history.
I do know there is some weird HMR issues I have started seeing with certain routes once I moved to a Merkle DAG design. Especially once I started reusing query.
So, if a page is deep in the Merkle graph, the more query is (re)used. Only on these deep graph pages does the HMR weird stuff happened.
This is also what I mentioned in the IndexDB thread. I'm working on a re-design that will hopefully consolidate the query. However, I'm starting to wonder if there is an eventual "overload" on the system in cases like this?
For example, this is a realistic scenario:
- Root parent calls
queryMerkleBlob to get root file content
- Child Layout calls
queryMerkleBlob to get root file content (for nav stuff)
- Child calls
queryMerkleBlob to get file content
- Child of Child calls
queryMerkleBlob to get data content from file definition
๐ This page with the form is lower down the graph which means this is happening in the query Map chain