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.

Fixed version in example package.json

See original GitHub issue

It would be easier to know what versions are being packaged in the working example if we had them fixed in the package.json. Is there something that prevents this?

https://github.com/mui-org/material-ui/blob/master/examples/nextjs/package.json

Issue Analytics

State:
Created 2 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

eps1loncommented, May 26, 2021

I understand that a npm dist tag may be more unconventional depending on your background. Ideally we’d just list the resolved version here e.g. ^4.11.0 instead of latest. But we don’t have automatic tooling for that. And without automatic tooling the versions will just become stale which is probably more confusing than using latest.

So if we could bump them automatically after yarn release:version, that’d be perfect. Any contribution moving us closer to this ideal would be welcome!

1reaction

eps1loncommented, May 26, 2021

I would suspect that latest is more descriptive to the majority of our audience compared to ^4.6.2. Using an npm dist tag also avoids having to bump these when releasing new majors.

So for pragmatic reasons we just use the dist tag because that’s conceptually what we want. Why is the exact version interesting here considering the goal is to always install the latest version?

Top Results From Across the Web

What's the difference between tilde(~) and caret(^) in package ...

It is used when you're ready to accept bug-fixes in your dependency, but don't want any potentially incompatible changes. The tilde matches the ......

segux/fix-package-versions - GitHub

fix -package-versions. CodeFactor Build Status Published on npm. Description. This package fixes node dependencies versions so they don't get updated nex ...

About semantic versioning - npm Docs

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

Semver explained - why is there a caret (^) in my package.json?

json for each dependency. Instead of specifying the exact version to be installed in package.json, npm allows you to widen the range of...

How to Manage Dependency Version More Efficiently

npm i or npm install — this command installs the latest or updated dependencies depending on Tilde(~) or Caret(~) symbol in the package.json...