Next step · What to do next

Update packages safely (monthly routine)

What you may see

I am told my packages are old, and I am afraid to update

Why this step

Small regular updates are safe and cheap; one huge update after a year breaks everything at once.

Before you start

Is everything saved in Git and do the tests pass now?

The prompt for this step

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

WHAT I WANT NEXT
Update packages safely (monthly routine)

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
Small regular updates are safe and cheap; one huge update after a year breaks everything at once.

DO THESE STEPS, IN THIS ORDER
1. Run the outdated check and sort packages into patch, minor and major updates; explain the difference in plain words.
2. On a new branch, apply patch and minor updates together, run the build and tests, and fix only what breaks.
3. Do major updates one package at a time, reading its upgrade notes first, each in its own commit.
4. Check the live preview before merging; schedule this monthly and note it in the README.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The build and tests pass on the branch, the preview works, and each major update is reversible by one commit.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not update everything at once on the main branch.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Run the outdated check and sort packages into patch, minor and major updates; explain the difference in plain words.
On a new branch, apply patch and minor updates together, run the build and tests, and fix only what breaks.
Do major updates one package at a time, reading its upgrade notes first, each in its own commit.
Check the live preview before merging; schedule this monthly and note it in the README.

Do not do this

Do not ignore security updates.
Do not update everything at once on the main branch.

Try another entry