https://github.com/yoyo837/nuxt-3392
See https://github.com/nuxt/nuxt.js/pull/3392#issuecomment-393863232
HTML minify work fine.
It report error.
@pi0 I have new discoveries:
Using yarn install dependencies does not work, but npm can.
Yarn: 1.7.0
Node: 8.11.1
Strange things. For me it works fine on my real project with latest nuxt-edge. But the example above just give empty error message. All with yarn
https://i.imgur.com/TDeLt96.png
@aldarund Please take a look at what is wrong with your page, not just console.
@yoyo837 ye i see it now. Although still all works fine with my real project with same version of nuxt :))
@aldarund Are you sure all with yarn?And what’s the version of yarn?
@yoyo837 yes, all with yarn. Im sure because i did a lot of full delete & reinstall yesterday
1.7.0
Encountered the same issue today
I encountered this and it seems to have been related to an older version of the html-minifier package. Forcing an update to the latest version seems to resolve it. In my case 3.5.10 was specified in my package-lock.json and now I'm using 3.5.16.
Cannot reproduce this with [email protected]. If you can, please ping me @tim-yao
No,This problem still exists until now. I'm very sure.

@yoyo837 reopened.
@yoyo837 Can't reproduce it with your repo linked in the issues and after updating :thinking:
Could you give a details reproduction instruction?
@manniL That is a repo small enough to reproduce the problem. This is caused by the #3392 merged, but that PR is trying to fix another issue. Now I'm not sure whether it should be revert.
I have been having this problem since that PR was merged, every time.
@yoyo837 I cloned the repo, updated the dependencies and was able to build nuxt without problems.
See comment: https://github.com/nuxt/nuxt.js/issues/3411#issuecomment-394224616
Which pkg manager do you use? npm or yarn ? Use npm is work fine.
Missed the comment. However, if NPM works but yarn doesn't, are you sure it's a Nuxt bug then?
@mannil well, even if it's yarn bug it still should work for people who are using yarn via some workaround. It also might be a bug in npm that make it work fine, but not as it should :)
It must be something with resolving nested dependency difference on yarn vs npm
Will look into it
yarn upgrade
This command can make it work fine.
This bug-report has been fixed by @Atinux, @aldarund, @yoyo837, @manniL.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Most helpful comment
@mannil well, even if it's yarn bug it still should work for people who are using yarn via some workaround. It also might be a bug in npm that make it work fine, but not as it should :)
It must be something with resolving nested dependency difference on yarn vs npm