Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]fossa cannot analyze the new format of pnpm-lock.yaml #1307

Open
LoisHuang2022 opened this issue Oct 19, 2023 · 1 comment
Open

[BUG]fossa cannot analyze the new format of pnpm-lock.yaml #1307

LoisHuang2022 opened this issue Oct 19, 2023 · 1 comment

Comments

@LoisHuang2022
Copy link

Describe the bug
Fossa doesn't seem to be able to analyze the new format of 'pnpm-lock.yaml'.

To Reproduce
Steps to reproduce the behavior:
pnpm-lock.yaml:

lockfileVersion: '6.0'

settings:
  autoInstallPeers: true
  excludeLinksFromLockfile: false

dependencies:
  '@emotion/react':
    specifier: ^11.10.6
    version: 11.11.1(@types/react@18.2.21)(react@18.2.0)
......
  1. Run fossa analyze
  2. See error
An issue occurred

  >>> Relevant errors

    Error

      Error parsing file: /xxxxxx/pnpm-lock.yaml.

          Aeson exception:
          Error in $.dependencies['@emotion/react']: parsing Text failed, expected String, but encountered Object

but if use this format

lockfileVersion: 5.4
specifiers:
  '@emotion/react': ^11.10.6
......
dependencies:
  '@emotion/react': 11.11.1

fossa analyze runs successfully

Additional context
fossa-cli version 3.8.18

@github-actions
Copy link

Thank you @LoisHuang2022 for creating this issue. If this is in regards to a defect, product question or feature request: you should use our support portal at https://support.fossa.com to file a request, as you would receive more immediate support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant