Closed robertpatrick closed 2 years ago
Try maybe with yarn
. It may be some peer dependencies maybe?
I have moved on to avoid the use of the axios module. Switching package managers seems like a workaround to the problem to me.
Not sure why a workaround. If NPM does the job poorly, eh can't blame on axios. 🤷🏻♂️
npm works perfectly and in some ways, is ahead of yarn. The point is that your have published a package to registry.npmjs.org that doesn't work. By the way, axios works fine. It's the axios-module that's broken. Clearly, you don't care so...
npm works perfectly and in some ways, is ahead of yarn Highly debatable on a lot of points. Anyway, PNPM is better overall.
It's not my package tbh (I'm just a random user passing by on some issues), and here it looks like a dependency resolution more than anything else but eh, since you don't really care about the module itself: no need to tryhard.
In my very simple Nuxt.js project, I used
npm install @nuxtjs/axios
and then added the following tonuxt.config.js
:when I try to run
npm run dev
, it refuses to start due to a missing module (that wasn't missing before I switched from axios to the axios module:After installing
at-least-node
andua-parser-js
to satify the missing dependencies, now I get a fatal error:Surely I must be doing something wrong...