Matt Kane
Matt Kane
Can the URLs be manually constructed? Unpic needs the transformer to be a pure, synchronous function with no side effects, so it can't call APIs.
OK, great. If anyone wants to contribute it they should do so against the [new syntax branch](https://github.com/ascorbic/unpic/pull/133) which includes uopdated instrucitons on contributing them. It looks like a relatively simple...
I agree! Adding it to the Loader API page would work best.
I think it would make sense to make `@astrojs/markdown-remark` a public API, but we'd need to discuss it.
I don't think adding it to context is the right approach, because markdown is just one of the formats that it supports. It's better to explicitly choose the renderer that...
This is your answer 😁 https://app.netlify.com/sites/euphonious-swan-75085e/deploys/63bd91ffe5d0c10009779bc0#L227
Yeah, that has to be a bug. I wonder if dev is looking in the wrong publish dir
Some suggestions from the API bash: - `session.flash()`: save something to the session just for the next request - TTL in session metadata, and a `session.gc()` to clean old entries...
@bkyerv no, I hadn't though of that. I'm not sure of the threat model though. It's never exposed to the client, so I'm not sure where it could be tampered...
@wildfiremedia this doesn't seem to be an option in the unstorage fs driver. It might be worth contributing, or at least making a feature request. It supports an in-memory LRU...