Highlights for simple pattern in nodejs webserver for serve my SPA
up vote
0
down vote
favorite
I been working in a website that have a simple application built in reactjs that works as single page application.
The requirements are that the routes must be normal routes like /works/software-engineering or /user/charlie-parker, avoiding he # because this website will be optimized for SEO and the routing it is very important.
My simple webserver built in nodejs looks like this:
const express = require('express');
const version = require('./package.json');
const app = express();
const port = process.env.PORT || 8080;
// make express look in the public directory for assets (css/js/img)
app.use(express.static(`$__dirname/public`));
// show docker container health
app.get('/health', (req, res) =>
res.setHeader('Content-Type', 'application/json');
res.send(JSON.stringify( version, status: 'up', uptime: process.uptime() ));
);
// redirect all routes like works/work-tag,works/work-id or user/user-id/edit to index.html
app.get('*', (req, res) =>
console.log('+++++++++++++++++++++++++++++++');
console.log(req.params);
console.log('+++++++++++++++++++++++++++++++');
res.sendFile(`$__dirname/public/index.html`);
);
app.listen(port, () =>
console.log(`App is running on http://localhost:$port`);
);
So my question for the community, **In your experience: Any case that is not covered for this simple web server for a SPA application? Some caveat for this kind of implementation? **
Thanks!
node.js webserver single-page-application
add a comment |
up vote
0
down vote
favorite
I been working in a website that have a simple application built in reactjs that works as single page application.
The requirements are that the routes must be normal routes like /works/software-engineering or /user/charlie-parker, avoiding he # because this website will be optimized for SEO and the routing it is very important.
My simple webserver built in nodejs looks like this:
const express = require('express');
const version = require('./package.json');
const app = express();
const port = process.env.PORT || 8080;
// make express look in the public directory for assets (css/js/img)
app.use(express.static(`$__dirname/public`));
// show docker container health
app.get('/health', (req, res) =>
res.setHeader('Content-Type', 'application/json');
res.send(JSON.stringify( version, status: 'up', uptime: process.uptime() ));
);
// redirect all routes like works/work-tag,works/work-id or user/user-id/edit to index.html
app.get('*', (req, res) =>
console.log('+++++++++++++++++++++++++++++++');
console.log(req.params);
console.log('+++++++++++++++++++++++++++++++');
res.sendFile(`$__dirname/public/index.html`);
);
app.listen(port, () =>
console.log(`App is running on http://localhost:$port`);
);
So my question for the community, **In your experience: Any case that is not covered for this simple web server for a SPA application? Some caveat for this kind of implementation? **
Thanks!
node.js webserver single-page-application
1
The problem is that there cannot be 404, even paths that obviously aren't supposed to be handled by client-side router, e.g./js/.
– estus
Nov 10 at 6:47
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I been working in a website that have a simple application built in reactjs that works as single page application.
The requirements are that the routes must be normal routes like /works/software-engineering or /user/charlie-parker, avoiding he # because this website will be optimized for SEO and the routing it is very important.
My simple webserver built in nodejs looks like this:
const express = require('express');
const version = require('./package.json');
const app = express();
const port = process.env.PORT || 8080;
// make express look in the public directory for assets (css/js/img)
app.use(express.static(`$__dirname/public`));
// show docker container health
app.get('/health', (req, res) =>
res.setHeader('Content-Type', 'application/json');
res.send(JSON.stringify( version, status: 'up', uptime: process.uptime() ));
);
// redirect all routes like works/work-tag,works/work-id or user/user-id/edit to index.html
app.get('*', (req, res) =>
console.log('+++++++++++++++++++++++++++++++');
console.log(req.params);
console.log('+++++++++++++++++++++++++++++++');
res.sendFile(`$__dirname/public/index.html`);
);
app.listen(port, () =>
console.log(`App is running on http://localhost:$port`);
);
So my question for the community, **In your experience: Any case that is not covered for this simple web server for a SPA application? Some caveat for this kind of implementation? **
Thanks!
node.js webserver single-page-application
I been working in a website that have a simple application built in reactjs that works as single page application.
The requirements are that the routes must be normal routes like /works/software-engineering or /user/charlie-parker, avoiding he # because this website will be optimized for SEO and the routing it is very important.
My simple webserver built in nodejs looks like this:
const express = require('express');
const version = require('./package.json');
const app = express();
const port = process.env.PORT || 8080;
// make express look in the public directory for assets (css/js/img)
app.use(express.static(`$__dirname/public`));
// show docker container health
app.get('/health', (req, res) =>
res.setHeader('Content-Type', 'application/json');
res.send(JSON.stringify( version, status: 'up', uptime: process.uptime() ));
);
// redirect all routes like works/work-tag,works/work-id or user/user-id/edit to index.html
app.get('*', (req, res) =>
console.log('+++++++++++++++++++++++++++++++');
console.log(req.params);
console.log('+++++++++++++++++++++++++++++++');
res.sendFile(`$__dirname/public/index.html`);
);
app.listen(port, () =>
console.log(`App is running on http://localhost:$port`);
);
So my question for the community, **In your experience: Any case that is not covered for this simple web server for a SPA application? Some caveat for this kind of implementation? **
Thanks!
node.js webserver single-page-application
node.js webserver single-page-application
asked Nov 10 at 4:28
Gonzalo Pincheira Arancibia
1,9361131
1,9361131
1
The problem is that there cannot be 404, even paths that obviously aren't supposed to be handled by client-side router, e.g./js/.
– estus
Nov 10 at 6:47
add a comment |
1
The problem is that there cannot be 404, even paths that obviously aren't supposed to be handled by client-side router, e.g./js/.
– estus
Nov 10 at 6:47
1
1
The problem is that there cannot be 404, even paths that obviously aren't supposed to be handled by client-side router, e.g.
/js/.– estus
Nov 10 at 6:47
The problem is that there cannot be 404, even paths that obviously aren't supposed to be handled by client-side router, e.g.
/js/.– estus
Nov 10 at 6:47
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53235992%2fhighlights-for-simple-pattern-in-nodejs-webserver-for-serve-my-spa%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
The problem is that there cannot be 404, even paths that obviously aren't supposed to be handled by client-side router, e.g.
/js/.– estus
Nov 10 at 6:47