You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mkdir checkly-test
cd checkly-test
npm init -y
npm create checkly # Accept to initialize the project and install dependencies
Which leads to the same error
➜ checkly-test git:(master) ✗ npx checkly test --record
Parsing your project... ⣟
=============
WARNING: You are currently running a version of TypeScript which is not officially supported by @typescript-eslint/typescript-estree.
You may find that it works just fine, or you may not.
SUPPORTED TYPESCRIPT VERSIONS: >=4.3.5 <5.4.0
YOUR TYPESCRIPT VERSION: 5.7.2
Please only submit bug reports when using the officially supported version.
Parsing your project... done
Running 2 checks in eu-west-1.
__checks__/api.check.ts
✔ Books API (221ms)
__checks__/homepage.spec.ts
✔ homepage.spec.ts (6s)
2 passed, 2 total
After some extra digging, I've also found out that the warning doesn't happen if you create the project on a folder without a package json
cd new-folder # Just making sure we aren't in a package.json folder
npm create checkly # Accept creating a new project and select creating a new TS-compatible template
➜ peach-hippopotamus git:(master) ✗ npx checkly test --record
Parsing your project... done
Running 4 checks in eu-west-1.
src/__checks__/api.check.ts
✔ Books API (217ms)
src/__checks__/home.check.ts
✔ Home page (6s)
✔ Login Check (6s)
src/__checks__/multi-step-spacex.check.ts
✔ SpaceX MS (4s)
4 passed, 4 total
The main difference here is that the package json now contains explicit versions for typescript and ts-node devDependencies:
Node.js version
23
NPM version
10.9
@checkly/cli version
latest (v4.8.1)
Steps to reproduce
Leads to this warning.
Things still work as expected but the warning isn't very "trustworthy". 🫣
What is expected?
No TypeScript version mismatch warning.
What is actually happening?
A warning is printed out.
Any additional comments?
No response
The text was updated successfully, but these errors were encountered: