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
[v2.22.0] Typing issue: Cannot redeclare block-scoped variable daysInWeek/minTime #2491
Comments
Also having this issue |
Just got this too. |
having this issue too, |
@kossnocorp kindly ping as many people updating date-fns will experience errors. |
@douweknook The typings.d.ts file is generated automatically by I've edited the first message to mention that |
hi everyone, |
Just to add that we're seeing this issue when using v2.21.3 |
@AniaMakes good to know, although it seems fine on my side with v2.21.3; I'm updating my first message regardless |
I've deployed my app around 1h before 2.22.0 and deployment went through, then after 2.22.0 was released the build failed. When I lowered the version back to 2.21.3 the build went through normally again. |
@Rogdham, thank you so much for a promptly and carefully crafted issue. I'm already working on a fix and hope to release it really soon. |
@kossnocorp see #2494, I think that should take care of the problem. That constants file needs explicit |
Fixed and released in |
Hello @kossnocorp, in the v2.22.0 release, there are duplicates of
daysInWeek
andminTime
intypings.d.ts
that create issues with TypeScript.Unfold for error messages
FAQ
This issue is getting some traction, people are subscribing to it, so we would all appreciate if you could reduce the noise and comment only if you bring something new to the discussion 🙏
I'm having the same issue
How to fix the issue for now?
skipLibCheck
totrue
intsconfig.json
(sectioncompilerOptions
).I want to fix the issue by creating a PR
Please coordinate by writing below! Note that thetypings.d.ts
file is generated automatically byscripts/build/typings.js
, so you probably need to look into that and make the changes there.⏳ People are looking to fix that issue now 🤞🎉 bug fixed in v2.22.1 🎉
The text was updated successfully, but these errors were encountered: