https://github.com/nuxt/nuxt.js
I can't run after I installed my dependencies
He should run normally
No parser and no filepath given, using 'babylon' the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be inferred.
Please provide solutions in a timely manner. At present, this situation has occurred in all projects, leading to the failure of all online businesses to function properly.
It is warning, not a error
@aldarund no , I simply can't run this initialized nuxt framework. This is an error !!!
@clarkdo I can't run the project extension at all. I wonder if I can get back to normal. I have been waiting for anxiety because I am doing projects for the company.
This is really bad, we can not see the output now. Try updating vue-loader they have been patched allready:
https://github.com/prettier/prettier/issues/4567
Can you try manually install [email protected]
in you project ?
Tested with vue-loader v14.2.2 and it seems to work. vue-loader v15 would be better because of its improved design, but it requires modifications to Nuxt code.
# css-loader and vue-template-compiler are added to silence peer-dependency warnings
yarn add vue-loader@^14.2.2 css-loader@* vue-template-compiler@^2.0.0
Nuxt has upgraded vue-loader to 15, 2.0 will be released soon.
a similar problem
when will version 2 release?
I also encountered the same problem, but the above reply is not very intuitive. What should I do exactly?
thanks @warriorBrian. the warning is gone.
@warriorBrian
Very good! I solved the problem, thank you very much
This question is the same as #3385
Thank you @warriorBrian
But, could someone explain to me why this is even happening in the first place? I'm working on a project with Nuxt, and earlier today everything was working as it should, but suddenly after installing a package: mailgun.js
everything went sideways. I'm trying to understand why this happened.
Could someone help?
@sebastianks I guess that because when you install mailgun package , you break locked dependency package in node_modules .
A patch release v1.4.1
for the quick fix has been published.
Most helpful comment
@Maple13
Can temporarily solve this problem