Adapt caching system fs so that NotionCMS works client side

[earlAchromatic]

This is basically the only thing blocking from client side usage. Might also be nice to allow for setting a remote cache.

Curious what good client side use cases look like though.

[earlAchromatic]

We now use indirect eval in the cache deserializer (for handling serialized functions) so we should force disable this on the client for security. Really, we should just force off the entire caching system as its not useful on the client.

[earlAchromatic]

We also are now using some node deps that will need some isomorphic treatment.

[earlAchromatic]

Client side support is now out of scope for this project.

[earlAchromatic]

I did think of re-opening this as I'm considering making ncms function inside of a worker. I can see some benefit to launching your app initially (no prerender) and pulling in a bunch of data from Notion - maybe they aren't pages, Notion db would be a base for your collections.

[earlAchromatic]

This may be the path forward as it has drivers that you could use to support just about any environment:

https://unjs.io/unstorage