deepak1556 / gulp-browserify

Bundle modules with BrowserifyJS
MIT License
195 stars 45 forks source link

Error: need proper browserify instance, on windows machine #84

Open damirkusar opened 9 years ago

damirkusar commented 9 years ago

Hi,

I have a own seed https://github.com/damirkusar/leptir-angular-seed. When i execute it with gulp, then i get this error message, but just on a windows computer:

Error: browserify-shim needs to be passed a proper browserify instance as the first argument you passed:←[32m'C:\Users\Damir\test\leptir-angular-seed\node_modules\gulp-browserify\node_modules\browserify\ node_modules\buffer\index.js'←[39m

at preValidate (C:\Users\Damir\test\leptir-angular-seed\node_modules\gulp-browserify\node_modules\browserify-shim\in dex.js:16:11) at shim (C:\Users\Damir\test\leptir-angular-seed\node_modules\gulp-browserify\node_modules\browserify-shim\index.js: 83:3) at nr (C:\Users\Damir\test\leptir-angular-seed\node_modules\gulp-browserify\node_modules\browserify\node_modules\mod ule-deps\index.js:243:23) at C:\Users\Damir\test\leptir-angular-seed\node_modules\gulp-browserify\node_modules\browserify\node_modules\resolve \lib\async.js:42:21 at C:\Users\Damir\test\leptir-angular-seed\node_modules\gulp-browserify\node_modules\browserify\node_modules\resolve \lib\async.js:121:35 at C:\Users\Damir\test\leptir-angular-seed\node_modules\gulp-browserify\node_modules\browserify\node_modules\resolve \lib\async.js:93:39 at C:\Users\Damir\test\leptir-angular-seed\node_modules\gulp-browserify\node_modules\browserify\node_modules\resolve \lib\async.js:59:30 at C:\Users\Damir\test\leptir-angular-seed\node_modules\gulp-browserify\node_modules\browserify\node_modules\resolve \lib\async.js:18:18 at FSReqWrap.oncomplete (fs.js:95:15)

do you know what that could be?

cbeihl commented 8 years ago

I'm seeing the same issue with my gulp build on Windows. On my Mac the exact same build works fine.

Any ideas on how to fix this ?

cbeihl commented 8 years ago

I'm able to get my build to work now using 'node-debug' although it takes much longer :

npm install -g node-debug
node-debug gulp

Maybe this is a timing or environment issue ?