React plugin about server HOT 3 CLOSED

Hey francisco, would you mind if I took a crack at this?

from server.

Hi @grantlouisherman the Plugins API is undocumented and it will change so I would recommend not doing this plugin at this point. For instance, the options will be a large breaking change from what is being done right now.

There is no estimated timeline for the 1.1, now I'm wrapping up the beta 2 for the 1.0 and there will be also a beta 3 so it'll be at least few months. This plugin is also really complex, so please explain what you intend on doing before having a go at it. The basic plugin interface so far is:

module.exports = {
  name: 'react',
  options: {
    // ...
  },
  init: [middleware that executes once on startup (no req/res data available)],
  before: [middleware that executes before user middleware],
  after:  [middleware that executes after user middleware],
  launch: [middleware that executes once the server is running (no req/res data available]
};

Then to add it the only way so far is this:

const server = require('server');
const react = require('server-plugin-react');

server.plugins.push(react);

server();

Suggestions (but when doing it you will get a better view of the limitations of those):

• You'll need some basic HTML template where the components will be rendered.
• Keep it to 0.x versions until there is a stable plugin API and until the plugin itself is stable.
• When ctx.options.env !== 'development', execute the bundling inside the init() and just use this bundle later on. On development, run it also on before() to allow real time changes. This might not be needed though, depending on which engine you use.

Conclusion: if you really want/need it at this point or don't mind the really unstable state, go ahead. However I do not recommend doing it at this point. If you have any question feel free to ask, and please tell me how you plan on doing it.

from server.

Done in https://github.com/franciscop/server-react

from server.