Nuxt.js: when npm run dev ,promisify is not a function

[wufuxi]

E:\myDemos\nuxtTest\node_modules.1.1.1@nuxt\lib\builder\builder.js:32
const glob = promisify(Glob)
^

TypeError: promisify is not a function
at Object. (E:\myDemos\nuxtTest\node_modules.1.1.1@nuxt\lib\builder\builder.js:32:14)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object. (E:\myDemos\nuxtTest\node_modules.1.1.1@nuxt\lib\builder\index.js:1:79)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)

_{This question is available on Nuxt.js community (#c2267)}

[NicoPennec]

The minimum Node.js version required for Nuxt.js is also increased to 8.0.0 (Current LTS) since Nuxt release 1.0 (https://github.com/nuxt/nuxt.js/releases/tag/v1.0.0)

And promosify() is a new utility function from Node 8

So you seem not on node >=8
Please upgrade your stack 😉

[NicoPennec]

https://github.com/nuxt/nuxt.js/issues/2545

[galvez]

Related to
https://github.com/nuxt/nuxt.js/commit/3b5a4709e8e023bfdce12f9d03fce443e87a4251

On Thu, Aug 9, 2018 at 2:47 AM Alexander Lichter [e-mail]
wrote:

Because this issue seems to be inactive for quite some time, I'll close it
now. If you feel like it deserves some attention because it's not fixed,
feel free to ping me and I'll reopen it.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nuxt/nuxt.js/issues/2604#issuecomment-411644076, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAwA6u--TX8it3k8jElukRpeJ0aTs5-ks5uO8zlgaJpZM4RfI2V
.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.