codesandbox / codesandbox/codesandbox-client

Incorrect latest version of certain dependencies

Open
#8,098 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
13.6k
Forks
2.4k
Avg merge
6d 19h
Merged PRs (30d)
2

Description

🐛 bug report

Preflight Checklist

  • I have read the [Contributing Guidelines][contributing] for this project.
  • I agree to follow the [Code of Conduct][code_of_conduct] that this project
    adheres to.
  • I have searched the issue tracker for an issue that matches the one I want
    to file, without success.

Description of the problem

I'm encountering an issue while attempting to install the latest version of certain dependencies. For instance, when I try to add @faker-js/faker as a dependency, it reports that version 7.6.0 is the latest available. However, when checking on npm, it shows that version 8.1.0 is the latest release.


@faker-js/faker@8.1.0 | MIT | deps: none | versions: 57
Generate massive amounts of fake contextual data
https://github.com/faker-js/faker#readme

keywords: faker, faker.js, fakerjs, faker-js, fake data generator, fake data, fake-data, fake-generator, fake-data-generator, fake content generator, fake contextual data generator, fake contextual data

dist
.tarball: https://registry.npmjs.org/@faker-js/faker/-/faker-8.1.0.tgz
.shasum: e14896f1c57af2495e341dc4c7bf04125c8aeafd
.integrity: sha512-38DT60rumHfBYynif3lmtxMqMqmsOQIxQgEuPZxCk2yUYN0eqWpTACgxi0VpidvsJB8CRxCpvP7B3anK85FjtQ==
.unpackedSize: 10.2 MB

maintainers:
- division-by-zero <leyla.jaehnig@gmx.de>
- shinigami92 <chrissi92@hotmail.de>
- prisis <d.bannert@anolilab.de>
- damienwebdev <damienwebdev@gmail.com>

dist-tags:
latest: 8.1.0  next: 8.1.0    old: 7.6.0     stable: 8.0.2
faker
To Reproduce
  • From any sandbox try to add @faker-js/faker as dependency

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin with the dependency-add flow in any sandbox and reproduce the reported result for @faker-js/faker. The issue names no source file or test, so trace how the sandbox determines the latest version and verify that it reports 8.1.0 rather than 7.6.0.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.