#Unsafe argument of type `any` assigned to a parameter of type `[key: string, value: string, cookie?:
12 messages · Page 1 of 1 (latest)
that's an error from eslint, not typescript. look more closely at the end of it
ah you're right. any idea how to resolve it?
you can read about the rule here: https://typescript-eslint.io/rules/no-unsafe-assignment/
every eslint rule has a page like that
if you don't think it's an error worth worrying about, adjust your linter configs and/or disable the rule locally with a comment
in general it's good practice to avoid any though. any is basically turning off the type checker
what I'm wondering is where the any crept in. maybe try hovering each name in your import list to see if any imports failed? TS will turn any unresolved import into an any
i think his tooltip is hiding some of the parameters. i might just be value: any or options: any
I'd think so but the same error is on remove (at least I assume it's the same error)
(i noticed that too and made a ninja edit 🥷)
but yeah if the code works elsewhere it could be something as simple as forgetting to run npm i in a new checkout