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

Node 10: TypeError: Cannot read property '1' of null #3261

Closed
pdesjardins90 opened this issue May 3, 2018 · 11 comments
Closed

Node 10: TypeError: Cannot read property '1' of null #3261

pdesjardins90 opened this issue May 3, 2018 · 11 comments

Comments

@pdesjardins90
Copy link

After upgrading node, WCT doesn't work anymore. The error is:
TypeError: Cannot read property '1' of null

Node v10.0.0
WCT version: 6.5

Steps to reproduce:

  • polymer init (shop app)
  • polymer test

Stack trace:

cli runtime exception: TypeError: Cannot read property '1' of null
error:   TypeError: Cannot read property '1' of null
    at module.exports (/Users/x/.config/yarn/global/node_modules/promisify-node/utils/args.js:9:63)
    at processExports (/Users/x/.config/yarn/global/node_modules/promisify-node/index.js:61:29)
    at processExports (/Users/x/.config/yarn/global/node_modules/promisify-node/index.js:82:25)
    at processExports (/Users/x/.config/yarn/global/node_modules/promisify-node/index.js:82:25)
    at processExports (/Users/x/.config/yarn/global/node_modules/promisify-node/index.js:82:25)
    at module.exports (/Users/x/.config/yarn/global/node_modules/promisify-node/index.js:164:10)
    at /Users/x/.config/yarn/global/node_modules/web-component-tester/runner/paths.js:49:23
    at Generator.next (<anonymous>)
    at /Users/x/.config/yarn/global/node_modules/web-component-tester/runner/paths.js:20:71
    at new Promise (<anonymous>)
@web-padawan
Copy link
Contributor

See #280

@paladox
Copy link
Contributor

paladox commented May 9, 2018

I get this error too.

@t1djani
Copy link

t1djani commented May 17, 2018

Same for me.

@jrpool
Copy link

jrpool commented May 27, 2018

Likewise. My stacktrace entries differ in the path, replacing the above
.config/yarn/global with
.nvm/current/versions/node/v10.2.1/lib/node_modules/polymer-cli.

The reason seems to be an incompatibility with Node 10. See Polymer/pwa-starter-kit#112.

@akc42
Copy link

akc42 commented May 30, 2018

I think its this problem. I went through with the debugger and it failed when trying to promisify glob
nodegit/promisify-node#28

@ghost
Copy link

ghost commented Jun 1, 2018

Got this too. Had to switch travis ci to use 9 for now.

@paladox
Copy link
Contributor

paladox commented Jun 5, 2018

There's a new release for promisify-node which fixes support for nodejs 10 https://github.com/nodegit/promisify-node/commits/master

@paladox
Copy link
Contributor

paladox commented Jul 9, 2018

This was fixed in 29a85f9 as the repo was moved to there.

@pdesjardins90
Copy link
Author

I can confirmed this is fixed and released, thanks guys!

@usergenic
Copy link
Contributor

(FWIW this was fixed by using node's own promisify and dropping support for Node < 8)

@mdaijaj
Copy link

mdaijaj commented Oct 14, 2019

I found this error then I re-install express module.

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

No branches or pull requests

9 participants