Empresas
Empregos
  • Sobre nós
  • Soluções
    • Publicação de vagas
      Publique sua vaga e receba candidatos qualificados em 48h.
    • Avaliações de candidatos
      Mais de 500 testes técnicos e psicológicos, mais anti-fraude.
    • Headhunting
      Busca executiva personalizada do início ao fim.
    • Folha de Pagamento + EOR
      Dispersão de folha e EOR em mais de 15 países da LATAM.
  • Preços
  • Empregos

0

5.8K
Visualizações
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?

over 4 years ago · Santiago Trujillo
15 Respostas
Responde à pergunta

0

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.

over 4 years ago · Santiago Trujillo Relatório

0

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

over 4 years ago · Santiago Trujillo Relatório

0

Another way is :

const result = [] as  any;
over 4 years ago · Santiago Trujillo Relatório

0

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.

over 4 years ago · Santiago Trujillo Relatório

0

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())
}
over 4 years ago · Santiago Trujillo Relatório

0

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);
over 4 years ago · Santiago Trujillo Relatório

0

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.

over 4 years ago · Santiago Trujillo Relatório

0

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[]>([]); 
over 4 years ago · Santiago Trujillo Relatório

0

The solution i found was

const [files, setFiles] = useState([] as any);
over 4 years ago · Santiago Trujillo Relatório

0

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} />
}
over 4 years ago · Santiago Trujillo Relatório

0

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

In tsconfig.json -

  "noImplicitReturns": false,

   "strictNullChecks":false,

enter image description here

Solution: type as 'never'

enter image description here

over 4 years ago · Santiago Trujillo Relatório

0

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')
over 4 years ago · Santiago Trujillo Relatório

0

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[] = []
over 4 years ago · Santiago Trujillo Relatório

0

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

result : any = [];

over 4 years ago · Santiago Trujillo Relatório

0

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[] = [];
over 4 years ago · Santiago Trujillo Relatório
Responde à pergunta
Encontrar trabalhos remotos

Descubra a nova forma de encontrar um emprego!

melhores empregos
Principais categorias de trabalho
Empresas
Postar vaga Preços Comercial
Jurídico
Termos e Condições Política de privacidade
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomende algumas ofertas para mim
Preciso de ajuda