body type is always unknown despite validation

[JohnRoseDev]

What version of Elysia is running?

1.2.25

What platform is your computer?

Darwin 22.5.0 x86_64 i386

What steps can reproduce the bug?

Define a route with a body validation config:

export const app = new Elysia()
  .post('/do_something', async ({ body }) => {

  }, {
    body: t.Object({
      foo: t.Integer(),
      bar: t.Integer(),
    }),
  })

What is the expected behavior?

The body object from the context parameter should be typed as { foo: number, bar: number }.

What do you see instead?

The body object from the context parameter is typed as unknown.

Additional information

This started happening some months ago and I was under the impression that eventually, upgrading Elysia each time there's a new version would fix this but it's still happening. I assume something in my tsconfig might be off but I've been using this same tsconfig since the beginning of my Elysia project and this problem was not there initially.

bun version:
1.2.4

"bun-types": "1.2.4"

tsconfig:

{
  "compilerOptions": {
    "lib": ["ESNext"],
    "module": "esnext",
    "target": "esnext",
    "moduleResolution": "node",
    "noEmit": true,
    "esModuleInterop": true,
    "downlevelIteration": true,
    "skipLibCheck": true,
    "allowSyntheticDefaultImports": true,
    "forceConsistentCasingInFileNames": true,
    "allowJs": true,
    "preserveSymlinks": true,
    "strictNullChecks": true,
    "types": ["bun-types"],
  }
}

Have you try removing the node_modules and bun.lockb and try again yet?

Yes

[hisamafahri]

Is this also happening when you create a new elysia app (bun create elysia app) too?

I cannot reproduce your issue sadly.

---

And juuuust wanna make sure (I assume you've done it correctly), you import the t from elysia, right? 😅

import Elysia, { t } from "elysia";

[usumic]

I ran into the same issue. Checking dependencies and versions of elysia within them solved it for me. I guess there was also some mismatch of the version of @sinclair/typebox. Maybe this could help you.

[JohnRoseDev]

Thanks for the replies.

Is this also happening when you create a new elysia app (bun create elysia app) too?

Yes, just tested.

And juuuust wanna make sure (I assume you've done it correctly), you import the t from elysia, right? 😅

Yes, t is imported from Elysia.

I guess then it must be related to my IDE or local TS version, which my ide says is at 5.1.3.

Still strange that is used to work just fine until some months ago. I just tried downgrading Elysia to 0.7.0 in this test project created by bun create elysia app, and this fixes the problem, body is now correctly typed. So it seems to be an unfortunate combination of my local ide setup together with some supposed change that happened in Elysia along the way from 0.7.0 towards 1.2.5.

I ran into the same issue. Checking dependencies and versions of elysia within them solved it for me. I guess there was also some mismatch of the version of @sinclair/typebox. Maybe this could help you.

Hm, the only relevant dependencies I have that could have an effect are Elysia and bun-types as well as my bun version, do you mean any other packages?

[fearandesire]

I'm suddenly having the same issue as well, when I wasn't within the past few days. Not sure what's changed or what I did, unfortunately.

[usumic]

@JohnRoseDev In my project I used some other of our modules which also uses elysia. So I've run into issues where these dependencies to elysia weren't the same. The time I replied there was also a change for the patch version of typebox (seen in bun.lock; not a direct dependency of our project). But I still don't know which fixed it in the end.

My steps were:

• removing node_modules and bun.lock
• starting without elysia and adding dependencies one by one to find the "faulty" one
  It seemed like the "right order" solved it here, a bit weird.

I've also searched for other issues during that day and stumbled upon #777 . But I've seen that you already use this setting.

Btw I use TS 5.8.2 and the generated tsconfig of bun.

[fearandesire]

@JohnRoseDev In my project I used some other of our modules which also uses elysia. So I've run into issues where these dependencies to elysia weren't the same. The time I replied there was also a change for the patch version of typebox (seen in bun.lock; not a direct dependency of our project). But I still don't know which fixed it in the end.

My steps were:

* removing node_modules and bun.lock

* starting without elysia and adding dependencies one by one to find the "faulty" one 
  It seemed like the "right order" solved it here, a bit weird.

I've also searched for other issues during that day and stumbled upon #777 . But I've seen that you already use this setting.

Btw I use TS 5.8.2 and the generated tsconfig of bun.

I've tried what you suggested and in other issues and haven't been able to fix it. It's really weird.

To list what I've tried:

• removed bun.lock, node_modules
• reinstalled with bun i
• bun pm cache clean
• tried different IDEs
• various typescript versions:
  • 5.8
  • 5.9.0 (via @next)
  • 5.5.3
• downgraded to Elysia prior version
• tried removing extreneous deps, building with tsc per-dep i installed, but this failed as long as elysia was installed
• override typebox to specific version
• tsconfig with different setups - from example repos, what others listed in other issues, etc
• upgraded bun to latest version
• verified I'm importing as import Elysia, { t } from 'elysia'
• even removed typescript globally, reinstalled

I can't for the life of me figure out why this doesn't work suddenly.
I'm new to Elysia and it's just a bit disappointing this suddenly happened, as I've enjoyed the experience so far.

And for more context, my IDE does type the body properly just fine on-hover. I can see what I've defined as the schemas, but tsc just won't build them.

[Chrysochrome]

This issue is quite strange. When I exclude the src folder in my tsconfig, the type inference in VSCode returns to normal. However, if I remove the exclude option, the type becomes unknown, and the TypeScript compiler also indicates that it is unknown during the build process.

[fearandesire]

I've fixed it for myself, and I have no idea how 😅

[Xu-pixel]

I encountered the same problem, and I solved it by adding "strict": true in the compilerOptions of tsconfig.

[ratthapolsk]

Solution: Fixing "Unknown" Parameter with Model Validation Issue in Elysia

After some investigation and a workaround, I was able to resolve this issue.

Problem: "Unknown" Parameter Despite Defining the Model in Route

While working in VS Code, I encountered an issue where the route parameter was showing as unknown, even though I had properly declared the model.

VS Code Editor:

No matter what I tried, I couldn’t get it to recognize the correct type. However, when I switched to the latest version of Cursor Editor, I found that it correctly inferred the type.

Cursor Editor:

Root Cause: Outdated VS Code and TypeScript Version

After further analysis, I checked the versions of both VS Code and the built-in TypeScript version that ships with it. I realized that my VS Code version was outdated:

Version: 1.85.1 (user setup)
Commit: 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2
Date: 2023-12-13T09:49:37.021Z
Electron: 25.9.7
ElectronBuildId: 25551756
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.26100

Since I was using Windows, I updated VS Code using the following command:

winget upgrade --id Microsoft.VisualStudioCode

After updating, I verified the installed TypeScript version within VS Code:

• Press Ctrl + Shift + P

• Search for "Select TypeScript Version"

Updated TypeScript Version:

With the latest VS Code and TypeScript, I checked my index.ts file again—and finally, the parameter types were correctly inferred! 🎉🎉

Fixed Type Definition in index.ts:

Conclusion

If you're facing the same issue, try updating your VS Code and TypeScript version. That should resolve the problem!

Good luck! 😁

[ppenter]

I fixed by strict: true.

[incpo]

That is also caused by "strictNullChecks": false in tsconfig.json, so make sure it is set to true.

[mmatila]

Upgrading to latest Typescript version which in my case happened to be typescript@5.8.3 fixed it for me!