{"id":629,"hash":"2bea7581eb5eaf909978ac26da86ae8f24a3f1da39c326e61c512034630ac6eb","pattern":"How to bypass warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any","full_message":"We have a strict zero lint issues policy. This means all errors and warnings need to be fixed.\n\nFacing this lint error in our React typescript project:\n\nwarning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any\n\nTried this: // eslint:@typescript-eslint/no-explicit-any: \"off\" which is not working.\n\nHow can I bypass this rule?","ecosystem":"npm","package_name":"typescript","package_version":null,"solution":"In Angular we add that in the TypeScript rules. Not in the general rules because sometimes that doesn't work.\n\nExample:\n\n\"rules\": {\n             \n   \"@typescript-eslint/no-explicit-any\": [\"off\"]\n}\n\nIn the .eslintrc.json file","confidence":0.95,"source":"stackoverflow","source_url":"https://stackoverflow.com/questions/58467000/how-to-bypass-warning-unexpected-any-specify-a-different-type-typescript-eslin","votes":90,"created_at":"2026-04-19T04:51:24.132005+00:00","updated_at":"2026-04-19T04:51:24.132005+00:00"}