Uploadthing onUploadAborted not working?
I was wondering why I got an error when trying to use
onUploadAborted inside my useUploadThing hook
it says it doesnt exist
tried to fix it but couldnt, my uploadthing is also up to date...Solution:
i had this same issue. you can read below this message to see what conversation took place: https://discord.com/channels/966627436387266600/1102510616326967306/1351067059844546561
the summary is that this
onUploadAborted function isn't exposed in the hook. the docs havn't been updated it seems like.
you have 2 solutions: ...
Issue with missing-suspense-with-csr-bailout error while upgrading to Next 15
I'm upgrading my project to Next 15, ran the codemod and fix a few errors.
Right now I'm stuck with this missing-suspense-with-csr-bailout error where you don't wrap a component that use useSearchParams in a Suspense tag.
Previously we used the missingSuspenseWithCSRBailout: false, flag to go pass it in the build but looks like it's no longer working for v15
Anyways I followed the error messages from the vercel dashboard and add a Suspense wrapper on the first client component in the tree but for some reason it's still have the same error on that route and sometimes even errors on other routes that doesn't have that error in previous builds
Am I even on the right track? Do I need to find every useSearchParams implementation on every component and custom hooks? Are we living in a simulation? Help please 😭...
T3 Env bundles ALL (even server) envs in build output (Next.js 15)
When using t3 env package in Next.js it seems that it loads everything (partially) into my
main-app-[random-hash].js (build output from webpack)
The actual value of the server envs are not bundled but the name of the env is. This poses a security risk because now you can see what packages I use on the server to maybe find an exploit.
Is this something I'm doing wrong or is it a bug in the package itself?...Solution:
There’s a big callout here https://env.t3.gg/docs/core#create-your-schema
Passing Cookies / Authentication For QStash
Summery:
Adding cookies / authentication in my qstash schedule as the API route is protected
Note: Everything works fine locally when i use postman for api testing.
QStash does hit the endpoint correctly in prod / testing locally...
Solution:
the solution was using this header
NPM Error when Upgrading from 7.4.1 to 7.7.2 (NextJS14)
Howdy fellow coders. I went to update an app Ive been finalizing for someone, which worked perfectly fine before today as far as building goes - It had said something about the url callback that is now .ufsUrl had been deprecated - still worked though.
today I got this type error: Property 'ufsUrl' does not exist on type 'ClientUploadedFileData<{ uploadedBy: string; }>'. when trying to push what wrre supposed to be just UI/information changes,
so I tried to update the @uploadthing package to the current recommended version, and theres a broken dependency stream.
...
Expo + Express on the backend | (maybeServerData ?? data)?.find is not a function
I cant seem to get uploadthing working when using express as a backend with expo. There is a lot of documentation when using expo + expo api routes, but when using express, its lacking and also causes an error that i cant seem to resolve
```
Uncaught Error...
