best way to implement /register and /login
Custom API (Laravel) with Nuxt
Reactive Headless Data Models in Nuxt
mask errors on nitro/server api endpoints
error.vue
for non-accept: application/json
requests, but anything that's json, it still renders the entire error.
in either case, I'm not sure if either work as expected, as I suspect both send the actual error back to the client. however, what if the error contains potentially sensitive data? how are you supposed to mask that so it sends a generic error back, not the actual, full, potentially sensitive error body back? do I have to mask any random potential calls on the server side, hoping I've captured each potential place that might throw errors?...Can I redirect in a server plugin?
Invalid props not being reported by TypeScript
@nuxt/ui
from v2 to v3.. but I was not been as easy as I expected.
I don't know if this is a thing with vue, nuxt or @nuxt/ui
but I'm not getting errors from invalid props. In v2 for example I had this code:...
supabase nuxt confirm page on email confirmation
Nuxt UI custom colors
i'd like to see a perfect example on how to add a custom variant to a button please
Issues Deploying Nuxt Application on o2switch with SSR and drizzle-kit Migrations
multiple modals how to be more efficient loading them
random no response errors on usefetch.
<no response> Failed to fetch
but the connection is OK and server is online. as the error logging also goes in a usefetch post and arrives to the backend fine? when people open a new window in their browser the issue is no longer there. so its very random. how could i diagnose this as i cannot reproduce it on my system? it also is not as descriptive as i would like making diagnosing the issue way harder. anyone with any advice on fixing such issues?
it happens on the following post request:
```...vitest not working with imports form '#app'
Nuxt2 displays wrong meta tags when the page is deleted
Nuxt UI 3 Dynamic Icons
Supabase server side login setup
Apollo | graphql | proxy
localhost:3000/graphql
to localhost:1337/graphql
.
How to correctly proxy, so user will not see backend. User must see that graphql request is going to localhost:3000/graphql
, but in reality these request should proxy to localhost:1337/graphql
```js...link checker exclude links