Node V6 error - 'Path must be a string. Received undefined'
See original GitHub issueReceiving error ‘Path must be a string. Received undefined’ when running with Node V6. This Gulp task worked fine with Node V5.11.0. Using gulp-sourcemaps v2.0.0-alpha
gulp.task('stylus', function () {
return gulp.src('src/**/*.styl')
.pipe(flatten())
.pipe(sourcemaps.init())
.pipe(stylus({use: rupture()}))
.pipe(plumber())
.pipe(uncss({html: ['src/**/*.html']}))
.pipe(cleanCSS())
.pipe(postcss(processors))
.pipe(concat('css.min.css'))
.pipe(sourcemaps.write('/maps'))
.pipe(gulp.dest('./dist/css'))
.pipe(reload({stream: true, match: '**/*.css'}));
});
Task works fine when I comment out both sourcemap lines.
Issue Analytics
- State:
- Created 7 years ago
- Comments:21
Top Results From Across the Web
"Path must be a string. Received undefined" #144 - zkat/npx
npm v5.51 node v8.9.0 ... it seems that anytime I run an npx command it shows "Path must be a string. Received undefined"...
Read more >Jest TypeError: Path must be a string. Received undefined
I solved this issue using: npm uninstall -g jest; npm install -g jest; npm cache clean; npm install.
Read more >Error: Path must be a string. Received undefined - Forge
In my case const { WebClient } = require("@slack/web-api"); was causing the problem. Changing it to import declaration didn't fix the issue ...
Read more >TypeError: Path must be a string. Received undefined-babel.js
The issue has something to do with Node 6. Using Node 5.x instead will probably fix the issue for you, if that's an...
Read more >the "path" argument must be of type string or an instance of url ...
OK, I figured out the issue. I thought the error was telling me that path was undefined. When it fact it was saying...
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
СУКА ПИДАРАСЫ БЛЯТЬ
still i receive the same error. could be some other issue?