-
Notifications
You must be signed in to change notification settings - Fork 932
Browserify Failed!: Unexpected token, related to new spinner.scss #198
Comments
And this is my gulpfile. Do I not currently support sass right now is that the problem? How do I fix it?
|
Good point. This is from the new spinner component. Will remove the sass dependency soon. In the mean time try a npm install. On May 17, 2016, 12:35 AM -0500, vesper8notifications@github.com, wrote:
|
I do use sass, but I have the ParseError too :
And my gulpfile : var elixir = require('laravel-elixir');
require('laravel-elixir-vueify');
elixir(function(mix) {
mix.sass('vendor.scss', null, { includePaths: ['node_modules/'] })
.sass('awe.scss', null, { includePaths: ['node_modules/'] })
.browserify('admin.js', 'public/js/admin.js')
.browserify('awe.js', 'public/js/awe.js')
;
}); What can I do ? |
I'll need some time to fix this. Can you try npm install in your project and see if it helps? On May 17, 2016, 4:53 AM -0500, Laurent Goussardnotifications@github.com, wrote:
|
@amanpatel I have created issue #196 which I think is the reason for this issue as well. If the package.json was changed back to the dist folder these issues would be solved. |
fyi doing a npm install (or npm update) simply does nothing. nothing new gets installed or updated (with my package.json above) and the gulp error stays the same |
Sorry, I'm just trying and, as @vesper8 said, npm install or update does not fix the issue. |
using npm and same error - with Alert.vue
|
@vesper8 @loranger @lukpep PR #200 was merged yesterday however, I forgot to bump the version number so npm wont be picking up the change. Depending on how desperately you need vue-strap to work you could manually edit Hope that helps |
@doonetheprune - thx. I've did a rollback to 1.0.7 and will wait for 1.0.11 on npm |
1.0.11 is now published. Please close the issue if it fixes it. yuche had accepted the change in package.json which changes the way people can use the package. It's now back to the way it worked before. |
The issue is still here for me. |
Have the same issue |
Getting this build error when running gulp since updating from the master to the 1.0.10 branch
Any ideas why?
This is my package.json
The text was updated successfully, but these errors were encountered: