Eduardo San Martin Morote
Eduardo San Martin Morote
I realize I never closed this but it was completed a long while ago 😄
Thanks for looking into this, it's interesting. I did some digging and I think this requires something a bit more abstract than a new option `ignoreCacheChanges` but I'm not sure...
This is a small bug that reuses the body as options: https://github.com/posva/mande/blob/main/src/index.ts#L263-L266 An easy workaround is to pass an empty first argument `post('', { ... })`
If it always fail, what part of the API is exactly supported?
I think the version is fine. I guess the `undefined` value is not meant to be valid? 😅 . I'm not 100% sure but it doesn't seem to be covered...
> Node will (seems to, at least wrongly) choose the export of the web environment, FYI Node is picking up the correct export based on this package.json exports. **This is...
I'm in the process of planning time on VueFire with Firebase to work on needed features. Hopefully I will be able to allocate time for this in the following months
When running the executable of course. It compiled just fine
I'm seeing the same issue with ```vue ``` or ```vue ``` in prod only after `nuxt generate`. Everything works in dev mode. All queries return a 404, e.g. `/api/_content/query/0XF0tlkC88.1721293108801.json?_params={%22first%22:true,%22where%22:[{%22_path%22:%22/open-source/_for-individuals%22}],%22sort%22:[{%22_stem%22:1,%22$numeric%22:true}]}`. When...