Vee-validate: npm ERR! bootstrap-sass

Created on 31 Oct 2016 · 7Comments · Source: logaretm/vee-validate

Not able to install this package.


npm ERR! Linux 3.19.0-25-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "vee-validate@next" "--save"
npm ERR! node v5.7.0
npm ERR! npm  v3.6.0

npm ERR! Cannot read property 'bootstrap-sass' of undefined

❔ question

Source

nikolaynesov

All 7 comments

Its probably not related to the plugin, can you include the package.json file here?

logaretm on 31 Oct 2016

@logaretm sure

{
  "private": true,
  "scripts": {
    "prod": "gulp --production",
    "dev": "gulp watch"
  },
  "devDependencies": {
    "bootstrap-sass": "^3.3.7",
    "gulp": "^3.9.1",
    "jquery": "^3.1.0",
    "laravel-echo": "^1.0.1",
    "laravel-elixir": "^6.0.0-11",
    "laravel-elixir-vue-2": "^0.2.0",
    "laravel-elixir-webpack-official": "^1.0.2",
    "moment": "^2.15",
    "pusher-js": "^3.2.1",
    "vue": "^2.0.3",
    "vue-multiselect": "next",
    "vue-resource": "^1.0.3",
    "vue-router": "^2.0.1",
    "vuex": "^2.0.0"
  },
  "dependencies": {
    "vee-validate": "^2.0.0-beta.13"
  }
}

nikolaynesov on 31 Oct 2016

Its definitively not related to the plugin, I just installed all those dependencies without issues, try to remove bootstrap-sass from package.json and try again.

logaretm on 31 Oct 2016

@logaretm true, the issue does not happen when just adding dependency manually and running npm install. It only happens when running npm install vee-validate@next --save.
Anyway thank you for the quick response.

I also found another issue with validating the password. When using the rule confirmed and attributes data-as. The confirmed field error message does not recognize data-as attribute of primary field. So the error message looks something like:

The Password Confirmation does not match the form.password.
expected:
The Password Confirmation does not match the Password.

Please let me know if I'm doing something wrong and thank you for this cool package!

nikolaynesov on 31 Oct 2016

👍1

OK I will look into the install problem again.

As for the confirmed rule it has been reported before in #46 and was fixed but not tagged yet. But I guess I will improve it to support data-as on the target field thanks for the feedback.

Thank you for your support and feedback.

logaretm on 31 Oct 2016

👍1

@logaretm, may you please explain me the difference between two "npm install" commands: with "vee-validate@next" and just "vee-validate"? I tried both - the first installed vee-validate version 2.0.0-beta.17, while the second installed version 2.0.0-beta.18. So which one should I use?