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.

Callback was already called

See original GitHub issue

After updating to 3.0.0, I get an Callback was already called error. I reverted back to 1.4.0 and it runs again without issues.

Here is the callstack:

Error: Callback was already called.
    at throwError ([PATH]\node_modules\neo-async\async.js:14:11)
    at [PATH]\node_modules\neo-async\async.js:6725:13
    at normalResolver.resolve ([PATH]\node_modules\webpack\lib\NormalModuleFactory.js:188:25)
    at doResolve ([PATH]\node_modules\enhanced-resolve\lib\Resolver.js:181:12)
    at hook.callAsync ([PATH]\node_modules\enhanced-resolve\lib\Resolver.js:232:5)
    at _fn0 (eval at create ([PATH]\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:15:1)
    at resolver.doResolve ([PATH]\node_modules\enhanced-resolve\lib\UnsafeCachePlugin.js:37:5)
    at hook.callAsync ([PATH]\node_modules\enhanced-resolve\lib\Resolver.js:232:5)
    at _fn0 (eval at create ([PATH]\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:15:1)
    at hook.callAsync ([PATH]\node_modules\enhanced-resolve\lib\Resolver.js:232:5)
    at _fn1 (eval at create ([PATH]\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:24:1)
    at hook.callAsync ([PATH]\node_modules\enhanced-resolve\lib\Resolver.js:232:5)
    at _fn43 (eval at create ([PATH]\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:399:1)
    at resolver.doResolve ([PATH]\node_modules\enhanced-resolve\lib\ModuleKindPlugin.js:23:37)
    at hook.callAsync ([PATH]\node_modules\enhanced-resolve\lib\Resolver.js:232:5)
    at _fn0 (eval at create ([PATH]\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:15:1)
    at hook.callAsync ([PATH]\node_modules\enhanced-resolve\lib\Resolver.js:232:5)
    at _fn0 (eval at create ([PATH]\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:15:1)
    at args ([PATH]\node_modules\enhanced-resolve\lib\forEachBail.js:30:14)
    at hook.callAsync ([PATH]\node_modules\enhanced-resolve\lib\Resolver.js:232:5)
    at _fn0 (eval at create ([PATH]\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:15:1)
    at resolver.doResolve ([PATH]\node_modules\enhanced-resolve\lib\UnsafeCachePlugin.js:37:5)
    at hook.callAsync ([PATH]\node_modules\enhanced-resolve\lib\Resolver.js:232:5)
    at _fn0 (eval at create ([PATH]\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:15:1)
    at hook.callAsync ([PATH]\node_modules\enhanced-resolve\lib\Resolver.js:232:5)
    at _fn1 (eval at create ([PATH]\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:24:1)
    at hook.callAsync ([PATH]\node_modules\enhanced-resolve\lib\Resolver.js:232:5)
    at _fn44 (eval at create ([PATH]\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:411:1)
    at hook.callAsync ([PATH]\node_modules\enhanced-resolve\lib\Resolver.js:232:5)
    at _fn1 (eval at create ([PATH]\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:24:1)

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:14 (12 by maintainers)

github_iconTop GitHub Comments

2reactions
Naynicommented, Mar 13, 2018

I’m currently at my day job, but I’d be happy to see if I can reproduce the callback firing twice and drop a PR later today.

1reaction
eulbotcommented, Mar 14, 2018
Build completed in 78.928s

Hash: ee6746c13f9feb58029c
Version: webpack 4.1.1
Child
    Hash: ee6746c13f9feb58029c
    Time: 78935ms
    Built at: 2018-3-14 11:47:23

I can confirm that it’s working with 3.0.2. Thank you all for your quick help.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Callback was already called async parallel - Stack Overflow
Hi I am trying to use the Async module to retrieve two users and do some processing after they have both been retrieved...
Read more >
Error "Callback was already called." even when was not called.
Error "Callback was already called." occurs when is no callback called. Look at my code, it looks like some overloading issue.
Read more >
Solved: CCL1043: Error when launching development server '...
CCL1043: Error when launching development server 'Callback was already called.' Go to solution.
Read more >
Uncaught Error: Callback was already called in mocha
One issue is that you pass a constructor argument ( Hi there! ), but your contract doesn't take any constructor arguments, so this...
Read more >
Error: Callback was already called - Agents
If you are seeing an error message, paste in the error message you are seeing (text or screenshot):. Error Callback was already called....
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