From d13b5e230b645dfccd3371de64cab6b9c7ee473d Mon Sep 17 00:00:00 2001
From: Robert Jackson <rjackson@linkedin.com>
Date: Fri, 8 May 2020 09:36:29 -0400
Subject: [PATCH] Ensure custom templateCompilerPath is an absolute path.

The examples that we show for using a custom template compiler path use
a relative path, but that doesn't actually work when inline compilation
runs and is parallelized (because the worker processes run from a
different relative root inside `/tmp`).

This ensures that any specified overrides are converted to absolute
paths.
---
 lib/ember-addon-main.js | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/lib/ember-addon-main.js b/lib/ember-addon-main.js
index b3c36ed7..d945fbb2 100644
--- a/lib/ember-addon-main.js
+++ b/lib/ember-addon-main.js
@@ -1,5 +1,6 @@
 'use strict';
 
+const path = require('path');
 const SilentError = require('silent-error');
 const utils = require('./utils');
 
@@ -201,7 +202,7 @@ module.exports = {
       app.options['ember-cli-htmlbars'].templateCompilerPath;
 
     if (templateCompilerPath) {
-      return templateCompilerPath;
+      return path.resolve(this.project.root, templateCompilerPath);
     }
 
     let ember = this.project.findAddonByName('ember-source');