Kent C. Dodds comments

Results 895 comments of


                                            Kent C. Dodds

Use `fly launch`/`dockerfile-node` instead of `.dockerignore`, `Dockerfile`, `fly.toml` & `start.sh`

The apps are under the Remix fly account. I have no issues with any changes to this stack so long as it works and is as simple or simpler

build(node): use `.nvmrc` to declare `node` version

Is there any way for these tools to reference the engines config in the package.json so we don't need an entirely separate file for managing the node version?

build(node): use `.nvmrc` to declare `node` version

That all sounds fine to me. I'm fine with documentation that recommends `fnm` as long as we don't need to add yet another root-level file to the codebase.

build(node): use `.nvmrc` to declare `node` version

Closing this for now. Feel free to open a new PR for supporting the package.json

add util for handling remix headers generally

I think React Router v7 (single fetch specifically) changes how headers work a fair bit so I don't think I'll be merging this since I want to get on RR7...

add util for handling remix headers generally

RR7 has been merged! Feel free to check whether this is necessary and update things if so. Thanks!

build(deps): remove `chalk` and use `styleText` instead

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.

build(deps): remove `chalk` and use `styleText` instead

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

build(deps): remove `chalk` and use `styleText` instead

Now we're running on node version 22. So we can look into doing this. There have been a number of changes to these different files. So if you would like...

/About route to explain the mission of epic stack

Hi @Jstreetman, Yeah, you can put something simple together. I want to make it easy for people to change for their own site, but having something simple would make a...