-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TS2353: Object literal may only specify known properties, and 'multiple' does not exist in type Field #1698
Comments
@falk-stefan |
@jackey8616 thank you for the hint! Unfortunately, I am now getting a bunch of errors relating to annotations:
This is what my {
"compilerOptions": {
"target": "es2022",
"module": "NodeNext",
"moduleResolution": "NodeNext",
"rootDir": "./src",
"sourceMap": true,
"outDir": "./dist",
"esModuleInterop": true,
"forceConsistentCasingInFileNames": true,
"strict": true,
"noImplicitAny": false,
"skipLibCheck": true,
"allowJs": true,
"checkJs": false,
"experimentalDecorators": true
},
"include": [
"src/**/*.ts",
"src/**/*.js"
],
"exclude": [
"node_modules"
]
} I tried to play arround by setting "emitDecoratorMetadata": true,
"experimentalDecorators": true but none of the settings would work. |
@falk-stefan |
@jackey8616 thank you 👍 |
@falk-stefan |
@jackey8616 I gave it a quick test. Looks good so far. I war able to create a local build. Looks good 👍 |
Sorting
I'm submitting a ...
I confirm that I
Expected Behavior
As far as I am aware, I did not change anything on my end recently which could have caused this but today, all of a sudden, the TypeScript compiler is compalining about the generated
routes.ts
file.Taking a look at an earlier version, I see that there's a difference in how the
multer.Multer
object gets used/updated:Working version
Offended version
The latter throws the following TS error:
What I don't get here is that I can't see what exactly caused this issue. All deployments re-generate this file and, so far, there were no complaints from the compiler. Not sure what I changed on my end which is causing the issue all of a sudden.
Possibly related
#1651
The text was updated successfully, but these errors were encountered: