Aman Kubanychbek
Aman Kubanychbek
AFAIK next.js does not support PWA out of the box...
Тут вот корень проблемы указан, дело в peer dependency пакета `create-react-context` (спойлер: автор его успешно забросил). ```sh Could not resolve dependency: peer react@"^0.14.0 || ^15.0.0 || ^16.0.0" from [email protected] node_modules/react-yandex-maps/node_modules/create-react-context...
What about [yup#setLocale](https://github.com/jquense/yup#using-a-custom-locale-dictionary) API? It seems to be easier to handle global translations for both primitives and their methods
In our case, this bug reproduced if the parent container had a `position: fixed + inset + transform`, with no scaling adjustments. And, we found out two workarounds: - as...
Here is my temporary solution as @js2me suggested ```js onCreateRouteName: (nameInfo, rawInfo) => { nameInfo.original = nameInfo.original.replace(/\d+$/, '') nameInfo.usage = nameInfo.usage.replace(/\d+$/, '') }, ```
Yeah, thanks, I've been looking through it. If you don't mind keeping this issue open then I'd like to reply here once I'll get something viable
What about [Snowpack](https://www.snowpack.dev/) integration? There is a statement in their docs which seems to be false in case of Linaria: > Snowpack also supports any popular CSS-in-JS library
nice feature no. 1 is [tree shaking](https://github.com/Araphel/babel-preset-es2015-native-modules)
AFAIK, it should perform this by default, your modules & third-party ones should be in ES2015
usage example, in view `@Html.IncludeNGon(converters: new IsoDateTimeConverter() { DateTimeFormat = "yyyy-MM-dd HH:mm:ss" })`