Should I merge it now? Yes.
No blocking findings.
This is a metadata cleanup for an unused pipe. Its transform method stays the same. Fresh Angular compilation and ESLint pass, and all 646 component dependency lists match the base exactly.
I would merge 27d6a631e0. No application template renders this pipe, so I found no affected user flow.
Code review
The change does what the title says
The PR removes standalone: false from BioLinkPipe in isLink.pipe.ts. Its template name is isLink. The installed Angular runtime defaults omitted pipe standalone metadata to true.
The compiled JavaScript confirms that only this pipe's standalone metadata changes. Its transform method and the other pipes in the file remain unchanged. See the changed decorator.
Creator profiles use a different BioLinkPipe
Two classes share this name. The changed class is in isLink.pipe.ts. The profile imports BioLinkPipe from cast-link.pipe.ts, whose template name is bioLink and which is already standalone.
The profile template still applies bioLink, bioFormat and hashtagFormat to the bio. This PR does not alter those imports or transformations. See the profile import and the template binding.
No consumer needs a migration
The application source has no import of the changed BioLinkPipe and no template use of | isLink. Imports from its file select CheckIsURL, RemoveURLS or SafeUrl. None imports the changed class through a namespace.
There is no NgModule declaration to remove and no component import to add. The exact match across all 646 compiled component dependency lists confirms that no template starts or stops using a pipe because of this change.
Checks run for this review
| Check | Result |
|---|---|
| Complete source diff | Pass. One decorator changes in one file. |
| Angular compilation | Pass in an isolated checkout with a 10 GB Node heap limit. |
| Compiled template dependencies | All 646 component lists match the saved PR 10841 output exactly. |
| Compiled pipe comparison | Only standalone metadata changes. Other pipes in the file match. |
| ESLint on the changed file | Pass. No errors or warnings. |
| Git whitespace check | Pass. |
The base tree at 6c60bf115b is identical to the reviewed PR 10841 head. That makes its saved compiler output a valid source baseline for this comparison.
GitHub reported this PR open and mergeable, with no status checks listed. An empty check list is not a CI pass.
Build and runtime coverage
I did not rerun full QA or development bundles, white-label builds, SSR comparisons or signed-in browser flows for this one-decorator change. The independent checks above cover source usage, compilation and lint.
The author reports passing QA and development builds, 42 QA warnings, unchanged initial JavaScript at 7,123,873 bytes and unchanged profile, messages, post-detail and dashboard lazy sizes. They also report matching server rendering over 145 URLs. I have not independently reproduced those measurements for this PR.
The author did not run a signed-in white-label sweep because no page renders this pipe. I found no source or compiler evidence that warrants holding the change for that sweep.