Directory

having the same problem. only thing i can think of is using inline maps but i dont want to do that

any progress on this being implemented? 1.63 is now stable and stabilization of 1.64 is right around the corner.

i figured out a partial solution/workaround toggle "emulate terminal in output console". this however comes at the cost of kind of buggy build output 

could it at least for now be possible that the callback is called inside `tokio::task::spawn_blocking`? Im trying `blocking_lock` an [async mutex](https://docs.rs/tokio/latest/tokio/sync/struct.Mutex.html#method.blocking_lock) inside the callback but despite the callback being synchronous...

bruh ffs how hard is it to use a code block stop pinging me

yea its pretty dumb. whats even dumber are the dumbasses using this. some people really do have negative iq. "shut up before i hackor you"

no response on this? im waiting. something else i additionally noticed is on my own website on chrome desktop when the website is also 1022 pixels or less the browser...

turns out lotomotive scroll isnt loading at all. the js executes without error but theres no dom changes.

fixed with related issue #202. still this was poorly documented. ```js const scroll = new LocomotiveScroll({ el: document.querySelector('[data-scroll-container]'), smooth: true, smartphone: { smooth: true, }, tablet: { smooth: true, },...

It should not detect mobile breakpoints based off something arbitrary like screen width. What if the Mobile screen width is very large. What if the desktop window is really small?...