Expected 0 arguments, got 1 in match?

[sgnix]

Playing around with ts-match, I get a type error in the match function. It appears that the codesandbox examples have the same error, for example https://codesandbox.io/p/sandbox/ts-pattern-api-examples-bdy5p2?file=%2Fsrc%2Fexamples%2Fbasic.tsx%3A24%2C14

Am I missing anything?

[gvergnaud]

TS-Pattern v5+ needs TypeScript v5 or higher and your project must be in strict mode. Can you confirm that your project has an expected config?

[sgnix]

Yes, I can confirm that the project is using TypeScript version 5.3.3 and strict mode. I still get that type error. The official ts-match examples in codesandbox also get the same type error.

[gvergnaud]

I'm pretty sure this is because codesandbox doesn't use TS v5+, const type parameters doesn't seem supported: See the syntax error here.

All tests pass with TS v5.3.3 locally

[sgnix]

Codesandbox uses TS 5.3.3. You can verify by inspecting the package.json file.
Additionally, using ts-match locally using a fresh install (TS 5.3.3) and strict mode, still produces the same type error.
I can't be the only one seeing this!
Anyone else?

[darrylnoakes]

I think the issue is the CodeSandbox TS integration, not TS itself.

Everything runs fine.

To corroborate what @gvergnaud said about const type parameters:
In match.d.ts:

These errors cause the declaration to fail, and match to be typed as (alias) match(): any.

[gvergnaud]

I switched the sandbox to a "devbox" and it seems like the editor is now using the version specified in the package.json and the issue is gone.

@sgnix your editor is likely not using the latest typescript version, you should be able to fix that by clicking on "Select TypeScript Version" in VSCode's CMD+P menu.

[sgnix]

All good now. It looks like my editor's LSP plugin had an outdated TS version. Thanks for your time!