I apologise in advance if I have misrepresented either of the frameworks.
Contact me to correct an error in the above comparison table, if you'd like to add another comparison criteria, or to add another framework.
So I was googling myself this Saturday evening and found your library along with the comparison table.
I can assist in clarifying the details in the comparison table.
Only one running node process. Correct
Does not require a separate webpack configuration. Correct
Enables use of all webpack loaders. Incorrect for universal-webpack: it supports all loaders
Supports stack trace. Do you have any proof that the two projects don't support stack traces, or what you're talking about
So I was googling myself this Saturday evening and found your library along with the comparison table.
I can assist in clarifying the details in the comparison table.
Only one running node process.CorrectDoes not require a separate webpack configuration.CorrectEnables use of all webpack loaders.Incorrect foruniversal-webpack: it supports all loadersSupports stack trace.Do you have any proof that the two projects don't support stack traces, or what you're talking aboutPrevents serving stale data.Same ^Does not override Node.js require().CorrectUses webpack target: "node".CorrectProvides low-level API.Correct