Skip to content
Browse files

Fix route template path handling (#1253)

Consider that we store the artifacts on an OS temporary directory (such
as what you would get with `mktemp -d` or `node-tmp`) which we can
assume for simplicity purposes to be `/tmp/react-static`.

In the snippet above, `route.template` is a path such as
`/home/johndoe/site/lib/pages/main.js`. Therefore `path.relative()` will
calculate the path to `/home/johndoe/site/lib/pages/main.js` from
`/tmp/react-static`, so the result will be something like
`../home/johndoe/site/lib/pages/main.js` which makes no sense and will
cause react-static to fail.

What we really intended is `path.resolve()`, so that the user still gets
  • Loading branch information...
jviotti authored and SleeplessByte committed Jul 18, 2019
1 parent 111045e commit 7cf575a16e7a3c2a4b773c74390fd1a10f02164e
Showing with 3 additions and 1 deletion.
  1. +3 −1 packages/react-static/src/static/extractTemplates.js
@@ -16,9 +16,11 @@ export default (async function extractTemplates(state) {
if (!route.template) {

route.template = slash(
path.relative(config.paths.ARTIFACTS, route.template)
path.resolve(config.paths.ARTIFACTS, route.template)

// Check if the template has already been added
const index = templates.indexOf(route.template)
if (index === -1) {

0 comments on commit 7cf575a

Please sign in to comment.
You can’t perform that action at this time.