Jan Peša

With some heavy trial-and-error I have identified the imports which were causing this and fixed them. A day (not so) well spent... Really a horrible experience for someone using Vite...

The problem I found with the approach posted by @nicktabolich is that it distributes logarithmic range in this form on X axis: `1111111111|222222222|33333333|4444444|55555|6666|777|88|9|1010101010|...` I assumed that I will always use...

Had the same problem. `unsavedWarningsConfigProvider.routeEvent = '$stateChangeStart';` in config helped.

@Joshfindit And how should be that fact helpful in this case? Because there seems to be no way to control downcasing within generated resolvers, amirite? The huge issue here is...

@fguille94 No, I meant that it should be ideally configurable via the `makeAugmentedSchema` config, where you should be able to toggle case insensitive search to make it usable in real...

Just encountered this as well, very annoying bug... I guess we'll have to stick with CSV string for now 🙄

This started happening to me after migrating from Vite 2 to Vite 3. 🤷

Wow, I was just surprised by this behavior too. Not what I was used to from 3.5.x. Well, it can be usefull, but there is also a nasty bug, which...

Just a heads-up. Do **NOT** install `@types/react-date-range` 0.x for the latest 1.x version of this lib. They are heavily out of sync. Use classic `declare module 'react-date-range;` as a temp...

@futurify-ydang Maybe because there is no such file as `react-date-range/locale/vi`? You have two options, either use: ```typescript declare module 'react-date-range/dist/locale'; // the correct path import { vi } from 'react-date-range/dist/locale';...