Marcin Kurkiewicz

[Marcin Kurkiewicz @Qrzy88]

@MichaelThiessen @vuejs Worth mentioning such implementation is not suitable for SSR... 👀

[Marcin Kurkiewicz @Qrzy88]

@MichaelThiessen @vuejs Hi Michael, I think you need to review the content you share, useHead from VueUse has been sunset in favour of Unhead, like ~6 months or so ago.. and direct usage of it is discouraged, according to the readme you link to.

[Latif Nasser @latifnasser]

Last January, I noticed something peculiar in my 2yo’s bedroom that - after a year of obsessive reporting - led me to a profound cosmic revelation about what’s even possible in our universe. A 🧵.

[Suchar Codzienny @SucharCodzienny]

Co można puszczać zamiast fajerwerków?
a) Muzykę
b) Wodze fantazji
c) Się
d) Pawia

[Marcin Kurkiewicz @Qrzy88]

@danielcroe @TheAlexLichter @nuxt_js Thank you! It is a bit clearer to me now.

[Marcin Kurkiewicz @Qrzy88]

@danielcroe @TheAlexLichter @nuxt_js Thanks for the explanation!
Note: Not just the prefix, but the entire env variable name is determined by the config structure.

[Marcin Kurkiewicz @Qrzy88]

@danielcroe @TheAlexLichter @nuxt_js Yeah, so I do not quite get the second point here. Where does this come from and why could we not have same freedom as in Nuxt2. 🙂

[Marcin Kurkiewicz @Qrzy88]

@TheAlexLichter @nuxt_js @danielcroe Another issue is: why does Nuxt 3 take anything into the RUNTIME config during the BUILD. It's a RUNTIME config, isn't it?
Nuxt 2 did not do that. One can run "OTHER_VAR=build yarn build" and then start the app without the env var - nothing is in the config.

[Marcin Kurkiewicz @Qrzy88]

@TheAlexLichter @nuxt_js Hi @danielcroe, is it a miss in Nitro or was it done on purpose? I'm really curious, I haven't played with an app on Nuxt 3 needing this in production but I would be genuinely shocked if I faced this, as I've been using different env vars in Nuxt 2 so far without issues. :)

[Marcin Kurkiewicz @Qrzy88]

@TheAlexLichter @nuxt_js You are getting me more curious now 🙂 would you mind elaborating on "naive" here?

[Marcin Kurkiewicz @Qrzy88]

@TheAlexLichter @nuxt_js No, it works just fine in Nuxt 2! Try it yourself 🙂

[Marcin Kurkiewicz @Qrzy88]

@TheAlexLichter @nuxt_js Uhm, I was pretty sure I was commenting on your tweet with linked video about the most common mistake in runtime config, where an env var named differently than the config key isn't actually read at runtime. It worked in Nuxt 2 (I just checked this)

[Alexander Lichter @TheAlexLichter]

Performance in @nuxt_js is amazing by default! But when building your app, you still have to keep quite some things in mind 👀

In the first video of the "Nuxt Performance In Depth" series, we explore the Nuxt payload and figure how to make it smaller! 💚

https://t.co/kJKrpnwhu5

[Nuxt @nuxt_js]

The State of JavaScript 2023 is here 👀

https://t.co/exePr7q3Bp

[Marcin Kurkiewicz @Qrzy88]

@SquashPL @siebor_szymon @CebulaDeal Jak tu pomagałoby to śledzenie twarzy?

[Marcin Kurkiewicz @Qrzy88]

@danielcroe Hey Daniel, with this diff I got intrigued by budget.json - would you mind sharing what is this about? Sounds like some kind of performance budget guard but I wonder how is it used 🙂