question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Node V6 error - 'Path must be a string. Received undefined'

See original GitHub issue

Receiving 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:closed
  • Created 7 years ago
  • Comments:21

github_iconTop GitHub Comments

14reactions
gubenkovalikcommented, Nov 6, 2017

СУКА ПИДАРАСЫ БЛЯТЬ

9reactions
StealthyDevcommented, Aug 23, 2016

still i receive the same error. could be some other issue?

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found