fix(core): find imports after template literals with vars

[spalger]

Current Behavior

If you have a template literal in your code all the code between the closing backtick of your template literal, to either the end of the file or the next template literal, will be treated as a SyntaxKind.TemplateHead and therefore not scanned for imports.

Expected Behavior

All import statements in a file, regardless of the other expressions in that file, should be found.

Related Issue(s)

No issue created.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
nx-dev	✅ Ready (Inspect)	Visit Preview	Dec 27, 2022 at 4:02PM (UTC)

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit fa82d96. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 11 targets

• nx affected --target=e2e --base=d3ef0eaf7214a09709882240b736a5a50c970864 --head=fa82d96508c7aacd8d47f84db67b207089d17ead --exclude=e2e-storybook,e2e-storybook-angular,e2e-react-native,e2e-detox --parallel=1
• nx affected --target=test --base=d3ef0eaf7214a09709882240b736a5a50c970864 --head=fa82d96508c7aacd8d47f84db67b207089d17ead --parallel=1
• nx affected --target=build --base=d3ef0eaf7214a09709882240b736a5a50c970864 --head=fa82d96508c7aacd8d47f84db67b207089d17ead --parallel=3
• nx depcheck --no-dte
• nx affected --target=lint --base=d3ef0eaf7214a09709882240b736a5a50c970864 --head=fa82d96508c7aacd8d47f84db67b207089d17ead --parallel=3
• nx lint --no-dte
• nx check-lock-files --no-dte
• nx check-commit --no-dte
• nx-cloud record -- nx format:check --base=d3ef0eaf7214a09709882240b736a5a50c970864 --head=fa82d96508c7aacd8d47f84db67b207089d17ead
• nx check-imports --no-dte
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

[spalger]

Thanks @AgentEnder, would you mind taking a look at #13921 too?

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.