Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot find @vue/cli-plugin-babel@^3.1.1 #2879

Closed
johnsardine opened this issue Nov 2, 2018 · 15 comments
Closed

Cannot find @vue/cli-plugin-babel@^3.1.1 #2879

johnsardine opened this issue Nov 2, 2018 · 15 comments

Comments

@johnsardine
Copy link

johnsardine commented Nov 2, 2018

Version

3.1.1

Reproduction link

https://gist.github.com/johnsardine/830a1abd0a7fee649724c6c04feb6eb5

Node and OS info

Node 9.11.1 / npm 5.6.0 / OSX 10.14

Steps to reproduce

Copy package.json from gist provided. Run npm i

What is expected?

The project should install correctly

What is actually happening?

Vue CLI v3.1.1
✨  Creating project in /Users/sardinha/Dev/project.
⚙ Installing CLI plugins. This might take a while...

npm ERR! code ETARGET
npm ERR! notarget No matching version found for @vue/cli-plugin-babel@^3.1.1
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'project'
npm ERR! notarget

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/sardinha/.npm/_logs/2018-11-02T16_07_23_412Z-debug.log
 ERROR  command failed: npm install --loglevel error
@dasDaniel
Copy link

dasDaniel commented Nov 2, 2018

same on

Windows 10 / Node 10.13.0 / NPM 6.4.1

it then gives choice to install older version through selection and freezes after selection

It looks like 3.1.1 has only been on npm for 2 hours, so maybe the other dependencies are going to be up soon. For now using npm install -g @vue/cli@^3.1.0

@alexmayerlab
Copy link

same on
node v8.11.3
npm 6.4.1

npm ERR! code ETARGET
npm ERR! notarget No matching version found for @vue/cli-plugin-babel@^3.1.1
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'smmart'
npm ERR! notarget

@dasDaniel
Copy link

looks like it was just added, (20 min ago)

note discreprency between dates and versions on npm

https://www.npmjs.com/search?q=vue%20cli
and
https://www.npmjs.com/package/@vue/cli-plugin-babel

@LinusBorg
Copy link
Member

Seems like npm had some issues with the latest release, but it's resolved now.

@JosephIbe
Copy link

I am still facing this issue with v3.1.2 but it works when i downgrade to v3.1.0 (with a warning that thise version is no longer maintained). Is this the only work-around or a temporary bug in latest version?

@GreggOD
Copy link

GreggOD commented Nov 27, 2018

I have figured my issues are down to NVM and locking a version of Vue. Trying to debug it.

@Jmingzi
Copy link

Jmingzi commented Dec 29, 2018

So do i, v3.2.1 is not existed, use v3.1.0 worked for me.

@sodatea
Copy link
Member

sodatea commented Dec 30, 2018

@Jmingzi Please upgrade your global @vue/cli version.

@GreggOD
Copy link

GreggOD commented Jan 9, 2019

@Jmingzi Please upgrade your global @vue/cli version.

I tried doing that but on Linux there's an issue with installing packages globally through NVM and through NPM - if you do the wrong sequence it locks it to a version regardless of any update queries. A common issue it seems.

I ended up uninstalling NVM, then Vue by removing it from the global installs folder manually. Then reinstalling everything.

@CloudMunk
Copy link

CloudMunk commented Oct 14, 2021

I'm incredibly stuck on this problem as well.

Have upgraded:
global @vue/cli 4.5.13
node: v14.18.1
npm: 6.14.15

still cannot find '@vue/cli-plugin-babel' although it is in devDependencies and on version 4.5.14

Other things I've tried:
Delete package.lock file + node_modules and reinstall with npm install => no luck same error
Restart Mac => no luck same error

What on earth is causing this? Anyone have a solid fix or solution to this? Or maybe even a workaround?

`Error: Cannot find module '@vue/cli-plugin-babel'
Require stack:

  • /usr/local/lib/node_modules/@vue/cli-service/lib/Service.js
  • /usr/local/lib/node_modules/@vue/cli-service/bin/vue-cli-service.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
    at Function.Module._load (internal/modules/cjs/loader.js:746:27)
    at Module.require (internal/modules/cjs/loader.js:974:19)
    at require (internal/modules/cjs/helpers.js:93:18)
    at idToPlugin (/usr/local/lib/node_modules/@vue/cli-service/lib/Service.js:145:14)
    at /usr/local/lib/node_modules/@vue/cli-service/lib/Service.js:184:20
    at Array.map ()
    at Service.resolvePlugins (/usr/local/lib/node_modules/@vue/cli-service/lib/Service.js:170:10)
    at new Service (/usr/local/lib/node_modules/@vue/cli-service/lib/Service.js:32:25)
    at Object. (/usr/local/lib/node_modules/@vue/cli-service/bin/vue-cli-service.js:15:17) {
    code: 'MODULE_NOT_FOUND',
    requireStack: [
    '/usr/local/lib/node_modules/@vue/cli-service/lib/Service.js',
    '/usr/local/lib/node_modules/@vue/cli-service/bin/vue-cli-service.js'
    ]
    }`

@sodatea
Copy link
Member

sodatea commented Oct 14, 2021

Require stack:

  • /usr/local/lib/node_modules/@vue/cli-service/lib/Service.js

Why is it referencing the global node_modules directory?
Should use the local one in the project instead. Try npm run serve or npm run build.

@CloudMunk
Copy link

Require stack:

  • /usr/local/lib/node_modules/@vue/cli-service/lib/Service.js

Why is it referencing the global node_modules directory? Should use the local one in the project instead. Try npm run serve or npm run build.

That is the exact command(npm run serve) I am running and getting this error :)

@ph3ne
Copy link

ph3ne commented Nov 19, 2021

I have exactly the same issue as @CloudMunk , I tried the same troubleshot procedure without success too. I can't make my project work anymore, that's very problematic.

@marquelamar
Copy link

This happened to me too. There are some posts on stack overflow, but i thought i'd come here first.

@ph3ne
Copy link

ph3ne commented Dec 2, 2021

The solution for me was to downgrade to NPM v6, see my answer on this issue: #6793

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests