imsnif / imsnif/synp

Package-lock.json missing some deps compared to npm's version

Open
#62 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
788
Forks
42
PR merge metrics
No merged PRs in 30d

Description

#### Issue description:
After converting yarn.lock, generated package-lock.json is missing some dep declaration and some "dev" flags (using 1.9.4)
Capture d’écran 2020-10-07 à 17 26 01

Here all json/lock files : https://gofile.io/uploadFiles
Or directly attached (beware of .txt extension)
[package-lock-npm.json.txt](https://github.com/imsnif/synp/files/5341805/package-lock-npm.json.txt)
[package-lock-synp.json.txt](https://github.com/imsnif/synp/files/5341806/package-lock-synp.json.txt)
[package.json.txt](https://github.com/imsnif/synp/files/5341807/package.json.txt)
[yarn.lock.txt](https://github.com/imsnif/synp/files/5341808/yarn.lock.txt)

I made a gitlab project for testing synp AND https://github.com/jeremylong/DependencyCheck.
https://gitlab.com/boloss/test-dependency-check
You can fork it if you want

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by comparing the attached package-lock-npm.json.txt, package-lock-synp.json.txt, package.json.txt, and yarn.lock.txt, then reproduce the conversion with synp 1.9.4. Investigate why dependency declarations and dev flags differ, and consider the issue complete when the generated package-lock.json matches npm's version for the supplied project.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.