Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to use it to troubleshoot Gulp tasks? #14

Open
coaxial opened this issue May 6, 2016 · 3 comments
Open

How to use it to troubleshoot Gulp tasks? #14

coaxial opened this issue May 6, 2016 · 3 comments

Comments

@coaxial
Copy link

coaxial commented May 6, 2016

I have a task that doesn't terminate and I'd like to use this package to find out what the problem is.

How do I do that?

When I call log at the end of my tasks sequence (with runSequence), I am getting this:

fs.js:1440
      if (!stat.isSymbolicLink()) {
                ^

TypeError: stat.isSymbolicLink is not a function
    at Object.realpathSync (fs.js:1440:17)
    at toRealPath (module.js:112:13)
    at tryFile (module.js:108:22)
    at tryPackage (module.js:96:10)
    at Function.Module._findPath (module.js:153:20)
    at Function.Module._resolveFilename (module.js:323:25)
    at Function.Module._load (module.js:276:25)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.wrap [as FSInitialize] (/Users/coaxial/code/myproject/node_modules/why-is-node-running/index.js:21:22)
@yoshuawuyts
Copy link
Collaborator

what version of Node / npm are you running?

@coaxial
Copy link
Author

coaxial commented May 7, 2016

$ npm -v
3.8.8

$ node -v
v4.4.3

@mafintosh
Copy link
Owner

If you are able to use 8+ latest version will prob do the trick

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants