Closed muffeeee closed 8 years ago
Had to leave a comment to continue describing the problem.
When I attempt to visit the wordpress site (calypso.localhost:3000), it all gets stuck on a wordpress-logo with some "dev | docs" bar at the bottom. Nothing spectacular happens.
The load times reported by the server on each asset is from 200 to 4000 ms(!), which is extremely long. WP-Calypso also uses an insane amount of CPU and RAM resources of my server.
This project seems dead before even starting.
Thanks for your interest in Calypso, @muffeeee.
When I attempt to visit the wordpress site (calypso.localhost:3000), it all gets stuck on a wordpress-logo with some "dev | docs" bar at the bottom. Nothing spectacular happens.
Do you see anything in your error console?
@bluefuton
No. I only get the standard request logs that you would expect, only that the response times shown in the console range from 200ms to 10000ms. No further errors.
OS: Debian 7
Six hundred and fifty-two modules? Are you guys crazy?
This is hardly an issue with wp-calypso
- if you look at our package.json
, defining our dependencies, it seems reasonable for a project of this size. The problem is with the node
ecosystem, where every little function becomes a separate module. Case in point: the recent debacle with left-pad
that left "half of the internet" broken. Just depending on babel
adds a ton of dependencies. Then there's React, etc.
Any reason why you are running this as root
? AFAIK, there's no need for root permissions - node_modules
are installed locally. Also, once they are installed, subsequent runs should be significantly faster (and less spammy).
Are there any errors in your browser's console? You can try running in full debug mode to see if any meaningful errors show up: DEBUG=* make run
(this turns on all debugging messages for both back- and front-end).
Of course, you might have stumbled upon a broken master
- please fetch the newest one from the repo and start by just trying make run
again (maybe after a make distclean
to start with truly a clean slate).
I don't think I've ever seen any nodejs project warning and erroring this much, nor has I ever seen ANY nodejs project depending on this many libraries. This project is slow and messy, but most of the time it won't even work. Six hundred and fifty-two modules? Are you guys crazy?
Here's what I get from installing, anyway:
The bundles thingy run for 5 minutes before doing anything. This long command output also makes my github window lag now..