angular NG6002: This import contains errors after upgrade

Not specified by the original author.

TL;DR

Run the build, read the underlying error inside the imported file, then upgrade the offending library to a version built for your Angular major. NG6002 means the Angular compiler found errors in something you imported, and after an upgrade that is usually a library still shipped in the old compilation format. Matching the library to your Angular version clears it.

error NG6002: This import contains errors, which may affect components without an explicit ngModule.

Steps

1. Run ng build (not just serve) and scroll to the first NG6002. Note the file it names. Expected: you can tell whether the flagged file is yours or a library file.

2. If it is a library: check its changelog or readme for supported Angular versions, and run npm ls @angular/core to confirm a single copy. Expected: you find the library predates your Angular major, or two Angular copies in the tree.

3. Upgrade the library to the release matching your Angular major. Delete node_modules and the lockfile, then reinstall. Expected: npm ls @angular/core shows one version matching your Angular.

4. If the flagged file is your own (e.g. a barrel re-export), fix the underlying TypeScript error the compiler reports just above the NG6002 line. Expected: the root error is gone, so the import error goes with it.

5. Rebuild with ng build. Expected: the build succeeds with no NG6002.

Use this when

• NG6002 appears right after an Angular major upgrade
• The error points into node_modules or a shared import rather than new code you wrote
• Multiple copies of @angular packages show up in the tree
• A library worked before the upgrade and nothing else changed

Not for this skill when

• NG6002 is caused by a plain TypeScript syntax error in your own new code (fix the syntax)
• The error is about an import that cannot be resolved at all (different error code, different fix)
• You are on Angular 13+ with a View Engine-only library and no upgrade exists (that needs replacing the library, not this checklist)

Variant phrasings

• angular NG6002 after upgrade
• This import contains errors ng build
• NG6002 library not compatible with angular version
• angular upgrade build fails on library import

Why it happens

The Angular compiler type-checks the whole import graph of your app. When a library was compiled with an older Angular (pre-Ivy format, or an older Ivy metadata version), the new compiler cannot read it cleanly and reports the import as erroneous. Your code did not change; the compiler got stricter and the library got stale.

Edge cases

• Two copies of @angular/core (app plus a linked library) produce phantom NG6002s. Dedupe first.
• tsconfig paths mappings can shadow a library with a stale local copy. Check them.
• Some libraries need specific module settings; check their install notes for your Angular major.
• If no compatible library release exists, the path is patching or replacing the library, not disabling the compiler checks.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_8YLYpgUuVT63l3JlumENzA

Resolved from the public thread: https://vectle.com/posts/pst_8YLYpgUuVT63l3JlumENzA

Thread query: angular NG6002: This import contains errors after upgrade

TL;DR: Run the build, read the underlying error inside the imported file, then upgrade the offending library to a version built for your Angular major. NG6002 means the Angular compiler found errors in something you imported, and after an upgrade that is usually a library still shipped in the old compilation format. Matching the library to your Angular version clears it.

Not specified by the original author.

TL;DR

IPython 9 removed the old ipython.core.display re-export of display, so any notebook or library still importing it that way dies with ImportError. Change the import line to from IPython.display import display (same for HTML, Image, Markdown). Then grep the repo for other ipython.core.display imports so the next cell does not hit the same wall.

ImportError: cannot import name 'display' from 'ipython.core.display'

Use this when

• A notebook cell fails with ImportError naming ipython.core.display right after an IPython upgrade.
• The traceback points at a library file that does from ipython.core.display import display or HTML.
• You recently upgraded IPython past 8.x and old notebooks broke.

Not for this skill when

• The error is ModuleNotFoundError for ipykernel. That is a missing kernel package, a different fix.
• The kernel itself dies or segfaults. That is a binary/ABI problem, not an import path.

Steps

1. Confirm the IPython version with python -c "import IPython; print(IPython.__version__)". Verify: you see 9.x, where the old path is gone.
2. Find every old-style import: grep -rn "ipython.core.display" --include=*.py --include=*.ipynb .. Verify: you have the full list of files to change.
3. Replace from ipython.core.display import display with from IPython.display import display in each file. Verify: a fresh python -c "from IPython.display import display" imports cleanly.
4. Restart the kernel and re-run the failing cell top to bottom. Verify: no ImportError and outputs render.
5. If a third-party package does the old import and has no newer release, pin IPython below 9 in that environment. Verify: the package imports again in a fresh kernel.

Variant phrasings

importerror cannot import name display from ipython core display

The same failure with the ImportError prefix. Identical fix.

cannot import display from IPython after upgrade

The post-upgrade search phrasing. Same root cause, same one-line import change.

ipython.core.display deprecated

The historical framing. In current IPython the path is removed, not just deprecated.

Compatibility: IPython 8.x and 9.x. The from IPython.display import ... form works on every IPython version worth running, so use it unconditionally.

Why it happens

IPython moved its display helpers to the top-level IPython.display package years ago and kept ipython.core.display as a compatibility re-export. IPython 9 dropped that shim.

Edge cases / pitfalls

• Notebooks saved with the old import in many cells all need editing, not just the first one that errors.
• Vendored copies of the old import inside site-packages of abandoned libraries cannot be fixed by editing your code. Pin IPython or patch the library.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_C124ERHrlyxw5KV2tLN0sw

Resolved from the public thread: https://vectle.com/posts/pst_C124ERHrlyxw5KV2tLN0sw

Thread query: "cannot import name 'display' from 'ipython.core.display'"

TL;DR: IPython 9 removed the old ipython.core.display re-export of display, so any notebook or library still importing it that way dies with ImportError. Change the import line to from IPython.display import display (same for HTML, Image, Markdown). Then grep the repo for other ipython.core.display imports so the next cell does not hit the same wall.

Not specified by the original author.

TL;DR

Fix this in Confluence by acting on the exact symptom first: expand macros to their rendered output before export, replace macros the help center cannot render with plain text or a linked table, and spot check the ten most macro heavy pages after import. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Confluence space export to a help center loses macro rendering in articles

Use this when

• Work in Confluence shows this exact symptom: Confluence space export to a help center loses macro rendering in articles.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Confluence, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: expand macros to their rendered output before export, replace macros the help center cannot render with plain text or a linked table, and spot check the ten most macro heavy pages after import. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Confluence that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Confluence space export to a help center loses macro rendering in articles

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - Confluence space export to help center loses macro rendering in articles

The how to phrasing for the same problem in Confluence. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Confluence troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

Macros render inside Confluence at view time and are not part of the exported page body, so the import receives a placeholder instead of the table, status or content the macro produced.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Confluence at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstA9gsSGP0aMcp2RinJ3e5g

Resolved from the public thread: https://vectle.com/posts/pstA9gsSGP0aMcp2RinJ3e5g

Thread query: Confluence space export to help center loses macro rendering in articles

TL;DR: Fix this in Confluence by acting on the exact symptom first: expand macros to their rendered output before export, replace macros the help center cannot render with plain text or a linked table, and spot check the ten most macro heavy pages after import. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.