Fix context helper file generation

[Beachman4]

Right now, the example in the documentation does not work because the types export was removed from the package.json and even if that is added back, the generation of the helper file is being done in the generators folder because of __dirname

fixes #54, fixes #21

[vercel]

@Beachman4 is attempting to deploy a commit to the Kevin's Projects Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nestjs-trpc-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 29, 2024 10:55pm

[KevinEdry]

Oh this is awesome! does it really fix the types generation?

[Beachman4]

Oh this is awesome! does it really fix the types generation?

Yes it should make it work according to the docs, but I think the context generation should be expanded to allow you to specify the placement so you can check it into version control. Right now, since it's in node_modules, when you use this type in your repo and you have a fresh node_modules, then typecheck will break, thus not allowing the context to be generated.

Alternatively, perhaps adding a bin to this package & adding a generate command, similar to prisma, as prisma follows a similar pattern with generated files being placed in node_modules.

[ctrhub]

Hey, thinks for this PR.

In addition to this:

but I think the context generation should be expanded to allow you to specify the placement so you can check it into version control.

I am also wondering how this will work with a monorepo(turborepo) where 2 or more apps are using the nestjs-trpc package. In a monorepo you only have one node_modules in the root folder. This means there will only be one nestjs-trpc package that will be used by multiple apps. Will this cause conflicts in type generation?

[guotingchao]

Can this commit be released? The latest version still cannot import Context.

[emptyengineering]

Hey, thinks for this PR.

In addition to this:

but I think the context generation should be expanded to allow you to specify the placement so you can check it into version control.

I am also wondering how this will work with a monorepo(turborepo) where 2 or more apps are using the nestjs-trpc package. In a monorepo you only have one node_modules in the root folder. This means there will only be one nestjs-trpc package that will be used by multiple apps. Will this cause conflicts in type generation?

This is also how I am using it, curious as well.

[arturbacilla]

@KevinEdry Can you please release this PR? 7 months since its creation...

[Vitals9367]

Hey, please merge this. I really want to use context in my setup!