Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by mtlynch | Hacker News Reader

Full thread

mtlynch·

Oof, just loading this page caused my browser to download 170 MB of content. I hope she has a good CDN.

View on HN

Trying it now for the first time, and getting an HTTP Basic Auth pop-up. They caught on.

Looks like it's all on yourhosting.nl. "Unlimited" traffic. Of course until we hug it to death...

That's more than three times my daily data allowance on my cellphone connection!

So... a typical node.js page size then?

One doesn’t typically write a webpage in node

node is used extensively on frontend. Massive bundles of js libraries. That is indeed part of the webpage.

And it doesn't matter how typical or not, I'm referencing the case in point.

I think you're confusing js with node. node typically doesn't run on the frontend, but can be used when developing the front but it won't be running on the users browser.

No confusion here. Node.js is an entire ecosystem, and npm is a child of that mess. It is absolutely famous for the massive gobs of absolutely junk it pulls in to satisfy dependencies a frontend dev could manage with 4 lines of native js.

You may rail on about how npm != node, but everyone considers npm to be 'node package manager', no matter what the initialism actually stands for.

Node.js is a server runtime, it does not run clientside at all. NPM can be used to download server OR client JS packages. A frontend bundler tool (e.g. webpack) can analyze a dependency graph of your client-side entrypoint and bundle all the NPM deps used, which will then be sent and executed on the client. No Node.js components or code are run client-side at any point (caveat - some packages can work server- and client-side).

HTH

Node.js is an ecosystem. The server is a component.

Node is a platform for running JS on the server; it's a non sequitur to talk about node page size whether in this case or any other

Reply on news.ycombinator.com