Randomized import name leads to non-deterministic builds

[davidtaylorhq]

As part of its transformation, content-tag introduces a new es6 import like

import { template as template_fd9b2463e5f141cfb5666b64daa1f11a } from "@ember/template-compiler";

The local name is a randomised UUID which changes every time content-tag is called:

content-tag/src/lib.rs

Lines 123 to 127 in 44d8b16

	let id = private_ident!(format!(
	"{}_{}",
	target_specifier,
	Uuid::new_v4().to_string().replace("-", "")
	));

This randomisation makes the build output different each time, which means that bundled chunks get given different hashes, and end-users get no cache-reuse between deploys of our application.

It would be great if the import name could be made deterministic. Either by picking a pseudo-random identifier which is extremely unlikely to be used in user-space (like decorator-transforms). Or by adding logic to check for existing identifiers in the file, and pick something which does not clash.