ChatGPT解决这个技术问题 Extra ChatGPT

What is "not assignable to parameter of type never" error in TypeScript?

Code is:

const foo = (foo: string) => {
  const result = []
  result.push(foo)
}

I get the following TS error:

[ts] Argument of type 'string' is not assignable to parameter of type 'never'.

What am I doing wrong? Is this a bug?

const result: [] = [] => const result: string[], not just [], but string[], if you don't know the type inside the array, you can always fallback to any[]

Y
YakovL

All you have to do is define your result as a string array, like the following:

const result : string[] = [];

Without defining the array type, it by default will be never. So when you tried to add a string to it, it was a type mismatch, and so it threw the error you saw.


That seems bizarre to me, why default to never[] ? is there ever a use for that except "an array that will ALWAYS be empty?"
I totally agree because, to be honest, I can't think of a use case that an array of nevers will be useful. But while looking into it I came across this answer which has great info.
Shouldn't the default type be "any"? When you declare a variable (let x; ) it is of type any by default. Not never.
@VincentBuscarello I guess, the main point of such default is to make one to always add types to their arrays; but the error message is definitely not helpful.
I always like to know where these changes happened in the source code for better understanding so for those curious see: github.com/Microsoft/TypeScript/issues/9976 and github.com/microsoft/TypeScript/pull/8944
O
Oleg Valter is with Ukraine

Another way is:

const result: any[] = [];

Actually using any isn't a good option, because it basically turns off any TypeScript features. It's a workaround and can lead to various bugs.
Yes. But sometimes nothing else works especially when you are working with third-party libraries..
wouldnt const result: any[] = [] be more accurate? its an array of any not and array treated as any
@g00dnatur3 is right. If you must use any, then at least specify that it is an array of items of any type.
R
Randy Hudson

This seems to be some strange behavior in typescript that they are stuck with for legacy reasons. If you have the code:

const result = []

Usually it would be treated as if you wrote:

const result:any[] = []

however, if you have both noImplicitAny FALSE, AND strictNullChecks TRUE in your tsconfig, it is treated as:

const result:never[] = []

This behavior defies all logic, IMHO. Turning on null checks changes the entry types of an array?? And then turning on noImplicitAny actually restores the use of any without any warnings??

When you truly have an array of any, you shouldn't need to indicate it with extra code.


True, this is absolutely unintuitive, a parameter called "no implicit any" should imply that any time something would be assumed to be any - it is not. Also, the implicit "never" seems dumb, why not simply state an error with: Array does not have its type declared. IMHO this should solely depend on noImplicitAny, not on the combination.
I think that people who contribute to large repos tend to sometimes over-engineer it. At least we know what flags we should set to make it intuitive for us. As for me I set both flags to true and feel fine with it.
n
neiya

I got the same error in ReactJS function component, using ReactJS useState hook.

The solution was to declare the type of useState at initialisation using angle brackets:

// Example: type of useState is an array of string
const [items , setItems] = useState<string[]>([]); 

I
ImFarhad

I was having same error In ReactJS statless function while using ReactJs Hook useState. I wanted to set state of an object array , so if I use the following way

const [items , setItems] = useState([]);

and update the state like this:

 const item = { id : new Date().getTime() , text : 'New Text' };
 setItems([ item , ...items ]);

I was getting error: Argument of type '{ id: number; text: any }' is not assignable to parameter of type 'never'

but if do it like this,

const [items , setItems] = useState([{}]);

Error is gone but there is an item at 0 index which don't have any data(don't want that).

so the solution I found is:

const [items , setItems] = useState([] as any);

Actually, I think a better version of your solution would be const [items , setItems] = useState([] as string[]);
L
Lakshan Hettiarachchi

The solution i found was

const [files, setFiles] = useState([] as any);

Using as any thwarts a static typing system. If you know what type or types will be housed in the array, it's much better to be explicit: const myArray: string[] = []; const [files, setFiles] = useState(myArray);. Note in the case of useState, you can pass in a generic, instead: const [files, setFiles] = useState<string[]>([]);
This is a bad practice. By taking as any you are just saying "nah I don't want to use typescript". Neiya's answer on the other hand is good enough. A better approach should be interface, but I am new to typescript as well, so I am not sure how to interface this one.
I can't believe this answer has so many upvotes, this is basically silencing typescript, defeating its purpose altogether.
@jmealy your answer worked for me and should be the ts way of solving this. Following your example, I declared a const outside my component as const initialEmailsState: string[] = []; and used it inside the the component with useState as const [emails, setEmails] = useState(initialEmailsState); and now I can set emails like this without problems: setEmails([...emails, createOption(inputValue)]);
S
Shah

Assuming your linter is okay with "any" types:

If you don't know the type of values that will fill the Array, you can do this and result will infer the type.

const result: any[] = []

04/26/2022: Coming back to this I think the solution you may have been looking for may be something like this:

const foo = (foo: string) => {
  const result: string[] = []
  result.push(foo)
}

You needed specify what the array is since result = [] has a return type of any[]. Typically you want to avoid any types since they are meant to be used as an "Escape hatch" according to Microsoft.

The result is an object that is an array that expects type string values or something that includes a string such as string | number.


M
Mickers

I was able to get past this by using the Array keyword instead of empty brackets:

const enhancers: Array<any> = [];

Use:

if (typeof devToolsExtension === 'function') {
  enhancers.push(devToolsExtension())
}

Thanks for pointing out. The Array keyword yet is another good way. It is even more semantically useful in case you have to define a type for an array of arrays like this let parsed: Array<[]> = [];
@ValentineShi You could still do something like [][]. If you wanted something like an array of array of numbers you could do number[][]. On that note, do consider that: parsed: Array<[]> here is implicitly Array<any[]>
r
rohit.khurmi095

Error: Argument of type 'any' is not assignable to parameter of type 'never'.

In tsconfig.json -

  "noImplicitReturns": false,

   "strictNullChecks":false,

https://i.stack.imgur.com/hLgbO.png

Solution: type as 'never'

https://i.stack.imgur.com/huAF7.png


A
Ashutosh Singh

Remove "strictNullChecks": true from "compilerOptions" or set it to false in the tsconfig.json file of your Ng app. These errors will go away like anything and your app would compile successfully.

Disclaimer: This is just a workaround. This error appears only when the null checks are not handled properly which in any case is not a good way to get things done.


For me,in tsconfig is only "strict" part,when i set it to false as you say error go away,and this is in react,not angular.Thanks.
A
Akshay Vijay Jain

One more reason for the error. if you are exporting after wrapping component with connect()() then props may give typescript error Solution: I didn't explore much as I had the option of replacing connect function with useSelector hook for example

/* Comp.tsx */
interface IComp {
 a: number
}

const Comp = ({a}:IComp) => <div>{a}</div>

/* ** 

below line is culprit, you are exporting default the return 
value of Connect and there is no types added to that return
value of that connect()(Comp) 

** */

export default connect()(Comp)


--
/* App.tsx */
const App = () => {
/**  below line gives same error 
[ts] Argument of type 'number' is not assignable to 
parameter of type 'never' */
 return <Comp a={3} />
}

d
domready

You need to type result to an array of string const result: string[] = [];.


B
BertC

I got the error when defining (initialising) an array as follows:

let mainMenu: menuObjectInterface[] | [] = [];

The code I got the problem in:

let mainMenu: menuObjectInterface[] | [] = [];
dbresult.rows.forEach((m) => {
    if (!mainMenu.find((e) => e.menucode === m.menucode)) {
        // Not found in mainMenu, yet
        mainMenu.push({menucode: m.menucode, menudescription: m.menudescription})  // Here the error
    }
})

The error was: TS2322: Type 'any' is not assignable to type 'never'

The reason was that the array was initialised with also the option of an empty array. Typescript saw a push to a type which also can be empty. Hence the error.

Changing the line to this fixed the error:

let mainMenu: menuObjectInterface[] = [];

H
Hadar Shpivak

you could also add as string[]

const foo = (foo: string) => {
  const result = []
  (result as string[]).push(foo)
}

I did it when it was part of an object

let complexObj = {
arrData : [],
anotherKey: anotherValue
...
}
(arrData as string[]).push('text')

M
Mounir bkr

in latest versions of angular, you have to define the type of the variables:

if it is a string, you must do like that: public message : string =""; if it is a number: public n : number=0; if a table of string: public tab: string[] = []; if a table of number: public tab: number[]=[]; if a mixed table: public tab: any[] = []; .......etc (for other type of variables) if you don't define type of variable: by default the type is never

NB: in your case, you must know the type of variables that your table must contain, and choose the right option (like option 3 ,4 5 ).