Drew Lustro
Drew Lustro
I experienced this one today. Error is obtuse and stack trace is unhelpful, especially within a large team. Some days I fight with Jest, some days I let Jest win....
@ShrijanaCodes – unfortunately no. I fought with this one for several hours and gave up.
Wow, I may have **just** got Node 15 working. Here are the required package upgrades / resolutions: ```js "devDependencies": { "babel-preset-gatsby": "0.12.3" } "dependencies": { "node-sass": "5.0.0", "gatsby-plugin-sass": "3.0.0" }...
Also having this issue... unknown `maxHeight` 🤷♂️
**+1 on this**... the style of `applyContainerQuery` is not compliant with best-practices design of HoC's. The signature should be something like: ```jsx applyContainerQuery(query) => (BaseComponent) => { ... containerQuery props...
Dope, thanks. On Wed, Dec 20, 2017 at 5:43 AM, George Kormaris wrote: > This is solved by using your own HOC over , like this: > > const customContainerQuery...
@castwide @nadnoslen – VSCode has notoriously lacked this feature for six years. VSCode supports robust predefined environment variables in `tasks.json` `launch.json`, but they do not work in (workspace) `settings.json` microsoft/vscode#2809
I agree this would be nice. On our site we'd like to disable the cache for logged in users.
Hi @thebadmonkeydev, What does "root-level" field mean? We might be experiencing this issue in our project too, but are not sure. We have some `cache: ...` fields defined on an...
Thanks @julianvmodesto !