Skip to content

Conversation

@benallfree
Copy link
Contributor

@benallfree benallfree commented Apr 7, 2024

@crutchcorn Can you take a look at this please, I think it might be helpful for the community.

This PR does two things:

  1. Make run() awaitable. Previously, run() was fire-and-forget, but this doesn't work well when wrapping Plop. I needed a way to await run().
  2. Along the same lines, run() was not bubbling exceptions. It was calling process.exit, but that is insufficient if the user has setup/teardown that needs to happen after run().
@crutchcorn
Copy link
Member

I like this change, but it's technically a breaking change.

Let's merge your other PRs, then we can address this. Sorry for the delays on this all - it's been a busy/rough month

@benallfree
Copy link
Contributor Author

benallfree commented Apr 21, 2024

Do we have a system for tagging open PRs for future releases?

How would you feel about making a next branch so users can do npm i plop@next?

@benallfree benallfree changed the title Make run() awaitable and bubble exceptions rather than process.exit(1) Apr 21, 2024
@benallfree benallfree changed the title enhancement: Make run() awaitable and bubble exceptions rather than process.exit(1) Apr 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants