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.

ReferenceError: path is not defined

See original GitHub issue

Trying to run on Ubuntu 16:

ReferenceError: path is not defined
    at processSrc (/usr/local/lib/node_modules/mdpdf/src/utils.js:51:23)
    at Object.$.each (/usr/local/lib/node_modules/mdpdf/src/utils.js:59:23)
    at initialize.exports.each (/usr/local/lib/node_modules/mdpdf/node_modules/cheerio/lib/api/traversing.js:300:24)
    at Object.qualifyImgSources (/usr/local/lib/node_modules/mdpdf/src/utils.js:58:12)
    at prepareHeader.then.then.then.then.mdDoc (/usr/local/lib/node_modules/mdpdf/src/index.js:116:23)
    at tryCatcher (/usr/local/lib/node_modules/mdpdf/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/mdpdf/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/usr/local/lib/node_modules/mdpdf/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/usr/local/lib/node_modules/mdpdf/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/usr/local/lib/node_modules/mdpdf/node_modules/bluebird/js/release/promise.js:694:18)
    at Promise._fulfill (/usr/local/lib/node_modules/mdpdf/node_modules/bluebird/js/release/promise.js:638:18)
    at /usr/local/lib/node_modules/mdpdf/node_modules/bluebird/js/release/nodeback.js:42:21
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:54:3)

with node v11.8.0, npm 6.5.0

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:23 (13 by maintainers)

github_iconTop GitHub Comments

1reaction
BlueHatbRitcommented, Feb 18, 2019

This has been fixed in version 2.0.2 which is now published to npm. Thanks for all your help and contributions!

0reactions
BlueHatbRitcommented, Feb 18, 2019

I’ve removed this logging now on master if you wanted to pull an update. You won’t need to npm install or npm link again. A release will be made once I get home and have access to my signing key and then you can continue on as normal!

Read more comments on GitHub >

github_iconTop Results From Across the Web

node.js - ReferenceError: path is not defined: Express
The page is rendered but it gives an error when I press any link. ReferenceError: path ...
Read more >
How to fix: ReferenceError: path is not defined
Recently, when attempting to use a gulp command in the Terminal app, I saw an error message saying ReferenceError: path is not defined...
Read more >
ReferenceError: path is not defined - Coding Questions
Whenever I run my code I get this error ReferenceError: path is not defined at ... loadImage(fileObj.path, resolve, reject)}) } else if (lib ......
Read more >
path is not defined · Issue #1118 · nodejs/docker-node - GitHub
I have tried removing custom environment setting for NODE_PATH and still no joy where path is involved. Additionally not setting NODE_PATH ...
Read more >
Error: "Cannot export file. ReferenceError: Path is not defined"
Hi there, when I want to transmutr a plant from Quixel Bridge I get this error: “Cannot export file. ReferenceError: Path is not...
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