Fix missing i18n path configuration

[Tenchi2xh]

No description provided.

[mdvanes]

I don't think this will work, because the environmental variable will exist server side and this code is client side. Instead, it would have to be replaced in the build step.

[Tenchi2xh]

Didn't think about that, so I looked into it, apparently it could work.

This says that the static %PUBLIC_URL% are substituted even client-side, and then say that process.env.PUBLIC_URL acts the same for the JS side.

I still wasn't convinced by that but then I read this comment on an issue:

Thanks. It's a bit surprising that what looks like a node.js process environment variable is available on the client.

It's a very common practice called "envifying".

What does 'process.env' represent, logically? A snapshot of what the node.js process environment was when webpack ran?

Yes.

Apparently, it will capture this:

  "homepage": "http://www.codestar.nl/codestar-website-react"

from our package.json as that PUBLIC_URL variable.

Should we try?

[mdvanes]

Ah ok, it works because of magic. Sure lets merge it in.

[Tenchi2xh]

It worked :)