Oh farrrrk me! 🤦♂️ React Apps, NodeJS c’mon! 🤦♂️ How does anyone do this shit?! 🤯
@prologic@twtxt.net you simply don’t… 😋
I made it by relying on parcel JS v1 (made some time ago).
I first tried create-react-app but aborted immediately once I saw it going for 3 minutes with npm install.
@justamoment@twtxt.net Yeah this is total bullshit I have to say. This is the most stupidest way to to render shit on a page and do some reactive-style single page app 🤦♂️ To make things even worse, there’s Typescript in this goddamn thing 🤬 Why?! 🤦♂️
A: Hey guys, I have a great idea, Since nobody likes Javascript, let’s create a new language?
B: But how will the browser run it?
A: No problems ! We’ll transpile it to Javascript
🤦♂️
Honestly the whole NodeJS / Typescript / NPM ecosystem is a fucking joke 🤦♂️
@prologic@twtxt.net yeah, it’s amazing how things just break apart without even starting to write a single line of code.
@justamoment@twtxt.net This is just so amazingly slow and convoluted 🤣 I dunno how you or @markwylde@twtxt.net do this for a living without tearing your hair out 🤦♂️
@akoizumi@social.kyoko-project.wer.ee Bahahahaha 🤣
@prologic@twtxt.net This is why I contain all node.js activities in an Alpine Linux chroot that I can nuke when I’m done.
@hashrock@twtxt.net Ahh sounds interesting! 🤔 I hope they come up with something way better than NodeJS / NPM 😆
@mckinley@twtxt.net Yeah I do too but with Docker containers 👌
The problem isn’t with NodeJS or NPM, it’s the developers that are so willing to use horrible frameworks/libraries/tooling that is just simply not needed. NodeJS gives you so much out of the box, and NPM is simply a place to store your packages. With Deno, you won’t even need a package manager as it takes a step closer to go modules approach.
If you’re going to use React, TypeScript, NextJs, Webpack, Styled Components, Material UI, Jest, and the 10k dependencies that comes with it, then yeah, your dev environment is going to be slow, bloated, and incredibly frustrating to work with. Not to mention have security issues. I’ve literally just done a fresh create-react-app installation (latest version 5.0.1 as I write this), and boom, 6 high severity vulnerabilities.
But it doesn’t have to be this way. Choose lightweight libraries that do one thing really well, and build your project from the ground up yourself.
The problem isn’t with NodeJS or NPM, it’s developers that are so willing to use horrible frameworks/libraries/tooling that is just simply not needed. NodeJS gives you so much out of the box, and NPM is simply a place to store your packages. With Deno, you won’t even need a package manager as it takes a step closer to go modules approach.
If you’re going to use React, TypeScript, NextJs, Webpack, Styled Components, Material UI, Jest, and the 10k dependencies that comes with it, then yeah, your dev environment is going to be slow, bloated, and incredibly frustrating to work with. Not to mention have security issues. I’ve literally just done a fresh create-react-app installation (latest version 5.0.1 as I write this), and boom, 6 high severity vulnerabilities.
But it doesn’t have to be this way. Choose lightweight libraries that do one thing really well, and build your project from the ground up yourself.
@markwylde@twtxt.net No, it doesn’t have to be this way, but it is (almost) always this way. When a programming language makes it too easy to manage dependencies, you inevitably get microdependencies. It doesn’t help that many people learn JavaScript or Python as their first language.
@prologic@twtxt.net I’m relying on vanilla JavaScript most of the time (even when using frameworks) to not have too much dependencies and lately I found that the type="module" works quite well for most of my needs so I’m dropping almost everything, instead of nom and other i rely on skypack for the libraries.
If you need something bigger but still lighter try snowpack, it uses CDN until you build by optimizing the disk space too.
If anything look bleak try pnpm for a more standard experience of the tooling.