!repo-banner

After.js

   !Github Actions  !After-status  

If Next.js and React Router had a baby...

Project Goals / Philosophy / Requirements

Next.js is awesome. However, its routing system isn't for me. IMHO React Router is a better foundation upon which such a framework should be built....and that's the goal here:

- Routes are just components and don't / should not have anything to do with folder structure. Static route configs are fine.
- Next.js's getInitialProps was/is a brilliant idea.
- Route-based code-splitting should come for free or be easy to opt into.
- Route-based transitions / analytics / data loading / preloading etc. , should either come for free or be trivial to implement on your own.

Table of Contents

- After.js
- Project Goals / Philosophy / Requirements
- Getting Started with After.js
- Quickstart
- Data Fetching
- getInitialProps: (ctx) => Data
- Add Params to getInitialProps: (ctx) => Data
- Injected Page Props
- Routing
- Parameterized Routing
- Client Only Data and Routing
- Transition Behavior
- Dynamic 404 and Redirects
- 404 Page
- Dynamic 404
- Redirect
- Code Splitting
- Static Site Generation (SSG)
- Disable Auto-Scroll Globally
- Disable Auto-Scroll for a Specific Page
- Custom
- Custom/Async Rendering
- Author
- Inspiration

Getting Started with After.js

After.js enables Next.js-like data fetching with any React SSR app that uses React Router.

$3

You can quickly bootstrap an SSR React app with After.js using Razzle. While Razzle is not required, this documentation assumes you have the tooling setup for an isomorphic React application.

``bash
yarn global add create-after-app
create-after-app myapp
cd myapp
yarn start
`

Refer to Razzle's docs for tooling, babel, and webpack customization.

Data Fetching

For page components, you can add a static async getInitialProps function.
This will be called on both initial server render, and then client mounts.
Results are made available on this.props.

`js
// ./src/About.js
import React from 'react';
import { NavLink } from 'react-router-dom';

class About extends React.Component {
static async getInitialProps({ req, res, match }) {
const stuff = await CallMyApi();
return { stuff };
}

render() {
return (


export default About;
`

$3

Within getInitialProps, you have access to all you need to fetch data on both
the client and the server:

- req?: Request: (server-only) An Express.js request object.
- res?: Response: (server-only) An Express.js response object.
- match: React Router's match object.
- history: React Router's history object.
- location: (client-only) React Router's location object (you can only use location.pathname on server).
- scrollToTop: React Ref object that controls scroll behavior when URL changes.

$3

You can extend ctx, and pass your custom params to it. this is useful when you want to fetch some data by condition or store fetched data in a global state managment system (like redux) or you may need to pass those params as props to your component from server.js (e.g result of user agent parsing).

`js
// ./src/server.js
...
try {
const html = await render({
req,
res,
routes,
chunks,
// Anything else you add here will be made available
// within getInitialProps(ctx)
// e.g a redux store...
customThing: 'thing',
});
res.send(html);
} catch (error) {
console.error(error);
res.json({ message: error.message, stack: error.stack });
}
...
`

Don't forget to pass your custom params to in client.js:

`js
// ./src/client.js
...
ensureReady({ routes }).then(data =>
hydrate(

{/*
Anything else you pass to will be made available
within getInitialProps(ctx)
e.g a redux store...
*/}

,
document.getElementById('root')
)
);
...
`

$3

- Whatever you have returned in getInitialProps
- prefetch: (pathname: string) => void - Imperatively prefetch _and cache_ data for a path. Under the hood this will map through your route tree, call the matching route's getInitialProps, store it, and then provide it to your page component. If the user ultimately navigates to that path, the data and component will be ready ahead of time. In the future, there may be more options to control cache behavior in the form of a function or time in milliseconds to keep that data around.
- refetch: (nextCtx?: any) => void - Imperatively call getInitialProps again
- isLoading - It shows that if the returned promise from getInitialProps is in the pending state or not

Routing

As you have probably figured out, React Router powers all of After.js's
routing. You can use any and all parts of RR.

$3

`js
// ./src/routes.js
import Home from './Home';
import About from './About';
import Detail from './Detail';

// Internally these will become:
// } />
const routes = [
{
path: '/',
exact: true,
component: Home,
},
{
path: '/about',
component: About,
},
{
path: '/detail/:id',
component: Detail,
},
];

export default routes;
`

`js
// ./src/Detail.js
import React from 'react';
import { Route } from 'react-router-dom';

class Detail extends React.Component {
// Notice that this will be called for
// /detail/:id
// /detail/:id/more
// /detail/:id/other
static async getInitialProps({ req, res, match }) {
const item = await CallMyApi(/v1/item${match.params.id});
return { item };
}

render() {
return (


export default Detail;
`

$3

In some parts of your application, you may not need server data fetching at all
(e.g. settings). With After.js, you just use React Router 4 as you normally
would in client land: You can fetch data (in componentDidMount) and do routing
the same exact way.

Transition Behavior

By default, after.js will wait for getInitialProps to get resolved or rejected, so when the getInitialProps job is complete, it will show the next page. We call this behavior blocked.

You may want to show the next page with a skeleton or a spinner while getInitialProps is pending. We call this behavior instant.

you can switch to instant behavior by passing a prop to .

`js
// ./src/client.js

// transitionBehavior = blocked | instant

ensureReady({ routes }).then(data =>
hydrate(


,
document.getElementById('root')
)
);
`

Dynamic 404 and Redirects

$3

React Router can detect No Match (404) Routes and show a fallback component, you can define your custom fallback component in routes.js file.

`js
// ./src/routes.js

import React from 'react';
import Home from './Home';
import Notfound from './Notfound';
import { asyncComponent } from '@deviousm/after';

export default [
// normal route
{
path: '/',
exact: true,
component: Home,
},
// 404 route
{
// there is no need to declare path variable
// react router will pick this component as fallback
component: Notfound,
},
];
`

Notfound component must set staticContext.statusCode to 404 so express can set response status code more info.

`js
// ./src/Notfound.js

import React from 'react';
import { Route } from 'react-router-dom';

function NotFound() {
return (
render={({ staticContext }) => {
if (staticContext) staticContext.statusCode = 404;
return

export default NotFound;
`

if you don't declare 404 component in routes.js After.js will use its default fallback.

$3

Sometimes you may need to send a 404 response based on some API response, in this case, react-router don't show fallback and you have to check for that in your component.

`js
import Notfound from './Notfound';

function ProductPage({ product, error }) {
if (error) {
if (error.response.status === 404) {
return ;
}

return

Something went Wrong !

ProductPage.getInitialProps = async ({ match }) => {
try {
const { data } = await fetchProduct(match.params.slug);
return { product: data };
} catch (error) {
return { error };
}
};
`

this makes code unreadable and hard to maintain. after.js makes this easy by providing an API for handling Dynamic 404 pages. you can return { statusCode: 404 } from getInitialProps and after.js will show 404 fallback components that you defined in routes.js for you.

`js
function ProductPage({ product }) {
return

{product.name}

ProductPage.getInitialProps = async ({ match }) => {
try {
const { data } = await fetchProduct(match.params.slug);
return { product: data };
} catch (error) {
if (error.response.status === 404) return { statusCode: 404 };
return { error };
}
};
`

$3

You can redirect the user to another route by using Redirect from react-router, but it can make your code unreadable and hard to maintain.
with after.js you can redirect client to other route by returning { redirectTo: "/new-location" } from getInitialProps.
this can become handy for authorization when user does not have permission to access a specific route and you can redirect him/her to the login page.

`js
Dashboard.getInitialProps = async ({ match }) => {
try {
const { data } = await fetchProfile();
return { data };
} catch (error) {
if (error.response.status === 401) return { redirectTo: '/login' };
return { error };
}
};
`

The redirect will happen before after.js start renders react to string soo it's fast.
when using redirectTo default value for statusCode is 301, but you can use any numeric value you want.

Code Splitting

After.js lets you easily define lazy-loaded or code-split routes in your _routes.js file. To do this, you'll need to modify the relevant route's component definition like so:

`js
// ./src/_routes.js
import React from 'react';
import Home from './Home';
import { asyncComponent } from '@deviousm/after';

export default [
// normal route
{
path: '/',
exact: true,
component: Home,
},
// codesplit route
{
path: '/about',
exact: true,
component: asyncComponent({
loader: () => import('./About'), // required
Placeholder: () =>

renderStatic will return the data from getInitialProps and this data will get saved by razzle into a file called page-data.json. After.js won't call getInitialProps at runtime, instead it will read the page-data.json and pass it as a prop to your component.

from ./src/static_export.js you should export render and routes function.

- async render(req, res) should render your app into html and at the end it should return html and data.
- async routes() should return path for pages you want to statically generate.

`js
// ./src/static_export.js

import { renderStatic } from '@deviousm/after';
import appRoutes from './routes';

const assets = require(process.env.RAZZLE_ASSETS_MANIFEST);
const chunks = require(process.env.RAZZLE_CHUNKS_MANIFEST);

export const render = async (req, res) => {
const { html, data } = await renderStatic({
req,
res,
routes: appRoutes,
assets,
chunks,
});
res.json({ html, data });
};

export const routes = async () => {
return ['/', '/about'];
};
`

after setting up this file you can build your app and run export script to generate your static site:

`bash
yarn build
yarn export
`

> for full documentation and advanced configuration visit: https://razzlejs.org/docs/static-export

Disable Auto-Scroll Globally

By default, After.js will scroll to top when URL changes, you can change that by passing scrollToTop: false to render().

`js
// ./src/server.js

const scrollToTop = false;

const html = await render({
req,
res,
routes,
chunks,
scrollToTop,
});
`

Disable Auto-Scroll for a Specific Page

We are using a ref object to minimize unnecessary re-renders, you can mutate scrollToTop.current and component will not re-rendered but its scroll behavior will change immediately.
You can control auto-scroll behavior from getInitialProps.

`js
class MyComponent extends React.Component {
static async getInitialProps({ scrollToTop }) {
scrollToTop.current = false;
return { scrollToTop, stuff: 'whatevs' };
}

render() {
return

Hello, World!

componentWillUnmount() {
this.props.scrollToTop.current = true; // at the end restore scroll behavior
}
}
`

Custom

After.js works similarly to Next.js with respect to overriding HTML document structure. This comes in handy if you are using a CSS-in-JS library or just want to collect data out of react context before or after render. To do this, create a file in ./src/Document.js like so:

`js
// ./src/Document.js
import React from 'react';
import {
AfterRoot,
AfterData,
AfterScripts,
AfterStyles,
} from '@deviousm/after';

class Document extends React.Component {
static async getInitialProps({ renderPage }) {
const page = await renderPage();
return { ...page };
}

render() {
const { helmet } = this.props;
// get attributes from React Helmet
const htmlAttrs = helmet.htmlAttributes.toComponent();
const bodyAttrs = helmet.bodyAttributes.toComponent();

return (






{helmet.title.toComponent()}
{helmet.meta.toComponent()}
{helmet.link.toComponent()}








);
}
}

export default Document;
`

If you were using something like styled-components, and you need to wrap you entire app with some sort of additional provider or function, you can do this with renderPage().

`js
// ./src/Document.js
import React from 'react';
import { ServerStyleSheet } from 'styled-components';
import { AfterRoot, AfterData, AfterScripts } from '@deviousm/after';

export default class Document extends React.Component {
static async getInitialProps({ renderPage }) {
const sheet = new ServerStyleSheet();
const page = await renderPage(App => props =>
sheet.collectStyles()
);
const styleTags = sheet.getStyleElement();
return { ...page, styleTags };
}

render() {
const { helmet, styleTags } = this.props;
// get attributes from React Helmet
const htmlAttrs = helmet.htmlAttributes.toComponent();
const bodyAttrs = helmet.bodyAttributes.toComponent();

return (




{helmet.title.toComponent()}
{helmet.meta.toComponent()}
{helmet.link.toComponent()}
{/ here is where we put our Styled Components styleTags... /}
{styleTags}







);
}
}
`

To use your custom , pass it to the Document option of your After.js render function.

`js
// ./src/server.js
import express from 'express';
import { render } from '@deviousm/after';
import routes from './routes';
import MyDocument from './Document';

const chunks = require(process.env.RAZZLE_CHUNKS_MANIFEST);

const server = express();
server
.disable('x-powered-by')
.use(express.static(process.env.RAZZLE_PUBLIC_DIR))
.get('/*', async (req, res) => {
try {
// Pass document in here.
const html = await render({
req,
res,
document: MyDocument,
chunks,
routes,
});
res.send(html);
} catch (error) {
console.error(error);
res.json({ message: error.message, stack: error.stack });
}
});

export default server;
`

Custom/Async Rendering

You can provide a custom (potentially async) rendering function as an option to After.js render function.

If present, it will be used instead of the default ReactDOMServer renderToString function.

It has to return an object of shape { html : string!, ...otherProps }, in which html will be used as the rendered string

Thus, setting customRenderer = (node) => ({ html: ReactDOMServer.renderToString(node) }) is the the same as default option.

otherProps will be passed as props to the rendered Document

Example :

`js
// ./src/server.js
import React from 'react';
import express from 'express';
import { render } from '@deviousm/after';
import { renderToString } from 'react-dom/server';
import { ApolloProvider, getDataFromTree } from 'react-apollo';
import routes from './routes';
import createApolloClient from './createApolloClient';
import Document from './Document';

const chunks = require(process.env.RAZZLE_CHUNKS_MANIFEST);

const server = express();
server
.disable('x-powered-by')
.use(express.static(process.env.RAZZLE_PUBLIC_DIR))
.get('/*', async (req, res) => {
const client = createApolloClient({ ssrMode: true });

const customRenderer = node => {
const App = {node};
return getDataFromTree(App).then(() => {
const initialApolloState = client.extract();
const html = renderToString(App);
return { html, initialApolloState };
});
};

try {
const html = await render({
req,
res,
routes,
chunks,
customRenderer,
document: Document,
});
res.send(html);
} catch (error) {
console.error(error);
res.json({ message: error.message, stack: error.stack });
}
});

export default server;
``

Author

- Jared Palmer @jaredpalmer

Inspiration

- Razzle
- Next.js

---

> MIT License