Hey, #vuers, sadly we are not able to have a meetup at our regular place.
So do you know any company that would host our meetup next week on Tuesday 14th November from 7pm in Berlin??? We need space for +- 50 happy vuers.
Please help 💚 Thanks for RT 🙏
I am usually not a big fan of most UX/ Product design frameworks graphs out there, often look over complicated. But, this one looks quite nice: SEER: Sense, Explore, Evaluate, Refine. Also, it involves users at different steps. https://t.co/cFycpZrqzS
Danke für alle großen und kleinen Events, die wir 2022 gemeinsam umgesetzt haben.
Wir wünschen Euch eine schöne Winterpause und sind im Januar wieder für Euch da!
❗NEW AX FEATURE: AI-Based Machine Translation
The new #feature for machine #translation of entire statements including branches and containers is now live. This makes translating a project into another language even faster - available now and in 29 languages.
Try it out now!
Did you now that Venueless is fully built on Django on the backend side? We're glad @DjangoConEurope is joining the ranks of the Python conferences powered by Venueless as well. It's snakes all the way down!
@patak_dev @vite_js About right, yes. Just running it once, the numbers are more like:
Legacy: 20s
New strategy (lazy): 11s
New strategy (eager): 27s
But those are in the same ballpark.
@patak_dev @vite_js adding all dynamic imports to `optimizeDeps.entries` gets rid of all `new dependencies optimized` logs and reloads, but also takes ~30s. I added 57 entries, most of them are lazy loaded routes.
@patak_dev @vite_js I'll try it out later today, but we have quite a lot of dynamic imports and maintaining a separate list of those does not seem feasible in the long term.
@patak_dev @vite_js Here are the devtool console logs.
I suspect the big difference is because there is a lot of app startup before a page reload actually happens.
@patak_dev @vite_js Measuring a page load deep into our app until component load shows this (just a sample size of one though):
legacy, no optimizeDeps.include: 38.921s, 2 reloads
new strategy, no optimizeDeps.include: 35.093s, 1 reload
new strategy, with optDeps: 18.684s, 0 reloads
@patak_dev @vite_js On our large codebase I see one hard reload less. The second reload is a async import, which is still a bit grating, especially on navigation, where the reload seems to forget the navigation and you have to do it again.