-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown compiler option 'ignoreDeprecations' #6616
Comments
Hello, please update to TypeScript 4.9.5, which added |
Astro assumes a TS version that supports 'ignoreDependency'. Described here: withastro/astro#6616
For anyone coming here later like me, if you see this error in VS code, also change the typescript version used to the workspace version. The one that comes with VS code is older than 4.9.5. |
Astro assumes a TS version that supports 'ignoreDependency'. Described here: withastro/astro#6616
Astro assumes a TS version that supports 'ignoreDependency'. Described here: withastro/astro#6616
Astro assumes a TS version that supports 'ignoreDependency'. Described here: withastro/astro#6616
What version of
astro
are you using?2.1.4
Are you using an SSR adapter? If so, which one?
None
What package manager are you using?
npm
What operating system are you using?
Mac
What browser are you using?
Firefox, Chrome
Describe the Bug
When I run my jest test on astro 2.1.4
will found this error
in the package
node_modules/astro/tsconfigs/base.json
have this lineI think I suppose to use typescript v5 in order to make it works. I know it's build in by astro. So, I check my typescript version and it's 4.9.4.
Not sure astro should update typescript to be 5? or I need to do something with my jest setup. Beside jest test, the application can build and run normally. Sorry if it's not a bug.
This is my code https://github.com/mameaw14/mameaw14.github.io
Link to Minimal Reproducible Example
https://github.com/mameaw14/mameaw14.github.io/actions/runs/4481801471/jobs/7879010494#step:6:16
Participation
The text was updated successfully, but these errors were encountered: