Is Vite Faster Than Turbopack?, by @gill_kyle@x.com:
Is Vite Faster Than Turbopack?, by @gill_kyle@x.com:
Even though I'm a backend developer I've got to keep abreast of some frontend stuff so that I can lend my general developer brain to designing or advising or fixing things wherever it happens, and it looks like I've now got to get up to speed on #Preact and #TailWind and #WebPack for the next phase of work. That'll keep me busy for a bit.
Way back in September of 2022, @bart finished off the Webpack miniseries by leaving it as an exercise for the student to deploy their web apps to GitHub Pages. Bart closes that circle in this installment while teaching us how to use GitHub Actions.
Meme Roulette Chrome Extension
Crafting a Chrome Extension: TypeScript, Webpack, and Best Practices Cendekia ・ Feb 13 #typescript #chrome #extensions #webpack source
https://devnews.tech/meme-roulette-chrome-extension/?utm_source=mastodon&utm_medium=jetpack_social
I just realised: I've been intentionally postponing getting into the guts of #webpack for so long, that it got "deprecated" and I no longer have to \o/
Another try, and I'm giving up once again
I just can't upgrade my whole build setup to use #webpack + #typescript + #esmodules for both the app code and the test suite. Something always breaks. I lose *hours* reading github issues and stuff, trying stuff left and right, trying to switch to this or that, nothing works entirely, and it never breaks the same way.
That kind of nonsense will end up with me abandoning my side project
Microfronends as a #decentralized alternative to #npm.
While i can smush everything into a #monoRepo, i wanted to explore the idea of using #Microfrontends as a kind-of self managed alternative to #npm.
Microfronends have been around for a while and i've come across many different approaches. I want to share how im using microfrontends in my project.
Im using #Webpack 5 #moduleFederation to create the #microfrontend. there are some interesting features that i dont think are being mentioned elsewhere:
- Dynamic Remotes: Modules can be loaded from various endpoints. We can use a custom function to ping different URLs and determine the fastest one for loading the required module.
- #Selfhosters can manage modules independently, enhancing control over updates and #security on #opensource projects.
- Development Experience: By using dynamic-remotes and running modules locally during development, it can speed up testing and iteration.
- Scalability: The approach allows for #CDN scaling with module deployments on multiple cloud providers. currently, my redundencies are on AWS S3 + github-pages... but i can see how this can be scaled to more cloud providers.
Im aiming for the architecture to look like the following. Let me know your thoughts on my approach and if its something you would consider for your project.
https://positive-intentions.com/blog/decentralised-architecture
https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure
I wrote a quick article on how to make a live-reload plugin for webpack. It was fun to make this for the very specific scenario I needed it for (where I couldn't use dev server or hot reloading), so I figured I would share how it works.
How to solve "Module parse failed: Bad character escape sequence" https://jsdev.space/howto/bad-character-escape-nextjs/ #javascript #nextjs #webpack
You can send query params to a #javascript module at import time
import "./mymodule.js?hello=world"
and then read them from import.meta.url
const hello = new URL(import.meta.url).searchParams.get('hello');
It does get a little hairy if you’re using a bundler like #webpack, #vite or #parcel
I got to spend a little time on some hobby-coding this weekend, and I updated my template repo for nodejs frontend apps.
The reason is that I wanted minification (actually obfuscation) and that required doing things differently for development versus production builds.
Fortunately webpack has a pretty elegant solution for all that, and it didn't take me very long to figure it out, so that's in the template repo now.
#Rspack 1.0 is now production-ready!
A new #JavaScript bundler designed to be fully compatible with #Webpack, supporting 40+ of the top 50 Webpack plugins.
Details on #InfoQ https://bit.ly/3Y5jp5F
How to Create a Custom Webpack Plugin https://jsdev.space/howto/custom-webpack-plugin/ #javascript #nodejs #webpack
Taking upon the challenge of making this #NodeJs project more user friendly that non-tech users can also use the tool.
Gotten to the point that one can run the code locally and receive the POIs. The image shows a preliminary mask of how the website might look like.
The trickiness of the task is that the tool uses the fs
package which doesn’t directly have a similar package for the web. One can compress a lot of the code with #webpack while using plugins like #pollyfill and #babel. These resolve all the issues other than I/O of files.
It seems like a possible solution to deal with the fs
issue is to use the various database and storage solutions of a browser.
In case you want to try @rspack_dev, do not forget to use `lazyCompilation: isDev,` it brings a lot of speed thanks to @rustlang
Hey #Webpack #Vue people.
I have some generated css-file which originally had full URIs configured for some third-party images I have no control over.
I want to get rid of this external dependency, and proxy these through a local server without having to hard-code the domain name.
The css-file is included through an scss-file.
Previous:
image: url(http:…)
Now:
image: url(/…)
I expected this to "just work", but Webpack fails with "Module not found".
Config in question: https://github.com/HabitRPG/habitica/blob/v5.26.1/website/client/vue.config.js
Sviluppo di un’interfaccia web con TypeScript, React e Webpack - Lorenzo Savini
hhttps://www.youtube.com/watch?v=J55oIFzXxTA&list=PLPGJdxeQ35eAHgEfkfChN_8gN5CJCF9tw&index=15
Introduciamo #TypeScript, vediamo come si integra in un’applicazione #React e come si generano gli asset finali della nostra interfaccia utilizzando #Webpack.