@jeffrey_way I lean heavily on using IIFEs within the template block - this pattern can move a lot of the logic into the template scope eg. stuff you would want evaluated in a loop, and seems to satisfy most cases where you might want multiple components per file.
@hugorcd@vercel@nuxt_js@nuxt_hub@Cloudflare Thanks. Looking for confidence in doubling down on cloudflare infra for an app in a critical stage of scaling over coming months, using various other cloudflare features (R2 blobs etc). Nuxtlabs investing in developing cloudflare integration in next few months in jeopardy?
@adamwathan Adobe GoLive was the sweet spot. It had this elastic pickwhip feature where you could reference files - I’ve imitated it in loads of UIs since.
@MichaelThiessen@vuejs People should sing about destructured computed more - I’d say one of the main perceived limitations of vue if you’re coming from the react world is the idea of two-way data-binding and this excellent feature is the way to control it gracefully.
@jonathan_wilke@supastarter Would love to see a guide for this monorepo setup for those of us who have extended from but are no longer downstream of the main repo
@RoryStewartUK When LED lights were invented, everyone thought it would mean less energy consumption, but we bought more LEDs. The availability of cheaper models, inevitably models run locally, will be outstripped by greater adoption. Jevon’s paradox.
@lukaszarpak@jacobandrewsky@vuejs Aside from slightly different syntax are there any? Sometimes it’s helpful to have to unwrap a ref to be reminded that it’s reactive
@adamwathan Option A seems the most intuitive currently but feel like option C would help nudge us all be more mindful of the variety of devices and implications.
@adamwathan Yeah actually yes. This can be a bit of a pest especially with lot of breakpoints. Most of the time I want to define leading per breakpoint. How about a util like leading-inherit to determine the current way it works - as can see a use case but it’s not the majority.
@adamwathan@CraftCMS is wonderful, and ultra flexible under the hood. Kind of one step abstracted from laravel if you want to be in php world. Easy self generating graphql api for headless projects.
@MichaelThiessen@nuxt_js When some potentially deeply nested server request depends on the response of a request in an ancestor component (and causes build errors if it’s supposed to be prefetched)
@MichaelThiessen@vuejs I’m looking to hire full stack freelancer(s) (Europe) across Nuxt, with strong design skills for a travel SaaS. DM me any relevant links if you have any availability…