Patrick Dahms
Patrick Dahms
Based on the current proto3 language guide: each `singular element` has a default value. > When a message is parsed, if the encoded message does not contain a particular singular...
@thekip that helped me. thank you ❤️
My guess is, that there is a bug in next.js since `12.2.0`. This has something to do with the "back-forward-cache" in safari. See https://web.dev/bfcache/ for more infos. We could work...
I checked some canary releases of next.js. The bug was introduced in `12.1.7-canary.32`. And my bet is this PR: #37431 changelog: https://github.com/vercel/next.js/compare/v12.1.7-canary.31...v12.1.7-canary.32
I added the following **workaround** to my `custom-types.d.ts` (project root file): ```ts declare module 'vfile-message' { export type VFileMessage = any; } ```
I have considered this for a 2.0 release. Unfortunately I don't have any admin rights anymore for this repo. :(
Yes I had the same issue. You can workaround it with the this webpack config: https://webpack.js.org/configuration/resolve/#resolvemainfields I use `mainFields: ['module', 'main']`. For the future I consider to remove the UMD...
awesome new rule. thx @gipcompany ❤️
The weekly downloads starting to grow. @mcollina what does it need to be a volunteer on this?