Upgrade a package and fix what breaks

Name the dependency. ML.ai installs the new version, fixes the code it breaks, and runs your tests.

Install ML.ai All use cases

New sessionAutomationsReview

Sessions

Review feat/export-csv
Tests for formatPrice
Upgrade uuid

Upgrade uuid to latest majoracme/orders4m 50s

Upgrade the uuid dependency to the latest major version. Fix anything that breaks and run the tests.

Ran npm installuuid 14.0.3

Checked require("uuid") in this projectv4 works

The deep import no longer exists.

require('uuid/v4') was removed in current uuid, so ids.js moves to the named v4 export.

ids.js+1−1

AllowAlwaysDeny

Ran npm test

after the upgrade

order ids are prefixed uuids

passing

session ids are prefixed uuids

passing

Describe a task or ask a question

Mode BuildModel AutoEffortlowmediumhigh

src/ids.jsProposed fix

ids.js+1 −1

1-const uuidv4 = require('uuid/v4')

1+const { v4: uuidv4 } = require('uuid')

3function newOrderId() {

Who uses for upgrades

Developers with a package a major version behind and no time for the changelog.

Teams with deprecated packages
A dependency npm now warns about.
Developers facing a breaking change
Removed imports that fail only at runtime.
Reviewers who want proof
A bump that arrives with a passing test run.

An upgrade is done when the code still runs

Changing the number is easy. Here is what makes the change safe to merge.

ids.jspackage.jsonpackage-lock.jsonpasted into chat

1const uuidv4 = require('uuid/v4')

3function newOrderId() {

4 return 'ord_' + uuidv4()

The installed version and the lockfile never made it into the chat.

What a pasted file can see

A chat window sees one pasted file

It does not know your installed version, your lockfile, or what else imports the package.

package.json:9+"uuid": "^14.0.3"

ids.js:1+const { v4: uuidv4 } = require('uuid')

ids.test.js:6assert.match(newOrderId(), /^ord_/)

The bump and the code it breaks

It finds what the bump breaks

ML.ai knew current uuid drops the deep import require('uuid/v4'), so src/ids.js changed with package.json.

npm install uuid@latest14.0.3

require("uuid") in this CJS projectv4 works

npm test2 passed

Checked in your setup before the edit

It checks the new API first

Before editing, it confirmed require('uuid') exports v4 in this CommonJS project. Then it ran the tests.

This turn said it would change package.json and src/ids.js, and is now also changing another file. Continue?

ContinueKeep to what was declared

The files it said it would change

It sticks to the files it named

It listed the work and asked which parts to do. Going past that list took another OK.

Upgrading by hand versus handing it off

You bump the number, read the changelog, and find the broken import one error at a time.

Terminal

$npm install uuid@latest

$npm test → Cannot find moduleBroken

$read the changelog

$fix the import, npm test again

The broken import shows up one run at a time

You name the package. ML.ai installs it, fixes what breaks, and runs your tests.

Upgrade uuid to the latest major version and run the tests

Ran npm installuuid 14.0.3

The deep import is gone. ids.js moves to the named export.

ids.js+1 −1

1-const uuidv4 = require('uuid/v4')

1+const { v4: uuidv4 } = require('uuid')

Which agent actually does this

Build

ReadInstallEditRun tests

Build · Read · Install · Edit · Run tests

Bumps the package and fixes the fallout

Installs the new version, edits what breaks, runs your tests, and asks before changing undeclared files.

architect

ReadPlanWrite

architect · Read · Plan · Write

Optional: plan a large change

Read-only. Returns an ordered plan before Build edits anything.

From version bump to passing tests

The bump is one line. The work is the code it breaks.

Explorer

package.json
src/ids.js
test/ids.test.js
package-lock.json

ML.ai ML.ai

Build

general, the default agent, takes the whole task

Upgrade the uuid dependency to the latest major version. Fix anything that breaks and run the tests.

Mode BuildModel AutoEffortlowmediumhigh

1Name the packageSay which dependency and how far to go. ML.ai may ask which parts of the work to do.

Explorer

package.json
src/ids.js
test/ids.test.js
package-lock.json

ML.ai ML.ai

Build

Upgrade the uuid dependency to the latest major version. Fix anything that breaks and run the tests.

Read package.json and src/ids.js

Ran npm installuuid 14.0.3

Checked require("uuid") in this projectv4 works

Ran npm test2 passed

Describe a task or ask a question

Mode BuildModel AutoEffortlowmediumhigh

2It installs the new versionnpm updates package.json and the lockfile together.

Explorer

package.json+6−2
src/ids.js+1−1
test/ids.test.js
package-lock.json+9−6

ML.ai ML.ai

Build

uuid goes from 3.4.0 to 14.0.3. The deep import no longer exists, so ids.js changes with it.

ids.jspackage.json+1 −1

1-const uuidv4 = require('uuid/v4')

1+const { v4: uuidv4 } = require('uuid')

3function newOrderId() {

AllowAlwaysDeny

Describe a task or ask a question

Mode BuildModel AutoEffortlowmediumhigh

3It fixes what brokeIt confirms the new import works in your project, edits the code, and runs your tests.

Explorer

package.json+6−2
src/ids.js+1−1
test/ids.test.js
package-lock.json+9−6

ML.ai ML.ai

Build

uuid goes from 3.4.0 to 14.0.3. The deep import no longer exists, so ids.js changes with it.

ids.jspackage.json+1 −1

1-const uuidv4 = require('uuid/v4')

1+const { v4: uuidv4 } = require('uuid')

3function newOrderId() {

AllowAlwaysDeny

Allowed · uuid 14.0.3 installed, ids.js fixed, 2 tests passed

Describe a task or ask a question

Mode BuildModel AutoEffortlowmediumhigh

4You review the changeThe summary lists every file touched and the test result.

Explorer

package.json
src/ids.js
test/ids.test.js
package-lock.json

ML.ai ML.ai

Build

general, the default agent, takes the whole task

Upgrade the uuid dependency to the latest major version. Fix anything that breaks and run the tests.

Mode BuildModel AutoEffortlowmediumhigh

Where upgrades go wrong

Three common failures, and what ML.ai did about each in a real run.

The bumpWith ML.ai

package.json^14.0.3

ids.js:1named v4 import

Code and package move together

The import that no longer exists

A major version removes a deep import, and nothing fails until the code runs.

How ML.ai ML.ai handles it

ML.ai switched src/ids.js to a named v4 import after checking it worked in CommonJS.

After the bumpWith ML.ai

npm installdone

npm test2 passed

Tests run before you review

Upgrading blind

The version changes and nothing runs until CI or production.

How ML.ai ML.ai handles it

ML.ai ran npm test after the change: 2 passed.

Files changedWith ML.ai

package.json^14.0.3

package-lock.jsonupdated by npm

src/ids.jsimport fixed

One consistent change

A lockfile out of step

package.json says one version and the lockfile pins another.

How ML.ai ML.ai handles it

npm moved both together. The diff stat showed 3 files changed.

Where this stops

What to expect, so nothing surprises you.

Which should I do?

AllowAlwaysDeny

It asks before starting

It listed install, fix and test, and waited for your pick.

npm testYour CI

Local tests only

It runs npm test on your machine. CI and staging checks are still yours.

architectBuild

Plan big changes first

For more than a few broken imports, get a plan from architect, then hand it to Build.

Root cause in session.ts

The store returns null before the session write finishes, so the middleware rejects a valid token.

session.ts+2 −1

40export async function getSession(id) {

41- const s = store.get(id)

41+ const s = await store.get(id)

42+ if (!s) throw new SessionNotFound(id)

AllowAlwaysDeny

Debug

Give ML.ai a failing test or a stack trace. It finds the actual cause and proposes a fix you approve.

See how it works

Plan · move off the .ini loader

1Add a shared config interface
2Read environment variables behind it
3Remove the .ini loader

Nothing edited until you hand it to general

Hand to generalRevise

Legacy modernization

explore maps the old code, architect plans the path, and each stage lands as its own diff.

See how it works

FAQs

What else does it change?

The lockfile, through npm install, and any source file whose import the new version broke.

Does it run my tests?

Yes. After the change, npm test ran: 2 tests, 2 passed.

Does it pick the version?

Ask for the latest major and it picks it (uuid 14.0.3 in the run). Name a version to pin one.

How is this different from modernizing legacy code?

This page covers version bumps and what they break. Modernize legacy code covers moving old code forward in stages.

Try today, or talk to us about what is next

Install the editor agent on your own machine, or book a call to talk through your team’s workloads

Download ML.ai Book a call

Upgrade a package and fix what breaks

Who uses for upgrades

Teams with deprecated packages

Developers facing a breaking change

Reviewers who want proof

An upgrade is done when the code still runs

A chat window sees one pasted file

It finds what the bump breaks

It checks the new API first

It sticks to the files it named

Upgrading by hand versus handing it off

By hand

With

Which agent actually does this

Bumps the package and fixes the fallout

Optional: plan a large change

From version bump to passing tests

Where upgrades go wrong

The import that no longer exists

Upgrading blind

A lockfile out of step

Where this stops

It asks before starting

Local tests only

Plan big changes first

Related use cases

Debug

Legacy modernization

FAQs

Try today, or talk to us about what is next