maerzhase / ssr3000 Goto Github PK

It could be interesting to think about multiple entry points. currently we are always just server the application from one single entry point.

The pages should only be inject when the user is navigating to another page. When we have this adding a prefetch property is very simple.

Readme has to reflect the new api

The readme could be re-structured, starting with a table of contents…

Users should be able to add a custom _document.js component to the app. the lib then checks if this component exists and if not falls back to the default document.

Add an export command that exports the app as static html.
This would somehow require an API to specify a HTML template. we have no a document component which we need to make customizable.

It would be nice if someone can add entry points to the application without closing it.

currently babel-loader just receives a default set of presets and plugins. i have to test how it behaves with a project specific .babelrc and document it in the README.

i dont like using the ejs anymore would be nicer if the html template would be a react component aswell.

As stated in the readme the user is responsible to have a serverMiddleware setup to serve the responses to the "client". For most simple setups would be nice to have a default middleware that makes it obsolete to specify a middleware by the user unless you really want to modify the default one.

There is no single test in the project. I guess having tests would raise confidence into SSR3000

integrate loadInitialData approach

insights

1. delete require cache somehow only works properly with https://github.com/sindresorhus/clear-module
   i have the suspicion is has to do with this magic stuff happening here: https://github.com/sindresorhus/clear-module/blob/master/index.js#L13

2. invalidate is not called on the server on symlinked node module change