It used to work

Nothing changed, but now it won't install, build or start. Software rots when it sits. 11 answers.

Everything in my project is years out of date. How do I update it? Get it running exactly as it is first. Then update in small steps (runtime, then framework, then the rest), testing between each, and replace what's abandoned. npm install fails on my old project. How do I fix it? Usually Node is too new for the project, the lockfile and package.json disagree, or a package needs build tools or no longer exists. Check each, in this order. My project only runs on an old version of Node. What do I do? Run it on its old version with a version manager so it works again, then upgrade one long-term-support release at a time. Node 20 and older are end of life. Create React App is deprecated. What now? Your app still works: Create React App is in maintenance mode but has no active maintainers. React recommends moving to a framework or a build tool like Vite. npm ERESOLVE: unable to resolve dependency tree. What does it mean? Two packages want different versions of a shared one, often React. --legacy-peer-deps forces the install but hides the conflict. Update the odd one out instead. My site needs a newer PHP version. How do I upgrade safely? PHP versions get four years of support, then none. Check what your code and plugins support, test on a copy, step up one version at a time, then switch live. How do I upgrade an old Laravel app? One major version at a time, following each official upgrade guide, upgrading PHP as you go. Laravel versions get security fixes for two years after release. My Python project won't install its dependencies. How do I fix it? Use a fresh virtual environment, the Python version the project was built for, and its pinned requirements. Most errors on old projects are version mismatches. My Docker build fails. How do I fix it? Find the Dockerfile step that failed. Old projects usually fail on an outdated base image, a file outside the build context, or installing dependencies. My Docker container won't start. Why? The container's logs say why. Usually the app crashed on start: a missing setting, a database it can't reach, the wrong command, or listening on localhost. A database migration failed in production. What now? Stop deploying, back up, and find out exactly which steps ran. Then either roll back and fix, or finish the steps by hand and mark it resolved. Never reset.

Not sure what's wrong with yours?

Tell us what you built. We'll go through it and tell you in writing what's broken, what it takes, and whether it can be saved. Free.

Submit your project