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.

"TypeError: Path must be a string. Received undefined" on node 6.0.0

See original GitHub issue

It seems like fromString always pass undefined as the sourcepath

TypeError: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    at Object.dirname (path.js:1324:5)
    at /home/guy/WebstormProjects/selfpointrest/node_modules/clean-css/lib/utils/input-source-map-tracker.js:192:56
    at Array.forEach (native)
    at trackContentSources (/home/guy/WebstormProjects/selfpointrest/node_modules/clean-css/lib/utils/input-source-map-tracker.js:189:20)
    at InputSourceMapStore.trackLoaded (/home/guy/WebstormProjects/selfpointrest/node_modules/clean-css/lib/utils/input-source-map-tracker.js:256:3)
    at fromString (/home/guy/WebstormProjects/selfpointrest/node_modules/clean-css/lib/utils/input-source-map-tracker.js:32:8)
    at InputSourceMapStore.track (/home/guy/WebstormProjects/selfpointrest/node_modules/clean-css/lib/utils/input-source-map-tracker.js:237:5)
    at Object.whenDone (/home/guy/WebstormProjects/selfpointrest/node_modules/clean-css/lib/clean.js:145:44)
    at processNext (/home/guy/WebstormProjects/selfpointrest/node_modules/clean-css/lib/imports/inliner.js:105:13)
    at importFrom (/home/guy/WebstormProjects/selfpointrest/node_modules/clean-css/lib/imports/inliner.js:79:10)
    at processNext (/home/guy/WebstormProjects/selfpointrest/node_modules/clean-css/lib/imports/inliner.js:104:16)
    at importFrom (/home/guy/WebstormProjects/selfpointrest/node_modules/clean-css/lib/imports/inliner.js:79:10)
    at /home/guy/WebstormProjects/selfpointrest/node_modules/clean-css/lib/imports/inliner.js:325:9
    at _combinedTickCallback (internal/process/next_tick.js:67:7)

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
srikanthenjamooricommented, Aug 22, 2016

I’m using grunt, and got the same issue.

0reactions
jakubpawlowiczcommented, May 23, 2016

👍

Read more comments on GitHub >

github_iconTop Results From Across the Web

node.js - TypeError: Path must be a string. Received undefined
I a persistent error while using serverless framework with serverless-offline and jest unit testing module.
Read more >
"TypeError: Path must be a string" after break from project #2463
src/app.js Module build failed: TypeError: Path must be a string. Received undefined at assertPath (path.js:7:11) at Object.extname ...
Read more >
the "from" argument must be of type string. received undefined
After investigating the call stack, I found a dependency was using a nodejs path module parameter that was only introduced in nodejs 10.10....
Read more >
Node.js – babel + path + node 6.x: TypeError - iTecNote
Node.js – babel + path + node 6.x: TypeError: Path must be a string. Received undefined · Best Solution · Related Solutions ...
Read more >
Node.js v19.3.0 Documentation
byteLength(string[, encoding]); Static method: Buffer.compare(buf1, buf2) ... Bugs or behavior changes may surprise users when Experimental API ...
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