Asset in template is not fingerprinted in production

Using current ember-cli-fastboot master.

If I have a template with an image, it refers to the unfingerprinted asset.

Input:

<img src="/assets/foo.png">

Output:

<img src="/assets/foo.png">

Expected:

<img src="/assets/foo-SomeHash.png">

See: topaxi.ch The puzzle.png image Or the repository: https://github.com/topaxi/topaxi.ch

Once the the page loads, the browser build correctly uses the fingerprinted asset.

[jasonmit]

https://github.com/tildeio/ember-cli-fastboot/blob/master/lib/broccoli/fastboot-build.js#L35

buildFastBootTree only asset revs over the javascript tree, so it doesn’t take into account anything in the public tree which is why it misses foo.png.

I worked around this by including the full emberApp.proto.toArray sourceTree. That’s when I also uncovered that everything in the root of /public (robots.txt, crossdomain.xml, etc.) isn’t served up by the fastboot server.

Unsure how to resolve this without resolving the new bug I stumbled on.

[ballPointPenguin]

not sure if this is the same issue, but I see 404s on my fingerprinted css and js assets despite the fact that the ember app is running correctly

UPDATE I just downgraded from node 6 to node 5 and the 404’s went away.