Package Details: vue-cli 4.5.1-1

Git Clone URL: (read-only, click to copy)
Package Base: vue-cli
Description: Standard tooling for Vue.js development
Upstream URL:
Licenses: MIT
Conflicts: nodejs-vue-cli
Submitter: flacks
Maintainer: tiberiousr
Last Packager: tiberiousr
Votes: 12
Popularity: 1.61
First Submitted: 2018-04-23 21:35
Last Updated: 2020-08-07 13:43

Latest Comments

1 2 Next › Last »

bhyoo commented on 2020-08-01 08:01

How about use yarn for make? yarn is much faster than npm (

tiberiousr commented on 2020-06-12 10:46

@GFdevelop Thanks for the heads up, I wasn't aware of the guidance on node packages. I've updated the PKGBUILD, bumped the pkgrel, and credited you as a contributor.

I'll do the same for the vue-cli-service-global package and a couple of others.

GFdevelop commented on 2020-06-12 09:25

Package contains reference to $srcdir/$pkgdir

Why you don't follow nodejs packaging guidelines?

You can see my example

tiberiousr commented on 2019-10-07 08:28

@hexd I've added an AUR package for cli-service-global that depends on this package.

hexd commented on 2019-10-06 21:31

Should @vue/cli-service-global be installed by another standalone package in AUR, or should it be part of this package?

$ vue serve

  Command vue serve requires a global addon to be installed.
  Please run yarn global add @vue/cli-service-global and try again.

bkuri commented on 2019-08-04 23:39

@tiberiousr yeah, I figured it's an npm error; decided to report nonetheless. FWIW, v3.10.1-1 gives me exactly the same error. Not sure what's going on. Thanks!

tiberiousr commented on 2019-08-04 19:52

@bkuri - I've updated the package for the 3.10.0 release. Hopefully that'll fix the issue for you.

tiberiousr commented on 2019-08-04 19:46

@bkuri - That's an npm error. There's nothing I can do to fix that. The PKGBUILD just installs the package via npm into a folder and packages that folder.

bkuri commented on 2019-08-03 22:27

I'm getting the following error when building v3.9.3-1:

npm ERR! Unexpected end of JSON input while parsing near '...XTPd3GY\npv+jr6sYK965'

Log can be found here:

flacks commented on 2018-11-16 10:50

No problem. Thanks for updating the command; also, using "+" for find - instead of "\;" - is considerably faster, especially for larger operations.