Hey y’all, my search engine skills are failing me here. Is anyone out there doing design systems implementation work using microfrontends and module federation? I’m especially curious about the idea of sharing assets like design tokens this way (not just components). Appreciate any examples or takeaways you can share ! #css#designsystems#frontend#webpack#ux
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! 🎉
I think I stumbled into an issue where a compiler is hallucinating and breaking the types of the source it’s trying to simplify. Has anyone had any experience with this, especially with Webpack? #WebDev#webpack#javascript
If you think react is complicated now, go back to 2015 when you had to configure babel and webpack yourself, you had to do SSR and routing yourself, you had to decide between flow and typescript, you had to learn flux and immutable.js, and you had to choose 1 of 100 boilerplates
The most frustrating part of my current struggle to update #PrismJS support in #Firefish is that it would be literally 3 lines of code to fix it if only it were possible for me to add <script> tags to the file served. I'm adding code that should only render on client side (it's exclusively presentation) and points to a CDN so browser caching means it's very limited bandwidth.
But no. I'm stuck messing with weird configurations for #Vue, trying to figure out how the #NodeJS package manager pnpm works, identifying what #Webpack is eating, translating tutorials from EMCA5 to 6, and how to use #Babel to precompile the Prism library with the right settings.
Every technology in that stack allegedly is supposed to improve #productivity. They're all supposed to make my life easier by reducing complexity and streamlining effort. But they have turned a 3 line fix into hundreds spread across a dozen files.
Oh well, this is how modern software development works, isn't it?
"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.
Just published a post on how you can compile #Rust to #WebAssembly for use with #Webpack, #Nodejs and #Deno. There's also an included repository and CodeSandbox demo. Take a look!