fix(compiler-cli): detect when the linker is working in unpublished angular and widen supported versions

[josephperrott]

When the linker is running using an unpublished version of angular, locally built, the version will be 0.0.0. When encountering this situation, the range that for the linker map support is considered to be *.*.* allowing for the linker to work at build time with packages built with versioned angular.

Most notably this allows for us to properly use the linker in building our documentation site with the locally built version of angular.

[JoostK]

Devtools has the same use-case, where it's being made to work by ignoring the warning:

angular/devtools/tools/esbuild/esbuild-base.config.mjs

Lines 45 to 55 in aee526a

	// DevTools relies on angular framework packages that are consumed,
	// locally via bazel. These packages have a version of 0.0.0-PLACEHOLDER.
	// DevTools also relies on Angular CDK and Material packages that are consumed via npm.
	// Because of this, we set unknownDeclarationVersionHandling to ignore so that we bypass
	// selecting a linker for our CDK and Material dependencies based on our local framework
	// version (0.0.0-PLACEHOLDER).
	// Instead this option defaults to the latest linker version, which should
	// be correct, except for the small time interval where we rollout a new
	// declaration version and target a material release that hasn't been compiled
	// with that version yet.
	unknownDeclarationVersionHandling: 'ignore',

There's also currently this logic, which I think wouldn't be needed with this change:

angular/packages/compiler-cli/linker/src/file_linker/partial_linkers/partial_linker_selector.ts

Lines 147 to 151 in 9acd2ac

	if (version === PLACEHOLDER_VERSION) {
	// Special case if the `version` is the same as the current compiler version.
	// This helps with compliance tests where the version placeholders have not been replaced.
	return linkerRanges[linkerRanges.length - 1].linker;
	}

EDIT: the above concerns the PLACEHOLDER version, not the substituted 0.0.0 version, so is irrelevant w.r.t. this change.

[JoostK]

Where does the 0.0.0 come from exactly, as the version for HEAD is suffixed with -PLACEHOLDER

[josephperrott]

0.0.0 is stamped from during the packaging, with 0.0.0 being the replacement when we are not "stamping" and the actual version stamping when we --stamp:

angular/tools/defaults.bzl

Lines 238 to 243 in ed0d5ec

	substitutions = dict(common_substitutions, **{
	"0.0.0-PLACEHOLDER": "0.0.0",
	})
	stamped_substitutions = dict(common_substitutions, **{
	"0.0.0-PLACEHOLDER": "{STABLE_PROJECT_VERSION}",
	})

[JoostK]

Ah, thanks for the reference! I wasn't aware of this behavior.

[AndrewKushnir]

This PR was merged into the repository by commit da7fbb4.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}