tomwray13 / nestjs-nextjs-trpc Goto Github PK

One cool thing about the monorepo configuration is the possibility of importing things from the server to the web, for example.
In my case, I was reusing some types defined on server, and some of those types were enums. Perhaps enums need a special parse, and Next.js can't parse them correctly because they are being imported from outside the root of the project.

From my research, enabling experimental configuration externalDir on next.config.js fixes the problem. But I'm opening this issue because I am not sure what trade-offs this configuration can bring. Maybe @tomwray13 has a better understanding and can provide us a better alternative, if that shows necessary. Or perhaps he could add it to the tutorial about the monorepo (which is great by the way).

It is worth mentioning that you can always duplicate the enum inside your next project and don't mind about this problem.

Thanks in advance.

Trying to follow your tutorial and I'm getting the above error message. I'm new to both Next.js and Nest.js (primarily been an Angular programmer for years) as far as I can tell Next is working fine but Nest is having issues.
I'm sure it's something small and stupid but would really appreciate it if someone can point out what's wrong.

Unhandled Runtime Error
Error: Unexpected token 'I', "Internal S"... is not valid JSON

Call Stack
TRPCClientError.from
../node_modules/.pnpm/@[email protected]_@[email protected]/node_modules/@trpc/client/dist/TRPCClientError-0de4d231.mjs (37:15)
from
../node_modules/.pnpm/@[email protected]_@[email protected]/node_modules/@trpc/client/dist/httpUtils-0cb58db4.mjs (128:35)
process.processTicksAndRejections
node:internal/process/task_queues (95:5)

Hi. Is there a way to test tRPC routers on NestJS? I'm having a hard time making it work. I have some ideas but no luck so far.

The power of NestJS lies in the decorators. I'm surprised that no one has yet tried to wrap tRPC functionality into decorators and enable their use with a custom platform, along the lines of how Express or Fastify has been integrated. Is there a stopper not allowing to go this way?

I get this error when trying to run pnpm dev

apps/web dev: - error ..\node_modules\.pnpm\@[email protected]_@[email protected]\node_modules\@trpc\client\dist\transformResult-9a244fe7.mjs (13:15) @ TRPCClientError.from
apps/web dev: - error TRPCClientError: Failed to parse URL from undefined/trpc/hello?batch=1&input=%7B%220%22%3A%7B%7D%7D
apps/web dev: digest: "356000022"
apps/web dev: null

Hey, I was testing the repo after reding your article, but it seems that after your last commit, the nextjs part (localhost:3000) does not work (but it work with the commit before). Just let you know

i wanted to ask in the blog post :)

If I write a module for user login, in what folder should I add it and how do I go about planning the dependent modules?

As I seen from the docs of TRPC,

Just curious that, Why do you setup with Vanila Client approach on web setup instead of NextJS integration? Are they any reason on this?

Getting this error when run the dev.

First of all, thanks for this awesome example!

But in my NestJS app, I am using Fastify adapters and my attempt to use it along with tRPC didn't pan out well.

Could you please add some examples regarding that? Thanks in advance!