Can't use setAtom normally

[joetawil7]

Bug Description

Hello and thank you for this amazing state management

I've been using Jotai for almost 3 years now and now in a new project I am trying to use the useAtom with the normal value,setvalue but the setValue is throwing a type error

'use client';

import { AlertCircle } from 'lucide-react';
import { useEffect } from 'react';
import { Alert, AlertDescription, AlertTitle } from '@/components/ui/alert';
import { useAtom } from 'jotai';
import { errorAtom } from '@/services/atoms';

export function ErrorAlert() {
const [error, setError] = useAtom(errorAtom);

useEffect(() => {
if (error?.length === 0) return;

const timer = setTimeout(() => {
  setError(undefined); 
}, 3000);

return () => clearTimeout(timer);

}, [error, setError]);

return (


Error
{error}

);
}

setError here is throwing
This expression is not callable.
Type 'never' has no call signatures.ts(2349)

Please help

Reproduction Link

no link

[joetawil7]

And forgot to mention that the atom is being initialized like this

export const errorAtom = atom<string | undefined>(undefined);

[joetawil7]

Even using

const setError = useSetAtom(errorAtom);

will throw this
No overload matches this call.
Overload 1 of 2, '(atom: WritableAtom<string, unknown[], unknown>, options?: Options): SetAtom<unknown[], unknown>', gave the following error.
Argument of type 'Atom' is not assignable to parameter of type 'WritableAtom<string, unknown[], unknown>'.
Property 'write' is missing in type 'Atom' but required in type 'WritableAtom<string, unknown[], unknown>'.
Overload 2 of 2, '(atom: WritableAtom<unknown, never[], unknown>, options?: Options): SetAtom<never[], unknown>', gave the following error.
Argument of type 'Atom' is not assignable to parameter of type 'WritableAtom<unknown, never[], unknown>'.
Property 'write' is missing in type 'Atom' but required in type 'WritableAtom<unknown, never[], unknown>'.ts(2769)
atom.d.mts(36, 5): 'write' is declared here.
atom.d.mts(36, 5): 'write' is declared here.

[dai-shi]

Assuming it's a TypeScript error, I think you are not using "strict": true in your tsconfig.json.

[joetawil7]

That's the case, thanks a lot