Skip to content

Export src/utils.ts in @orpc/nest as @orpc/nest/utils #1311

@longnguyen2004

Description

@longnguyen2004

Describe the feature

Currently, import { populateContractRouterPaths } from "@orpc/nest" is pulling in both implement.ts and utils.ts through index.ts. However, implement.ts contains imports from @nestjs/common, which get pulled in along the way. When importing the contract into the frontend, those imports leak into the frontend, causing errors such as process is not defined.

I propose splitting off utils.ts into a separate export, such as @orpc/nest/utils, so that NestJS imports don't get leaked into the frontend.

(yes I know I can just declare all the paths, but this is still a real problem)

Additional information

  • Would you be willing to help implement this feature?

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions