render on client side only #126

vasso1pupkishvilli · 2017-03-20T07:56:06Z

Hi, please describe what configuration do we need to render on the client side only.
I mean without isomorphic server side rendering.
Thanks in advance.

altaywtf · 2017-03-20T12:18:56Z

Hello mate, you need to get rid of server related code and webpack configuration 😅

However, I'd suggest you to take your time and write a basic boilerplate for yourself instead of shredding this one.

Or you can take a look at these issues:

Have a nice day.

vasso1pupkishvilli · 2017-03-20T14:18:54Z

OK. But please describe the meaning of client.tsx file

hirako2000 · 2017-04-06T21:32:12Z

just

replace the get part in server.tsx
=>

app.get('*', (res) => {
  res.sendFile(path.join(__dirname, 'public/index.html'));
});

so that it serves simple index.html page

Add an html page, e.g at the root of src:

<!DOCTYPE html>
<html lang="en">
  <head>
    <title>Some title</title>
  </head>
  <body>
  	<main id="app"></main>
  	<script src='/public/js/app.js'></script>
  </body>
</html>

Import that index.html page from client.tsx

or, instead of 2) and 3), use html-webpack-plugin to generate an html like above from a template (cleaner).

yaniving · 2017-08-15T09:13:00Z

I'm getting res.sendFile is not a function

`**const appConfig = require('../config/main');

import * as e6p from 'es6-promise';
(e6p as any).polyfill();
import 'isomorphic-fetch';

const express = require('express');
const path = require('path');
const compression = require('compression');
const Chalk = require('chalk');
const favicon = require('serve-favicon');

const app = express();

app.use(compression());

if (process.env.NODE_ENV !== 'production') {
const webpack = require('webpack');
const webpackConfig = require('../config/webpack/dev');
const webpackCompiler = webpack(webpackConfig);

app.use(require('webpack-dev-middleware')(webpackCompiler, {
publicPath: webpackConfig.output.publicPath,
stats: { colors: true },
noInfo: true,
hot: true,
inline: true,
lazy: false,
historyApiFallback: true,
quiet: true,
}));

app.use(require('webpack-hot-middleware')(webpackCompiler));
}

app.use(favicon(path.join(__dirname, 'public/favicon.ico')));

app.use('/public', express.static(path.join(__dirname, 'public')));

app.get('*', (res) => {
res.sendFile(path.join(__dirname, 'public/index.html'));
});

app.listen(appConfig.port, appConfig.host, (err) => {
if (err) {
console.error(Chalk.bgRed(err));
} else {
console.info(Chalk.black.bgGreen(
\n\n💂 Listening at http://${appConfig.host}:${appConfig.port}\n,
));
}
});**`

any one ?

altaywtf closed this as completed Mar 20, 2017

ufukomer mentioned this issue Jun 7, 2017

Choose which routes should use server side rendering #136

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

render on client side only #126

render on client side only #126

vasso1pupkishvilli commented Mar 20, 2017

altaywtf commented Mar 20, 2017

vasso1pupkishvilli commented Mar 20, 2017

hirako2000 commented Apr 6, 2017

yaniving commented Aug 15, 2017 •

edited

Loading

render on client side only #126

render on client side only #126

Comments

vasso1pupkishvilli commented Mar 20, 2017

altaywtf commented Mar 20, 2017

vasso1pupkishvilli commented Mar 20, 2017

hirako2000 commented Apr 6, 2017

yaniving commented Aug 15, 2017 • edited Loading

yaniving commented Aug 15, 2017 •

edited

Loading