Gulp / Elixir .src/init

@StreetGT I’ve started getting the exact save error this evening on a fresh install.

same problem

Looking at the stack trace and in node_modules/gulp-sourcemaps/index.js, it seems to be trying to require ./src/init which doesn’t exist in the directory, but does in the GitHub repository: https://github.com/floridoo/gulp-sourcemaps/blob/master/src/init.js

I know paths can be ignored in an .npmignore file but can’t see one in the repository. So is the src/ directory being excluding in npm installs some other way?

@martinbean I copied the files manually, and it worked

@alansslva Yeah, I’ve created an Issue and seems I’m not the only one who’s noticed: https://github.com/floridoo/gulp-sourcemaps/issues/242

Something’s FUBAR-d somewhere!

Haha so glad it isn't just me. Mine is screwed as well.

I have a feeling we have a leftpad situation again....

src has never been part of the repo for releases (look at the tags on github, rather than the default branches):

index.js in the release is the compiled version of what's in src in the main repo branches... specifically which version is being troublesome?

Ah, so it wasnt Yarn.

Glad i am not the only one .. I am having the same Issue.

@alansslva wrote: I copied the files manually, and it worked

Sorry to trouble you, but can you be very explicit about what you put where?

@alansslva what files did you copy and where I am facing the same problem.I am sorry I am using the first time Laravel.

@CharlesW @suditugeorge94 Copy the Folder src to your node_modules/gulp-sourcemaps Folder. This should do the trick.

Fixed by adding lock to dependencies in package.json file.

"gulp-sourcemaps": "2.0.0",

remove npm_modules and then npm install again afresh

My package.json file below for example.

{ "private": true, "scripts": { "prod": "gulp --production", "dev": "gulp watch" }, "devDependencies": { "gulp": "^3.9.1", "gulp-sourcemaps": "2.0.0", "laravel-elixir": "^5.0.0", "bootstrap-sass": "^3.3.0", "alt": "^0.17.9", "angular": "^1.5.3", "angular-animate": "^1.5.3", "angular-loading-bar": "^0.9.0", "angular-sanitize": "^1.5.3", "angular-ui-router": "^0.2.15", "filepicker-js": "^2.4.5", "jquery": "^2.1.4", "lodash": "^4.11.2", "ng-tags-input": "^3.0.0", "satellizer": "^0.14.0", "uuid": "^2.0.2", "vinyl-source-stream": "^1.1.0" }, "dependencies": { "angular-chart.js": "^1.0.2", "gulp-sourcemaps": "2.0.0", "ng-sortable": "^1.3.6", "sweetalert": "^1.1.3", "toastr": "^2.1.2" } }

@christopher you... you're good you...

@JakeYeager i'm looking at npm shrinkwrap to try and lock the npm packages down - like in the composer.lock file. Never used it before - but after this incident wasted 3 hours of my life I thought I'd dive in....

Seems to be fixed now. Removed my node_modules folder and re-ran sudo npm install and it works again.

In addition to removing my node_modules folder, I also removed the .npm folder (off your home directory), then ran npm install again. Now gulp is working again.

Starting to question how much I really want to rely on frameworks that are heavily dependent on dependencies...

@christopher wrote: Copy the Folder src to your node_modules/gulp-sourcemaps Folder. This should do the trick.

That worked great, thank you!

@Nicholaus valid concern -- but this is very much a node issue. node packages are notorious for just stopping working at some point. the entire node ecosystem is very "wild west"

And -- it's not like you have to use gulp to use laravel...

Had the same issue, first thought it was Yarn. I just removed the folder: '/node_modules/laravel-elixir/gulp-sourcemaps' for the time being.

Mapping them still works.

To fix that you got to:

node_modules/laravel-elixir/packages.json

and change the gulp-sourcemaps version to be locked at: "1.7", so it will be:

            "gulp-sourcemaps": "1.7.*",