search

lighthouse-labs / webpack-react-skeleton

5 stars 6 forks source link

[Proposal] Bind through express #5

Open interlock opened 8 years ago

interlock commented 8 years ago

While the static server for webpack-dev works great for an SPA with an external data source, it may be nice to configure a local API to drive the SPA. If we bind and serve webpack through express we can do that!

Thoughts?

rohannair commented 7 years ago

Express + middleware kinda sucks, webpack-dev-server is amazing but just has a ton of hidden features.

Also... this is from 6 months ago and we didn't see @interlock. Our bad... cc: @Sailias

Sailias commented 7 years ago

@interlock this application was meant to be a standalone application that can transpile down to html, css, and js without the need for a node server when deploying. I use this approach to host the SPAs in S3 as a static website.

If we want to create another branch with a node server that serves this as an isomorphic website, that'd be cool too.

Ideally this application would be good with the following implementations:

alex-wilmer commented 7 years ago

I think having all these different iterations would be really cool, but I think the internals should be built on top of create-react-app. It's setup brilliantly, actively maintained, great docs, deploys to gh-pages etc

Sailias commented 7 years ago

@alex-wilmer I'm not opposed to that. create-react-app looks pretty simple. I also agree having the different iterations would be nice. It would be nice if I could use this repo as a boilerplate for future projects in those iterations.

rohannair commented 7 years ago

create-react-app is fantastic. But it would be interesting to do this one as a full ssr. I was going to build a koa + ssr + apollo stack library myself but maybe we can just do all of that in here.