base/run async conflicter resolved.

[stephenplusplus]

Fixes #269

self.conflicter.resolve(function (err) {
  if (err) {
    return self.emit('error', err);
  }
});

That block was called from base.js/run before giving the files a chance to be added to the conflicter. Thus, callbacks bound to the resolved:___ event weren't firing, and everything was locking up.

[passy]

You're mindblowingly fast.

[stephenplusplus]

Anything for yo, man!

[sindresorhus]

Use fixes #<issuenumber> in the commit or pr to have it autoclosed when it's merged ;)

[passy]

I rebased this on top of v0.11.2 but there's still nothing happening after the prompt. I'll recheck if I did something wrong ...

[passy]

Problem persists for me. Might just be the lack of sleep, but would be good if someone else could check that this fixes the pure generator if you just cherry-pick this patch on top of the latest release.

[passy]

False alarm! Everything is running as it should now. @stephenplusplus You rock! 🤘

[passy]

To conclude my monologue here ...

@sindresorhus Shall I release a v0.11.3 with this fix?

[sindresorhus]

@passy yes please :)

as you know, it needs to be cherrypicked as we don't want the prompt changes breaking everything.

[sindresorhus]

Thanks for the quick resolution @stephenplusplus :)

[SBoudrias]

Maybe it'll be best to create a branch rather than a tag to hold more in depth changes for the next major bump?

[passy]

Yup, we should do that the next time.