styleText doesn't land until Node 22 (node 21.7 technically) which won't be LTS until October, so I don't think we can merge this until then based on this decision doc

https://github.com/epicweb-dev/epic-stack/blob/main/docs/decisions/021-node-version.md

styleText doesn't land until Node 22 (node 21.7 technically) which won't be LTS until October, so I don't think we can merge this until then based on this decision doc

https://github.com/epicweb-dev/epic-stack/blob/main/docs/decisions/021-node-version.md

I am so used to using it that I didn't realize it is still in Active development stage.

I will try to keep this PR up-to-date until it is stablized.

Another point: this does not actually remove chalk from the dependency tree, as other dependencies do depend on chalk, but now it is a transitive dev dependency.

styleText doesn't land until Node 22 (node 21.7 technically) which won't be LTS until October, so I don't think we can merge this until then based on this decision doc

https://github.com/epicweb-dev/epic-stack/blob/main/docs/decisions/021-node-version.md

What do you think about updating the requirement to Node 20.12.0?

I'm used to work with .nvmrc or .node-version files so that Node version manager like fnm can select the right version for the project.
Is it worth opening a PR to add one of those (with corresponding documentation)? So it might also unblock this PR.
Edit: This is already suggested in #799

Why don't node managers reference the engines config in the package.json? I'd really rather avoid adding an extra file to the root just for the node version.

I'm going to close this for now. We can revisit when Node 22 is our base.