Question: I cannot add images to my GitHub pages, I've tried a lot of solutions I found on the internet, such as

```
![LSTM]({{ site.url }}/{{ site.baseurl }}/docs/images/LSTM/lstm-unit.png)
![lstm unit]({{ site.baseurl }}/docs/images/LSTM/lstm-unit.png)
![lstm unit]({{ site.url }}/docs/images/LSTM/lstm-unit.png)

```

nothing works. 
The error I received most is

> 
> '/blog/docs/images/LSTM/lstm-unit.png' not found.
> 
> 
> 

The strangest thing is when I use

```
![lstm unit](../images/LSTM/lstm-unit.png)

```

I get an error 

> 
> `/blog/machine learning/images/LSTM/lstm-unit.png' not found.
> 
> 
> 

But I don't have any `/blog/machine learning` directory. I guess it has something to do with my setting the categories and tags to `machine learning` in the input YAML Front Matter. So I tried to remove them, then I cannot open my essay on the Jekyll service at all. It says

> 
> `/blog/machine learning/LSTM-and-its-variants/' not found.
> 
> 
> 

but I put my essay in `docs/_posts`...

What on earth is going on here? Please help me sort this out, Thanks.
In case you need, my GitHub is built on `docs` directory, and images are in `docs/images/LSTM/` directory

UPDATE
------

Finally, I got it worked by using below code

```
![LSTM]({{ '/images/lstm/architecture.png' | absolute_url }})

```

This is quite different from the solutions I found online, is anybody could help me explain it?

Answer: 
**EDIT: As of Cloud Next 2018, Cloud Functions has exited beta. There is node 8 support now, but it is currently in beta.**

There are a number of things to keep in mind.

Cloud Functions will only use a version of node with LTS (Long Term Support). Only even number versions of node receive LTS.

Cloud Functions is in beta, and the engineering team has more important priorities than providing a new version of node. It's a priority to get to production readiness, and that doesn't necessarily involve having the latest version of node.

It's not feasible to simply drop in a new major version, as that might break existing clients. It will probably have to be the case that each project can select the version of node they would like to use, and that's a significant change.

You are able to use any language that you want that can transpile to ES6. This includes TypeScript and even Kotlin, if you wish. [The Firebase CLI supports TypeScript directly](https://firebase.google.com/docs/functions/typescript), and has for a few months now. TypeScript is actually the Firebase team's recommended development language.

If you want to stay on top of the latest languages for Cloud Functions development, I strongly recommend that you not depend on the version of node. Instead, select tooling that can transpile to ES6.
Firebase Cloud Functions now supports Node 8. Instructions on how to upgrade: [Cloud Functions: Migrating to Node 8](https://howtofirebase.com/cloud-functions-migrating-to-node-8-9640731a8acc).

Update: [Official announcement and instructions](https://firebase.googleblog.com/2018/08/cloud-functions-for-firebase-config-node-8-timeout-memory-region.html).