bill92 Posts - Answer Overflow

bill92

Explore posts from servers

KPCKevin Powell - Community TtRPC PPrisma

Posts Comments

TtRPC

•Created by bill92 on 10/12/2024 in #❓-help

Network tab returns array but data is undefined

4 replies

TtRPC

•Created by bill92 on 9/18/2024 in #❓-help

Infer query type of `data`

Using trpc version 11, how can I infer data?

const { isLoading, isError, error, data } =
    trpc.patient.list.useQuery();

<SomeComponent data={data} />

const { isLoading, isError, error, data } =
    trpc.patient.list.useQuery();

<SomeComponent data={data} />

Are there any utils on doing so? I've seen export type PatientData = inferRouterOutputs<ApiRouter>; but it doesn't work any help?

3 replies

TtRPC

•Created by bill92 on 5/24/2024 in #❓-help

conditional useQuery without input

How to use the enabled option for useQuery that doesn't has an input?

 const { isError, error } = trpc.iam.logout.useQuery(undefined, {
    enabled: isEnabled,
  });

 const { isError, error } = trpc.iam.logout.useQuery(undefined, {
    enabled: isEnabled,
  });

I'm passing undefined and TS is not complaining, only on runtime I get

app-index.js:33 Query data cannot be undefined. Please make sure to return a value other than undefined from your query function. Affected query key: [["iam","logout"],{"type":"query"}]

How to properly use this feature?

6 replies

PPrisma

•Created by bill92 on 5/22/2024 in #help-and-questions

`PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime` error

I'm having an error when trying to bundle my application with ts up

PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "darwin-arm64".

This is likely caused by a bundler that has not copied "libquery_engine-darwin-arm64.dylib.node" next to the resulting bundle.
Ensure that "libquery_engine-darwin-arm64.dylib.node" has been copied next to the bundle or in "packages/api/dist".

We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation

PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "darwin-arm64".

This is likely caused by a bundler that has not copied "libquery_engine-darwin-arm64.dylib.node" next to the resulting bundle.
Ensure that "libquery_engine-darwin-arm64.dylib.node" has been copied next to the bundle or in "packages/api/dist".

We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation

7 replies

TtRPC

•Created by bill92 on 5/9/2024 in #❓-help

Error calling middleware

I'm getting an error trying to test out some pretty basic middleware. This is my code

export const createContext = ({
  req,
  res,
}: trpcExpress.CreateExpressContextOptions) => ({ prisma, res, req });

const t = initTRPC.context<Context>().create();

export const router = t.router;
export const procedure = t.procedure;

export const middleware = procedure.use(async (opts) => {
  console.log('middleware');
  return opts.next(opts);
});

export const authRouter = router({
  me: middleware.query(async ({ ctx }) => {
    console.log(ctx.req.headers.cookie);
    return { success: true };
  }),
});

export const createContext = ({
  req,
  res,
}: trpcExpress.CreateExpressContextOptions) => ({ prisma, res, req });

const t = initTRPC.context<Context>().create();

export const router = t.router;
export const procedure = t.procedure;

export const middleware = procedure.use(async (opts) => {
  console.log('middleware');
  return opts.next(opts);
});

export const authRouter = router({
  me: middleware.query(async ({ ctx }) => {
    console.log(ctx.req.headers.cookie);
    return { success: true };
  }),
});

Getting TypeError: Cannot read properties of undefined (reading 'use') I'm following the documentation [https://trpc.io/docs/server/middlewares] and I'm using @trpc/server@next

3 replies

PPrisma

•Created by bill92 on 4/7/2024 in #help-and-questions

Monorepo setup: Prisma with NestJS

I currently have a postgres database that uses row level security. This database is used by two services that are built with NestJS. - auth service - core service In order to interact correctly with the database and RLS, I need to use these two services with a different database account so that it can bypass RLS. (auth service needs to bypass) Here is where the monorepo setup comes to play, I want to implement a monorepo with 4 packages: - db (prisma) - auth service (nestjs) - core service (nestjs) - web (next js app) The idea is that both auth and core can connect to the same database using a different username, I was thinking on passing a different DATABASE_URL when starting the service. Has anyone done this approach or can share how to do so? I did not find anything on the documentation and would like a but of guidance please

1 replies

Gaming

Programming