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.

Support npm package semver / update installed packages

See original GitHub issue

We are having issues where installing a package @latest or @^3.0.0 will install the dependency correctly (e.g. 3.0.1), but if a new version of that package is released, on page load the installed dependency stays stuck at the previous version.

e.g. at the time of creation we have @polymer/polymer@^3.0.0 it will install @polymer/polymer@3.0.1. If we add another package, namely a webcomponent that must be singleton, that relies on @polymer/polymer@^3.0.0 after @polymer/polymer@3.0.2 has been released, it will install both @polymer/polymer@3.0.1, and @polymer/polymer@3.0.2 when they should both resolve to 3.0.2

This use case is common when we publish a stackblitz and share it with our users.

Issue Analytics

State:
Created 5 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

EricSimonscommented, May 10, 2018

Just shipped that to prod- here’s a quick demo of it in action:

deps

Lmk if that fixes things on your end!

0reactions

sulcocommented, Feb 12, 2021

If anyone stumbles upon this post, the answer is: it updates to the @latest

Closing for now as it seems that the original issue was resolved

Top Results From Across the Web

About semantic versioning

Using semantic versioning to specify update types your package can accept. You can specify which update types your package can accept from dependencies...

npm check and update package if needed - node.js

Use this package to update all package versions in your package.json (-u is short for --updateAll). Install all of the new versions of...

Updating NPM Packages with Semantic Versioning

I this blog post, we'll look at the most popular method to automate package updates — and doing so safely. Automating NPM library...

4 safe steps to update NPM packages [Cheat Sheet]

Understand npm package versioning; Audit installed npm packages; Update only one npm package at time; Test your code after updating npm packages.

How to Use Semantic Versioning in NPM

The Node Package Manager (npm) ecosystem uses Semantic Versioning, or SemVer, as the standard for version numbers. By default, when installing an npm...