Für Kurzentschlossene: Heute Abend geht es bei #t3see um Vite & TYPO3. Ich zeige den aktuellen Stand meiner Extension und best practices, um Vite einfach mit TYPO3 zu verbinden. Hier anmelden: https://t3see.de/meeting
Looking for some feedback from #webdev folks.. I'm experimenting with migrating a #nextjs project to Astro. On paper, the site is a great candidate - content-focused (blog, articles) looking for lighter client experience and better dev experience. https://astro.build/
I have a CMS wired up and have started migrating a couple React components. What gotchas are hiding deeper in this project? Where are the common pitfalls with Astro?
This may look like it’s just a screenshot of the Mattrbld onboarding screen, but it’s in fact the first time Mattrbld is running completely on #vite instead of #webpack.
There’s still quite a lot to do—but the #FOSS release is getting closer! 🎉
Soo...after we all got #vite for #DDEV running with laravel, craftcms, typo3, wordpress - has anybody got this running in GitHub #Codespaces (or Gitpod)? 🤓 Would love to see an example for the port forwarding. Currently trying with DDEv + #craftcms. Cheers! 🤗
#HowToThing#015 — A special one: Creating a polyphonic & multitimbral synth with stochastic sequencer to generate offline audio (not WebAudio!), rendered via fibers (co-routines) and exporting the result as WAV file. Each synth voice uses a randomized config & FX pipeline for each note played (osc → adsr → SVF → filter delay line). Generated audio is attached.
This project is also available as new example #130 in the thi.ng/umbrella monorepo (originally based on a workshop exercise @ University of Applied Sciences, Augsburg, Nov 2022)
"The state of the art is no longer in finding more sophisticated ways to build JavaScript or CSS. It's not to build at all. To lean on HTTP/2 and the now universal support for import maps to avoid bundling."
#JavaScript developers, do you think #ESLint should be a part of the build process?
I've seen quite a few projects use #Webpack and #Vite plugins to run ESLint during their build process. This both shows a huge error overlay when there are linting errors, and halts the build when building for production.
However, I never understood that, as linting does not really ensure validity of the code, but rather that it aligns to some stylistic rules.
It requires a bit of config, but not too bad, given that it's bleeding edge.
What tripped me up in the very end:
You need to call init() first from your wasm module, otherwise error "wasm is undefined", when calling your function.
#vite would be such a better tool if it wasn't doing some non-platform thing with platform primitives at every turn. Or at least, could it have a "vite, but for people who actually like the web" configuration option?