Nuxt•7mo ago

Repository patern backend & disadvantage backend in another directory

Hello, I was wondering if it is possible to inject a class instance in my backend. I would like to make the repository pattern and basically inject my class like we do in the frontend but in the backend. I could not figure out so if if anyone know, please tell me. Also, is there a disadvantage of moving the backend to another project using express or something at the place of using server directory?

4 Replies

xibman•7mo ago

You can with a nitro plugin Check this repo

xibman•7mo ago

https://github.com/enkot/nuxt-open-fetch/blob/main/src%2Fruntime%2Fnitro-plugin.ts

GitHub

nuxt-open-fetch/src/runtime/nitro-plugin.ts at main · enkot/nuxt-op...

Generate zero-overhead, typed OpenAPI clients for Nuxt. - enkot/nuxt-open-fetch

lavOP•7mo ago

I just need to do this: export default defineNitroPlugin((nitroApp) => { const clients = useRuntimeConfig().public.openFetch Object.entries(clients).forEach(([name, client]) => { // @ts-expect-error - This is a dynamic property nitroApp[$${name}] = createOpenFetch(client) }) }) ? nitroApp[give it a name] = myObj

Niza•7mo ago

For readability purposes

export default defineNitroPlugin((nitroApp) => {
  const clients = useRuntimeConfig().public.openFetch

  Object.entries(clients).forEach(([name, client]) => {
    // @ts-expect-error - This is a dynamic property
    nitroApp[$${name}] = createOpenFetch(client)
  })
})

export default defineNitroPlugin((nitroApp) => {
  const clients = useRuntimeConfig().public.openFetch

  Object.entries(clients).forEach(([name, client]) => {
    // @ts-expect-error - This is a dynamic property
    nitroApp[$${name}] = createOpenFetch(client)
  })
})

Gaming

Programming

Repository patern backend & disadvantage backend in another directory