Fix exit code error in build command on Node 20+

[jrolfs]

This should close #495 pending @schickling's take on whether this is the correct remediation.

Although I'm very keen to dig more into Effect, I'm still very much a noob in that department. This fix assumes that since everything in the command is wrapped in an Effect that no additional error handling is necessary to handle actual runtime errors, but I haven't tested out that assumption yet.

[changeset-bot]

🦋 Changeset detected

Latest commit: 741d455

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR

Some errors occurred when validating the changesets config:
The package or glob expression "examples-*" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[kachkaev]

not stale

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[notunderctrl]

not stale

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[kachkaev]

not stale 🙏

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jrolfs]

not... stale... 🙏🏻

[trevoro]

This is the funniest and most tragic pull request comment thread I've seen in years. @jrolfs thanks for doing this dude.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[notunderctrl]

not stale.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[notunderctrl]

not stale.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[kachkaev]

not stale

[timlrx]

@jrolfs I merged your fix in timlrx/contentlayer2#8 - published as contentlayer2 v0.4.5. Tested it out verified that yarn contentlayer2 build no longer throws the error message in node 20.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[kachkaev]

🇫

[jrolfs]

@timlrx thanks and thanks for getting a fork off the ground! I was considering doing it myself but will switch our stuff over to yours (currently running a patched version).

[jrolfs]

For anyone following this, I switched to the fork, and it's working great and includes this fix. I wrote some docs on how to switch over here.

[justice-sh]

Thank you very much guys. 🙏