Alex Cory
Alex Cory
What do you mean out of beta? We're in Next 12 now and [SWC support was introduced in Next 11](https://nextjs.org/blog/next-11-1#:~:text=SWC%20integration%20to%20replace%20JS%20tooling%20(Babel%20and%20Terser)).
Wait so it **is fixed**, or it **is not fixed** yet? Because I only see documentation updates.
I would submit a PR myself but like I said, not familiar with `@most/core`
Ah, I totally missed your previous commits. Thanks for the quick turnaround
@zhicong Do you mean something like this? ```js useEffect(() => { const getSubscribe = async () => { const keyboardDetector = await import('on-screen-keyboard-detector') return keyboardDetector.subscribe } const subscribe = getSubscribe()...
Give this a shot. Seems to be working for me. ```js const getViewports = () => ({ viewport: { width: Math.max( document.documentElement.clientWidth || 0, window.innerWidth || 0 ), height: Math.max(...
I'm pretty sure this also affects when the keyboard is opened the height will be incorrect.
If the body of the post is the same, it will attempt to cache it. Try ```js const {post} = useFetch(`/hello?q=${new Date().getTime()}`, { cachePolicy: 'no-cache' }) ```
This is great feedback. I agree, I think we should put this into effect. Will get to it as soon as I can.
I can :) Will do it asap