Is it possible to keep type safety in ElysiaJS when using seperate route files, espcially when using plugins(JWT)?

[heinergiehl]

Hi Guys, I wonder whether there is an elegant inbuilt solution to guarantee typesafety when using plugins like @elysiajs/jwt
Please see my current stackOverflow post:
https://stackoverflow.com/questions/79494287/is-it-possible-to-keep-type-safety-in-elysiajs-when-using-seperate-route-files
Thank you so much <3

[kravetsone]

Please just follow best-practice

there no real cases im useless separating which break type safety and force u to do a much more work

[heinergiehl]

You mean, I should not use too many files, but rather have it in one file, so I can profit from type safety?

[mtt-artis]

👋

You need to add jwt on every Elysia instance where jwt is need for type inference, Elysia will handle the deduplication for you.
https://elysiajs.com/essential/plugin#plugin-deduplication

// jwt.ts
export const jwtConfig = jwt({
  name: "jwt",
  secret: "Fischl von Luftschloss Narfidort",
})

// File1.ts
import { jwtConfig } from "./jwt.ts";

new Elysia()
  .use(jwtConfig)
  .get()
  .post();

// File2.ts
import { jwtConfig } from "./jwt.ts";

new Elysia()
  .use(jwtConfig)
  .get()
  .post();

[heinergiehl]

Thanks for the answer, MrSir. Is this considered best best practice?
Hmmm, when using a jwtConfig object, I get an error:

Although I have in my index.ts:

[heinergiehl]

ah, got it working by putting

in an other file than index.ts