fix(vue-app): always import error layout, either internal or custom

[danielroe]

closes #8066

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

The client template needs access to NuxtError and we can follow the pattern of App.js - thanks #8066 (comment) for a helpful diagnosis of the issue.

For reference:

• fix(vue-app): error page layout not correctly applied in client rendering #6479 (original source of NuxtError import)
• fix(vue-app): missing layout in error page with splittedChunks.layout #8016 (PR introducing regression that this fixes)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly. (PR: #)
• I have added tests to cover my changes (if not applicable, please state why)
• All new and existing tests are passing.

[codecov-commenter]

Codecov Report

Merging #8067 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #8067   +/-   ##
=======================================
  Coverage   68.98%   68.98%           
=======================================
  Files          91       91           
  Lines        3847     3847           
  Branches     1047     1047           
=======================================
  Hits         2654     2654           
  Misses        969      969           
  Partials      224      224           

Flag	Coverage Δ
#unittests	68.98% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 45b7838...d8eca35. Read the comment docs.

[pi0]

Thanks!

[aeadedoyin]

Hi @pi0 When will this be released? Asper 2.14.6

[Kolobok12309]

@danielroe, Thanks for fix this bug, my fail

[danielroe]

@Kolobok12309 Not at all! It was a good PR and we just didn't spot the issue...