u/darraghor great plugin, however it seem to be detecting GET(':id') as invalid while GET(":id") as valid. Both should work with NestJS. I've patched "paramDecoratorNameMatchesRouteParam.js" in my project with the following and it solved it for myself. const isParameterNameIncludedInAPathPart = (paramName, pathPartsToCheck) => { return pathPartsToCheck.some((pathPart) => { return (pathPart === \":${paramName}"` ||` pathPart === `':${paramName}'` || pathPart.includes(\/:${paramName}/`) ||` pathPart.includes(\/:${paramName}"`) ||` pathPart.includes(\":${paramName}/`));` }); }; More on reddit.com

Here is a little guide I wrote for ESLint. It it suitable for beginners who have no experience with ESLint at all. It is also great for people who are used to ESLint but usually copy/paste stuff until it works and do not really understand what they are doing. If you have any questions/feedback, please feel free! More on reddit.com

You can take a look on my repo https://github.com/MobileReality/eslint-config and section in readme „Used packages” unicorn is very interesting eslint config More on reddit.com

I have been curating these rules now for ~5 years. It's been traveling with me as I consult different companies. Currently, we are using it at a 30 eng team. Compared to other rulesets, Canonical is pretty opinionated and strict. Therefore, it is expected that you disable a handful of rules in your project, e.g. @typescript-eslint/return-await improves DX in vast majority of projects, but if you have performance sensitive project, then it makes sense to disable that rule (or at least limit it to try-catch). However, the benefit is that all the code feels like written by the same engineer. This is esp. important when you have a rapidly growing team. More on reddit.com