Getting error when compiling with Elixir/Browserify
See original GitHub issueHi there
When I run gulp I got this:
[22:27:27] gulp-notify: [Laravel Elixir] Browserify Failed!: Couldn't find preset "stage-2" relative to directory "/var/www/crm/node_modules/vue-select" while parsing file: /var/www/crm/node_modules/vue-select/src/mixins/pointerScroll.js
Any ideas what it might be?
Thanks in advance
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Elixir Browserify issues - Laracasts
Elixir Browserify issues. Hi, I have a gulpfile.js as follows. Copy Code var elixir = require('laravel-elixir'); require('laravel-elixir-vueify'); ...
Read more >Laravel Elixir Browserify Failed!: Unexpected token
After some time looking around I found this repo (JeffreyWay) which states there is some lines I needed to add in my gulp...
Read more >Laravel Elixir - Laravel - The PHP Framework For Web Artisans
Laravel is a PHP web application framework with expressive, elegant syntax. We've already laid the foundation — freeing you to create without sweating...
Read more >Say hello to Elixir !. I have been using Gulp for various…
It has saved my hours of effort and reduced lots of error and has helped my workflow. ... We have Laravel Elixir which...
Read more >Gulp, Laravel, and Elixir: Easy Web Application Building and ...
This is a useful tool to compile and organize files as needed, ... to get the Gulp file to execute as expected, without...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Same as #52 & #51. You need to install the babel preset for stage-2. Since I’ve had a number of these issues pop up now, I’ll likely remove this in a future release. Run this:
npm install --save-dev babel-preset-stage-2
Thanks 😃