Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Keep versions of AMP build tools and dev dependencies up to date

See original GitHub issue

In addition, set up an automated means of periodically rolling forward the versions in package.json and yarn.lock

/cc @cramforce

Issue Analytics

State:
Created 6 years ago
Comments:11 (11 by maintainers)

Top GitHub Comments

1reaction

rsimhacommented, Jun 25, 2018

Update: We now use Renovate to keep our dependencies up to date.

1reaction

cramforcecommented, Jan 4, 2018

The new integration now needs write access to code. We need to check whether that is OK security wise.

Top Results From Across the Web

Keep npm dependencies up to date - Aleksey Hudochenkov

npm update updates all dependencies to the highest version, matching the specified semver range (“wanted” column in npm outdated ). npm update ...

Automatically keep your dependencies up to date in closed ...

Generally, I would say that keeping your dependencies at the absolute latest version, including major, minor and patch is the preferred way. Don ......

Update Composer dependencies to latest despite static ...

Is it possible to update all my Composer dependencies to the latest versions via one command, if I have used static version numbers?...

How to efficiently update your npm dependencies - Code-trotter

In your console, your dependencies will be splitted between dependencies and devDependencies. For each possible update, yarn gives you the ...

ampproject/amp-toolbox - GitHub

amp -toolbox uses Lerna to manage it's packages. To keep build times low, devDependencies (but not CLI dependencies) must be added to the...